Two calculators, one birth, two different answers

If you have ever put your birth details into two dasha calculators, there is a fair chance you got two different tables. Not wildly different — the same Mahadasha lord, usually — but start and end dates that disagree by months, and sometimes a different Antardasha running today. That experience makes people distrust the whole system, and it should not. The system is deterministic. It is the inputs that differ, and there are exactly two of them that matter.

The Vimshottari dasha calculation is genuinely short. One table lookup, one division, one multiplication, and a walk along a fixed nine-planet wheel. It is short enough that you can do it on paper in about ten minutes, and doing it once is the only reliable way to know whether the table you were handed is right — or which of two disagreeing tables to believe.

This guide works it end to end on one birth, with every number shown. Everything here is arithmetic you can reproduce; nothing depends on interpretation. What each period means is a separate question, and our Mahadasha and Antardasha guide answers it. This page is only about where the dates come from.

Step 1 — find the nakshatra your Moon was in, and read off its lord

Vimshottari is driven entirely by the Moon. Not the Sun, not the ascendant — the Moon’s sidereal longitude at the moment of birth, and nothing else. The zodiac is divided into 27 nakshatras (lunar mansions) of 13°20′ each, and each nakshatra is permanently assigned to one of the nine dasha planets. Whichever nakshatra your Moon occupied, that nakshatra’s lord is the Mahadasha you were born into.

The assignment repeats in threes: the nine lords run in Vimshottari order (Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury) across nakshatras 1–9, then again across 10–18, then again across 19–27. So Ashwini, Magha and Mula are all Ketu’s; Rohini, Hasta and Shravana are all the Moon’s; and so on. This mapping is fixed and is not a matter of school or opinion.

For our worked example, take a birth on 15 June 1990 at 07:30 IST in New Delhi. Computed sidereally on the Lahiri ayanamsa, the Moon sits at 316°05′37″ — which falls inside Shatabhisha, the 24th nakshatra, whose lord is Rahu. So this person was born in a Rahu Mahadasha, and Rahu’s full term is 18 years.

That is the entire first step. The only thing that can go wrong here is the word sidereal, and it is the subject of the last section of this guide.

Step 2 — the balance at birth, which is the only real arithmetic in the system

Almost nobody is born at the exact start of a nakshatra, so almost nobody gets their first Mahadasha in full. You inherit whatever part of it had not yet run — the balance of dasha at birth. This single number sets every date in your entire 120-year table, because every later period is stacked on top of it. Get it wrong by six months and every boundary for the rest of your life is wrong by six months.

The rule is a straight proportion. Work out how far into the nakshatra the Moon had travelled, as a fraction of the nakshatra’s full 13°20′. That fraction of the Mahadasha has already elapsed; the remainder is your balance.

In the worked example the Moon is at 316°05′37″. Shatabhisha begins at 306°40′, so the Moon has travelled 9°25.6′ into it — 9.427° out of 13.333°, which is 70.703% of the way through. That means 29.297% of Rahu’s eighteen years were still to run at the first breath: 18 × 0.29297 = 5.2734 years, or 5 years 3 months 9 days. Rahu’s Mahadasha therefore ends on 23 September 1995.

It is worth pausing on how sensitive this is. The nakshatra is only 13°20′ wide, and the Moon crosses roughly that much sky in a day. A birth time recorded an hour late moves the Moon about half a degree, which is about 4% of a nakshatra — on an 18-year period, roughly eight months of balance. This is why astrologers ask for the birth time to the minute, and why a chart cast from a remembered "sometime in the morning" cannot produce trustworthy dasha dates. If your birth time is genuinely uncertain, treat every date in your table as approximate rather than pretending to a precision the input does not support.

Step 3 — walk the wheel forward to today

From here it is addition. The balance runs out, and then each following planet takes its full term in the fixed Vimshottari order, wrapping around the wheel. Nothing is skipped and nothing is reordered.

For our example birth, Rahu’s partial period runs from birth to 23 September 1995. Jupiter follows with its full 16 years, to 23 September 2011. Saturn follows with its full 19 years, to 23 September 2030. So this person has been in a Saturn Mahadasha since September 2011 and will be until September 2030 — and in August 2026 they are about three-quarters of the way through it.

Two small things trip people up here. First, the wheel continues past Mercury back to Ketu; it does not stop at the end of the list. Second, a period that began before birth is not shortened for anyone but you: the sub-periods inside your first Mahadasha are still carved out of its complete term, and simply start part-way through, which is why your first Antardasha is usually a partial one too.

If the planet you land on is Saturn or Rahu, we have written the long version of what those specific periods ask: Shani Mahadasha covers Saturn’s nineteen years and, usefully, separates them from Sade Sati — a different Saturn clock that people constantly confuse with this one. Rahu Mahadasha does the same for Rahu’s eighteen.

Step 4 — divide the Mahadasha to get the Antardasha

Each Mahadasha is subdivided into nine Antardashas (also called bhuktis), one for each planet, in the same fixed order — except that the sequence starts with the Mahadasha lord itself and then continues around the wheel. So Saturn’s Mahadasha opens with Saturn–Saturn, then Saturn–Mercury, Saturn–Ketu, Saturn–Venus, Saturn–Sun, Saturn–Moon, Saturn–Mars, Saturn–Rahu, Saturn–Jupiter.

The length of each is proportional to the sub-lord’s own share of the 120-year cycle: multiply the Mahadasha’s years by the sub-lord’s years and divide by 120. Saturn–Rahu, for instance, is 19 × 18 ÷ 120 = 2.85 years. The nine sub-periods always sum back to the parent period exactly, which is a useful check on your own arithmetic — if they do not sum to the parent, you have made a mistake.

Applying that to the worked example: inside the Saturn Mahadasha running 2011–2030, Saturn–Saturn runs to September 2014, Saturn–Mercury to June 2017, Saturn–Ketu to July 2018, Saturn–Venus to September 2021, Saturn–Sun to August 2022, Saturn–Moon to March 2024, Saturn–Mars to May 2025, and Saturn–Rahu from 5 May 2025 to 11 March 2028. So in August 2026 this person is in Saturn Mahadasha, Saturn–Rahu Antardasha.

That is the complete answer to "which dasha am I in" — and you can now check it against whatever your chart tool says. If the two disagree, the last section explains why.

One level further — the Pratyantardasha, and where to stop

The same proportional rule applies again inside the Antardasha, producing the Pratyantardasha — the third level. Multiply the Antardasha’s length by the sub-sub-lord’s years and divide by 120, running the nine planets in order starting from the Antardasha lord.

In the worked example, the Saturn–Rahu Antardasha of 2.85 years divides into Saturn–Rahu–Rahu (about five months from May 2025), then Saturn–Rahu–Jupiter, then Saturn–Rahu–Saturn to 7 August 2026, then Saturn–Rahu–Mercury to early January 2027, and so on. In mid-August 2026 this person is a few days into Saturn–Rahu–Mercury.

The subdivision can continue — the classical texts name two further levels, Sookshma and Prana — and our own chart engine computes them. But there is an honest limit worth stating. At the fourth and fifth levels the periods are days and hours long, which means they are shorter than the uncertainty in most people’s recorded birth time. If a one-hour error in your birth time moves your Mahadasha boundaries by eight months, it moves your Prana boundaries clean past several of them. Reading the fifth level off a chart cast from an approximate birth time is false precision, however confidently the software prints it.

As a practical rule: the Mahadasha and Antardasha are what a reading is built on, the Pratyantardasha is a useful refinement when the birth time is genuinely reliable, and below that you are measuring with an instrument finer than your input.

Why two calculators disagree, cause 1: the ayanamsa

Step 1 needed the Moon’s sidereal longitude — its position measured against the fixed stars, which is what Vedic astrology uses. Astronomical software natively computes the tropical longitude, measured from the equinox. The difference between the two is called the ayanamsa, and it must be subtracted to get a sidereal position.

The problem is that there is no single agreed ayanamsa. Several are in serious use, and they do not agree with each other. Computed against the Swiss Ephemeris, Lahiri and Raman differ by 1.4463°, and Lahiri and Krishnamurti by 0.0969°. These are not rounding errors: a nakshatra is only 13°20′ wide, so the Lahiri–Raman gap is 10.85% of an entire nakshatra.

Feed that into step 2 and the consequences are large. That 10.85% shifts the balance at birth by 10.85% of the Mahadasha’s length — about 2 years 2 months on a Venus period, 2 years on a Saturn period, 1 year 11 months on a Rahu period — and every boundary in the table moves with it. And because the gap is a tenth of a nakshatra, roughly one birth in nine falls close enough to a nakshatra boundary that Lahiri and Raman disagree about which nakshatra the Moon was in at all, and therefore about which Mahadasha the person was born into.

Our worked example shows this concretely. The same Moon reads 316.094° under Lahiri and 317.540° under Raman. Both put it in Shatabhisha, so both agree the first Mahadasha is Rahu — but Lahiri gives a balance of 5.27 years and Raman gives 3.32 years, and that near-two-year shift propagates all the way down. In August 2026, the Lahiri table says this person is in Saturn–Rahu; the Raman table says Saturn–Jupiter. Same birth, same system, same arithmetic — a different answer to "which sub-period am I in today", entirely because of a choice made before the calculation started.

Neither table is wrong in the sense of containing an error. They are answers to slightly different questions, and the only defensible thing a tool can do is say which question it answered. That is why our own chart output states the ayanamsa it was built with rather than leaving it implicit — the default is Lahiri, the system most widely used in India. When you generate your Kundali, the dasha table comes with the convention that produced it attached.

Why two calculators disagree, cause 2: how long a dasha year is

The second cause is smaller, less discussed, and catches people out because it looks like a rounding difference until it is not.

The Vimshottari periods are stated in years — Rahu 18, Saturn 19 — but converting "18 years" into a calendar date requires deciding how many days a year has. Implementations differ. Some use the solar year of about 365.25 days. Others use a 360-day scheme of twelve 30-day months, which is a tidy way to express durations as years, months and days. The two are 1.46% apart.

That sounds negligible and is not, because the error compounds along the wheel. On our worked example, holding the ayanamsa fixed at Lahiri and changing only this convention: the first period boundary moves 27 days, the second 111 days, the third 211 days, and the fourth 300 days. The further from birth you look, the further apart the two tables drift — so a disagreement of a few days in childhood becomes most of a year by the period you actually care about.

Our engine uses 365.25 days. There is no universal right answer here either; what matters is that a tool is consistent and says what it does. If two tables agree on the ayanamsa and still disagree by a few months at a distant boundary, this is almost always the reason.

Worth separating out: a third source of small differences is the underlying ephemeris — the body of astronomical data used to locate the Moon. Modern ephemerides agree to well under an arcsecond, which is far too small to move a nakshatra fraction meaningfully, so this one is a real but immaterial difference. It is included in what our chart declares anyway, on the principle that a number you cannot audit is a number you have to take on faith.

Four things to check before you trust a dasha table

Put together, the arithmetic above gives you a short audit you can run on any dasha table, including one produced by us.

None of this makes the dasha table less useful. It makes it checkable, which is a different and better thing. A timing system you can audit is one you can reason with; a table you have to take on trust is one you will eventually stop believing.

• Which ayanamsa? If the tool does not say, you cannot reconcile its table with any other, and this is the largest single cause of disagreement between calculators.
• What length of dasha year? 365.25 days or a 360-day scheme — the difference is invisible near birth and grows to months at the boundaries you care about.
• How precise is the birth time it was given? An hour of uncertainty is roughly eight months of Mahadasha boundary on an 18-year period, and it invalidates the fourth and fifth subdivision levels entirely.
• Do the sub-periods sum to their parent? Nine Antardashas must add back to the Mahadasha exactly. If they do not, the table has an arithmetic error and nothing below it can be relied on.

What the arithmetic is for

Working the calculation once changes how you read the result. The dasha table stops being an oracle handed down by software and becomes what it actually is: a deterministic schedule derived from one measurement — where the Moon was when you were born — under two stated conventions.

It also clarifies what the tradition takes the schedule to be. In classical Jyotish the dasha sequence is understood as the order in which stored karma becomes available to ripen — which is why the timetable is fixed at birth and cannot be renegotiated, and equally why knowing it is held to be useful rather than fatalistic. That is a philosophical claim, not an arithmetical one, and it is worth keeping clearly separate from the calculation: the division above would produce the same dates whatever one believed about why the sequence exists.

That also puts the interpretive question in its proper place. The arithmetic tells you which planet is running and when it changes. It says nothing at all about what that period will bring, because that depends on where the planet sits in your chart, which houses it rules, and its dignity — none of which appear anywhere in the calculation above. This is the point our Mahadasha and Antardasha guide makes at length, and it is worth repeating here: the chart is the content, the dasha is only the timing.

So the useful next step is not another calculator. It is to take the period you have just identified and ask what that specific planet is doing in your specific chart — which house it rules, whether it is a functional benefic for your ascendant, and how it interacts with the sub-period lord running inside it. That is the question that produces foresight instead of anxiety, and it is the one worth taking to a reading.