Ten calculation modes, eighteen divisional charts, 82 event questions — and a published study of whether the timing engine works. Written so a practitioner can check every claim.
In short. astrocult computes a full Parashari chart set, KP as a genuinely separate system, and a Vimshottari event scan across 82 classical questions. What it will not do is attach a date or a probability to a life event — because we tested that and published the result.
The difference from most Jyotish software is not the number of features. It is that every number here is either arithmetic you can verify against an ephemeris, or a classical rule shown with its reasoning attached. Nothing in between is presented as a forecast.
Ten independent calculation modes, each with its own reference frame rather than a shared one bent to fit:
Positions are computed in-app rather than fetched, so the figures below are the ones that matter. Every one of them is verifiable against any standard ephemeris — that is the point of publishing them.
| Quantity | Method | Agreement |
|---|---|---|
| Sun | Truncated VSOP87 | ~1″ |
| Moon | Meeus lunar theory | ~10″ |
| Time base | ΔT correction applied | — |
| KP ayanamsa | Calibrated to KSK 1900.0 epoch | within ~3′, 1900–2100 |
| Lagna | From city centroid | sub-degree |
| D-60 sensitivity | Shifts with birth time | ~every 2 min |
The KP row deserves the honesty it gets in the app itself: at roughly 3 arc-minutes of drift by 2025, that is about 6% of the narrowest sub-division. Star and sub lords are unaffected — but a cuspal sub lord sitting within 3′ of a boundary may differ from software built directly on Swiss Ephemeris. The app says so rather than hiding it.
82 classical questions — marriage, first job, property, higher study, litigation, chronic illness, and so on. Each one is not a keyword but a rule set: a primary house, weighted supporting houses, obstructing houses, natural karakas, and the divisional chart the tradition assigns to it. Marriage, for instance, resolves to the 7th house, the 2nd and 11th as weighted support, the 6th and 12th as obstruction, Venus and Jupiter as karakas, and D-9 for refinement.
You can enter events that have already happened. The app then shows what these same rules say about them — which period was running, and whether its lords are significators for that event in your chart. It reports the tally plainly: if your real marriage falls in a period the rules never flag, you see that before you weigh anything still ahead.
Not on feature count — plenty of packages compute more vargas or more dasha systems. The differences that matter are about what the software is willing to claim.
| Question | Commonly | Here |
|---|---|---|
| Event timing | A date range with a confidence percentage | Named periods with dasha boundary dates; no probability attached |
| Basis for the ranking | An undisclosed score out of 100 | A count of classical indicators that converge, defined on screen |
| Published validation | None | 111 charts, 866 dated events, result published including the null |
| Checking it against your life | Not offered | Backtest panel, plus a multiple-comparisons warning before you look |
| KP | Often Lahiri and whole-sign relabelled | Krishnamurti ayanamsa with Placidus cusps, as KP requires |
| Rectification | Returns one “correct” time | Returns Inconclusive when candidates score alike, and says why |
| When significators are absent | Lists periods anyway | Says the classical significators are not present, and lists nothing |
These are design decisions, not missing features. Each one was in the product at some point and was removed on evidence.
Every panel, label, note and caveat exists in both languages — not a machine translation layer over an English product, but written text in each, with Devanagari typography set properly rather than squeezed into a Latin line height.