Rahu True Node vs Mean Node — The 1.29° Difference That Changes Your Kundali
If you have ever noticed Rahu in a slightly different position between two Vedic astrology software programs — different enough to change the nakshatra or pada — you have hit the true node vs mean node problem. It is one of the most common sources of disagreement between Vedic astrology apps, and it is entirely a calculation choice, not a bug.
The mean node smooths out the Moon's orbital wobble and gives a steady retrograde position. The true node(osculating node) uses the actual instantaneous intersection of the Moon's orbit with the ecliptic — it oscillates back and forth around the mean position with an amplitude of ±1.29° and a period of about 6 months. Jagannatha Hora uses the true node. Most traditional Vedic texts assume the mean node. VedIntel™ AstroAPI uses the true node for alignment with modern Vedic software standards.
What Rahu Actually Is
Rahu and Ketu are not physical planets. They are the two points where the Moon's orbital plane intersects the ecliptic (the plane of Earth's orbit around the Sun). Rahu is the ascending intersection — where the Moon crosses northward through the ecliptic. Ketu is the descending intersection, always exactly 180° opposite.
Because the Moon's orbit precesses — its orbital plane rotates slowly — Rahu and Ketu move backward through the zodiac completing one full revolution in approximately 18.6 years. This is why Rahu is always retrograde in traditional Vedic charts.
The complication is that the Moon's orbit is not a perfect ellipse. It is perturbed by the Sun's gravity, which causes the actual node position to oscillate around the smooth mean. The mean node ignores this oscillation. The true node captures it.
The 1.29° Maximum Difference
The oscillation amplitude is ±1.29° with a roughly 6-month period. In practice, at any given birth date, the difference between true and mean Rahu can be anywhere from near-zero to the full 1.29°.
- Each nakshatra spans 13.333° — so 1.29° is about 10% of a nakshatra width
- Near nakshatra boundaries, 1.29° can push Rahu into a different nakshatra entirely
- Each nakshatra has 4 padas of 3.333° each — so 1.29° can change the pada
- The nakshatra lord determines the Vimshottari dasha lord — a different lord means a completely different dasha timeline interpretation
As a concrete example: for a chart with Rahu near 11° Libra (Swati nakshatra pada 2), the mean node would place it approximately 0.9° differently — still Swati, but a different pada. For charts near a nakshatra boundary, the difference can cause a full nakshatra change.
In Swiss Ephemeris: SE_MEAN_NODE vs SE_TRUE_NODE
Swiss Ephemeris exposes both calculations as named constants:
VedIntel™ AstroAPI uses SE_TRUE_NODE. This matches Jagannatha Hora, which is the reference software for our golden record test suite. The API returns the true node position for Rahu and Ketu in all endpoints.
Kaalsarp Dosha and the Node Choice
Kaalsarp dosha — one of the most commonly checked doshas in Vedic astrology — depends entirely on Rahu and Ketu positions. The check is: are all seven planets (Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn) hemmed between Rahu and Ketu on one side of the chart?
A 1.29° difference in Rahu position near a planet can determine whether that planet falls inside or outside the Rahu-Ketu axis — which determines whether Kaalsarp dosha is present. This is not an edge case. For charts where a planet is within 1.29° of Rahu or Ketu, the true vs mean choice can flip the Kaalsarp result.
Verify Rahu Position in Your App
Every VedIntel™ API response includes Rahu and Ketu positions with nakshatra, pada, and nakshatra lord. Free plan — 500 calls/month, no credit card.