Loading...
Loading...
Argument-fuelling reference
The D-9 Navamsa is the most-quoted divisional chart in Vedic astrology — it's the marriage chart, the inner-self chart, the destiny chart. Two software tools that agree on the Lagna can still disagree on the Navamsa Lagna, because a planet sitting near a 3°20' pada boundary shifts to the next Navamsa under a tiny ayanamsha rounding. Here is how the division works, where the disagreements come from, and how to verify a Navamsa boundary call.
Every rashi is divided into 9 padas of exactly 3°20' (= 200 arcminutes). A planet's pada index within its sign tells you which navamsa rashi it occupies on the D-9 chart. The starting Navamsa rashi depends on the parent rashi's quality (chara/sthira/dwiswabhava).
Take a planet's sidereal longitude. Find its position within its rashi (longitude mod 30°). Divide by 3°20' (3.333…°) to get the pada index 1-9. The Navamsa rashi for that planet starts from a fixed rashi determined by the parent rashi's element-quality combination: chara (movable) rashis start the Navamsa cycle from themselves, sthira (fixed) from the 9th rashi forward, dwiswabhava (mutable) from the 5th. Count pada-1 forward from the starting rashi to find the actual Navamsa rashi.
Worked example: a planet at sidereal 16°43' Aries. Position within rashi = 16°43'. Divide by 3°20' = 5.0125 → pada 6 (the second arcminute past the boundary at 16°40'). Aries is chara, so the Navamsa cycle starts from Aries itself. Counting 6 from Aries: Aries → Taurus → Gemini → Cancer → Leo → Virgo. The planet's Navamsa is Virgo. If the same planet had sat at 16°39'59", its position-within-rashi would be 16°39'59" → divide by 3°20' = 4.9999 → pada 5 → Leo, not Virgo. That is a 60-arcsecond boundary, smaller than the rounding noise on most ayanamsha calculations.
Three sources, in order of impact:
First and biggest — the choice of ayanamsha. Lahiri (24.22° at 2026.0) and Raman (22.82°) differ by 1.4° — more than the entire width of one Navamsa pada. A planet at tropical 17°50' Aries lands at sidereal 23°37' Pisces under Lahiri (pada 8 → Sagittarius Navamsa) but at sidereal 25°02' Pisces under Raman (pada 8 → Sagittarius Navamsa) — same Navamsa here but a few percent of charts shift to the next pada. See the [Ayanamsha Comparison page](/learn/ayanamsha-comparison) for the per-system shift table.
Second — pre-1880 birth timezones. Before standardised civil timezones, software either falls back to the city's longitude-based local mean time (LMT) or to a modern tzdb-imposed offset (often wrong by 10-25 minutes for cities outside major capitals). Einstein's 1879 Ulm chart computes UT = 10:50 under LMT vs UT = 10:37 under Berlin tzdb — a 13-minute shift, enough to move the Lagna across a pada boundary. Our engine uses LMT for pre-1880 births per the historical-timezones policy in the Calculation Standards.
Third — engine precision. Pure JavaScript engines using truncated orbital elements (the Meeus method) place the Moon within ±0.5° of Swiss Ephemeris; the Sun within ±0.01°. That sub-degree noise is dwarfed by the ayanamsha-choice impact, but it can flip a Navamsa decision for a planet at exactly 16°40'00" within its rashi. Our engine prefers Swiss Ephemeris when available (sub-arcsecond) and surfaces a warning on the chart when the Meeus fallback is active.
Take the planet's sidereal longitude (D-1 chart). Compute (longitude mod 30°) ÷ 3°20'. The integer part + 1 is the pada index. If the fractional part is below 0.05 or above 0.95, the planet is within 10 arcminutes of a pada boundary — flag the result and re-verify with a high-precision Swiss Ephemeris source. For Navamsa cases at exact half-degree boundaries, classical commentators sometimes prefer the previous pada (the "Krishnamurti rule"), sometimes the next; our engine follows the modern JHora convention (round up to the next pada at the boundary).