Rahu and Ketu are not bodies in the sky. They are the two points where the Moon's path crosses the Sun's path, and there are two standard ways to compute where those points are. The mean node is an average: a point that slides backwards through the zodiac at a steady rate. The true node is the actual crossing point at that moment, which swings a little ahead of and behind the average. Some software shows one, some the other, and a few let you choose. That is one of the reasons a kundli can differ between apps.
The short answer: the two are never far apart. In this engine's run for 2026, the largest gap is 1.731 degrees. This app uses the mean node in every calculator, and the gap changes an answer only in a few edge cases, which this page names and measures.
What a node is
The translator's introduction to the Bhrigu Sutras (Part I, pp. 12-13) gives the standard description. The Moon's orbit and the Sun's apparent path are tilted to each other, so they cross at two points. Where the Moon crosses going from south to north is the ascending node, named Rahu; where it crosses going north to south is the descending node, Ketu. The passage says the two are "exactly 180 degrees apart", and that their motion is "always retrograde", at "19 degrees 20 minutes per year", so that Rahu and Ketu stay in a sign "for about 18 months".
That description fits the mean node exactly. This engine's mean node moves 0.05295 degrees backwards per day, which is 19.34 degrees per year, and it goes once round the zodiac in 18.61 years. Thirty degrees at 19.34 degrees a year is 1.55 years in each sign: the "about 18 months" of the passage. The BPHS translation's note in Ch. 3, which lists average daily motions, gives Rahu and Ketu 3 minutes of arc a day, also an average.
Neither text says whether its authors meant the averaged point or the true one, and no book in this app's library uses the words "mean node" or "true node" at all. A search of the whole corpus for both terms returns nothing. So the choice is a convention, not a ruling from the texts, and this page treats it that way.
Why the true node wobbles
The line where the Moon's orbit crosses the Sun's path does not turn at a perfectly steady rate. The true node runs ahead of the average for a while, then falls behind it. This engine computes the difference with the five periodic terms in Meeus, Astronomical Algorithms (2nd ed., Ch. 47), in the function the true node offset calculation in the app's code. The largest of those five terms has a coefficient of 1.4979 degrees, which is why the gap rarely gets much past one and a half degrees.
One consequence surprises people. Because the wobble sometimes carries the true node forward faster than the average carries it back, the true node is not always retrograde. Sampling 2026 once a day at 00:00 UTC, the true node moved forward on 94 of 364 day-to-day steps. The mean node, by construction, moves backward every day. This is why the app marks Rahu and Ketu as retrograde in every chart: that is true of the mean node it uses, and it matches the Bhrigu Sutras passage. For what retrograde means for other grahas, see vakri (retrograde).
How big the gap is, with this engine's numbers
| Date (00:00 UTC) | Mean Rahu (sidereal) | True minus mean |
|---|---|---|
| 1 January 2026 | 317.9532 (Aquarius) | -1.0907 degrees |
| 1 April 2026 | Aquarius | +1.3122 degrees |
| 1 July 2026 | Aquarius | -1.6650 degrees |
| 1 October 2026 | Aquarius | +1.4206 degrees |
| 18 November 2026 | 300.9428 (Aquarius) | +0.0237 degrees |
Across 2026, sampled daily, the gap peaks at +1.731 degrees on 9 October and reaches -1.722 degrees on 26 December. Sampled hourly, it is larger than one degree in 4,752 of the year's 8,761 hours, 54.2% of the time. Over a longer span, 1970 to 2060 in six-hour steps, the largest gap this engine finds is 1.878 degrees, on 22 September 1980. The code comment in the app's code gives "about 1.88 degrees" for 1970-2015, which agrees.
For scale: one sign is 30 degrees and one nakshatra is 13 degrees 20 minutes. A gap under two degrees cannot move Rahu more than one step across a line, and it moves it across a line only when Rahu is already close to one.
Where the choice changes an answer
The sign of Rahu and Ketu, near an ingress
A live example is happening as this page is written. By this app's mean node, Rahu enters Capricorn on 5 December 2026 at 18:59 UTC and stays until 23 June 2028 at 21:57 UTC (Rahu transit in Capricorn). The true node, computed in one-minute steps, crosses from Aquarius into Capricorn on 25 November 2026 at 03:51 UTC. The two ingresses are 10 days and 15 hours apart.
| Node | Enters Capricorn (UTC) | In India (IST) |
|---|---|---|
| True node | 25 November 2026, 03:51 | 25 November 2026, 09:21 |
| Mean node (this app) | 5 December 2026, 18:59 | 6 December 2026, 00:29 |
The mean ingress at 18:59 UTC falls after 18:30 UTC, so in India it is already 6 December. Sampling 2026 once a day, the true and mean Rahu sit in different signs on 10 days, all in that window, and in different nakshatras on 31 days. So a Gochar (transit) reading taken in late November 2026 will put Rahu in Aquarius here and in Capricorn on a true-node tool. Ketu, always opposite, changes sign with it. Dates near an ingress from any software can differ by hours to a day or two for other reasons as well, such as the ayanamsa.
The house of Rahu in a birth chart
This app counts houses by whole signs, so Rahu's house changes only when its sign changes. For a birth during one of those few days a year when the two nodes are in different signs, the birth chart here and on a true-node tool will put Rahu and Ketu one house apart, and every reading tied to that house moves with them. For any other birth, the two nodes share a sign and a house, and only the degree differs.
Kaal Sarp verdicts on the edge
Kaal Sarp asks whether all seven grahas from the Sun to Saturn lie on one side of the Rahu-Ketu axis. Move the axis by a degree and a graha that sat just inside can fall just outside. The Kaal Sarp calculator is the one place in this app that checks this: it computes the verdict on the mean node, then recomputes it with the true node as a probe, and says whether the answer holds. (What the rule is, and what the texts do and do not say about it, is in Kaal Sarp dosha explained.)
Worked example, run through the engine: born 12 January 1997 at 12:00 IST (06:30 UTC), New Delhi. Mean Rahu is at 158.6469 degrees. Counting each graha's distance forward from Rahu gives Mars 0.0938, Venus 90.1027, Mercury 90.5311, Sun 109.6377, Jupiter 115.3832, Moon 152.8723 and Saturn 179.4235 degrees. All seven are between 0 and 180, so on the mean node the combination is present, with Mars only 0.0938 degrees from the edge.
At that moment the true node is 1.2618 degrees behind the mean node. Moving the axis back by that much pushes Saturn past the far end, and on the true node the verdict is not present. The calculator prints exactly this: "No text in this app's library says which node the rule intends, so this chart is a genuine borderline case."
How often does this happen? Of 3,000 sampled birth moments 1985-2060 (evenly spaced, New Delhi), the mean-node rule found Kaal Sarp in 190, and in 17 the verdict changed on the true node. The other 2,983 charts give the same answer either way.
What the choice does not touch
- The Vimshottari dasha dates. They run from the Moon's nakshatra, not from Rahu's position, so a Rahu Mahadasha starts on the same day either way.
- The Moon, Sun, ascendant and the other seven grahas. Only Rahu and Ketu move.
- The ayanamsa. The same Lahiri value is subtracted from both nodes, so the gap between them is the same in tropical and sidereal terms.
- The order of Rahu and Ketu. On either method they stay exactly 180 degrees apart.
What this app does, and why
Rahu everywhere in this app is the mean node: in the birth chart, the transits, the dashas, the yogas and the doshas. Ketu is placed exactly opposite it. The engine comment on the true node offset calculation states the reason: it is "A DIAGNOSTIC, not a correction", because "No text in this project's library says which node a rule was written for". Since the texts give no ruling, the app keeps one convention and keeps it everywhere, so that the Rahu in your chart, in the transit page and in the dosha check is always the same point.
The mean node also matches the description the library does give: steady retrograde motion, 19 degrees 20 minutes a year, about 18 months in a sign. Where the choice could flip a verdict, as in Kaal Sarp, the app does not hide it; it reports the true-node result beside the mean one and calls the chart borderline. The methodology page and the sources page set out the rest of the engine's conventions.
Limits: what no tool can settle
- Which node the classical rules meant. The library is silent, and no calculation can answer a question about intent.
- Which of two charts is "right" when they differ only in the node. Both are correct computations of different, well-defined points.
- Small differences between two true-node tools. This engine uses five periodic terms; other software may use more, so two true-node programs can disagree by a fraction of a degree.
- Whether a borderline Kaal Sarp chart "has" the combination. The honest answer is the one the calculator gives: it depends on the convention. Nothing in the chart on its own, or in Rahu's or Ketu's readings, decides it.
If you compare this app with another tool, first check which node each one uses. If Rahu differs by a degree or two and everything else matches, the node is almost certainly the reason. If the Moon or ascendant differ as well, look at time zone, place and ayanamsa first, as why apps disagree on your nakshatra explains.
- Does this app use the mean node or the true node?
- The mean node, in every calculator. Ketu is placed exactly 180 degrees from it. The true node is computed only as a check inside the Kaal Sarp calculator.
- How far apart can the two nodes be?
- In this engine's run for 2026, at most 1.731 degrees. From 1970 to 2060 the largest gap it finds is 1.878 degrees, on 22 September 1980.
- Why does my Rahu differ from another app by about a degree?
- Most likely one app uses the mean node and the other the true node. If only Rahu and Ketu differ, that is the reason; if the Moon or ascendant differ too, see why a kundli differs between apps.
- Is the true node more accurate?
- It is the more exact position of the actual crossing point. Whether astrological rules were written for that point or the average is a separate question, and no text in this app's library answers it.
- Is Rahu always retrograde?
- The mean node always is, and the Bhrigu Sutras introduction describes the nodes' motion as "always retrograde". The true node is not: sampled daily in 2026, it moved forward on 94 of 364 steps.
- Can the node choice change my Kaal Sarp result?
- Only when a graha sits very close to the axis. Of 3,000 sampled birth moments 1985-2060, the verdict changed in 17. The Kaal Sarp calculator tells you when your chart is one of them.
Kaal Sarp Dosha
Whether all seven classical grahas sit on one side of the Rahu-Ketu axis, and how close the call is.
This date and time are sent only to compute the answer. No name or place is asked for, nothing is stored, and no account is created.