Numerology Dasha

What this long-form adds to the calculator above

The calculator above lays out the main periods of a numerology dasha and names the one running now. This section covers what the short copy does not: where the system sits beside the astrological Vimshottari and how the two differ, the full first round of lords for every Mulank, the sub-periods the Numerology page cuts each period into, how this app compares the numerology dasha with the astrological one, and how the timeline's boundaries are dated. Every date below was produced by this app's engine in scripts run for this page.

A note on how the period boundaries are dated now

The change matters in one practical way: the running lord now changes on the birthday rather than a day or two before it. A birth on 29 February is the one special case. In a common year the anniversary does not exist, and the engine's date arithmetic rolls it to 1 March, so for a 29 February 2000 birth the Moon period that opens at birth closes on 1 March 2002, while the Ketu period that begins in 2020, a leap year, starts on 29 February itself.

Two dashas with the same nine lords

The numerology dasha borrows the vocabulary of the astrological Vimshottari Dasha - nine lords, main periods and sub-periods - but almost nothing else. The engine header calls it a parallel timing layer, and its Mahadasha-and-Antardasha shape was deliberately built to mirror the astrology engine's own, so the two can be read side by side. The table sets the differences out.

The numerology order is not arbitrary within its own system. It is the order of the numbers each lord rules in this app's numerology: the Sun rules 1, the Moon 2, Jupiter 3, Rahu 4, Mercury 5, Venus 6, Ketu 7, Saturn 8 and Mars 9, exactly as the Mulank table on the Numerology page assigns them. So the lord of each period is also its number, and its length in years is that number. A Mulank 5 person starts on Mercury, the lord of 5, for five years, then moves to the lord of 6 for six years, and so on round the circle.

Because the two systems start from different inputs and run at different speeds, they cannot be expected to agree about which lord is running, and usually they do not. The article on what a Mahadasha is explains the astrological idea the numerology system borrows its terms from.

The first round for every Mulank

Since the sequence and lengths are fixed and the first period is always complete, every person with the same Mulank passes through the same lords at the same ages. That means the whole first round - the first forty-five years - can be tabled once. The ages below are the age at which each lord's period begins, from a run of the engine for each Mulank.

Reading the table this way shows a few structural facts the calculator's timeline only implies. Saturn's eight years are always followed directly by Mars's nine, so every Mulank has a seventeen-year Saturn-then-Mars stretch in each round: from birth for Mulank 8, from age 28 for Mulank 1, and for Mulank 9, whose round opens on Mars, from age 37 running into the next Mars at 45. The three short periods - Sun, Moon and Jupiter, six years together - always follow Mars. And a person's age in the second round is simply the first-round age plus 45, since the round repeats exactly.

The timeline stops once at least a hundred years are covered, adding whole periods, so the last period can run past a hundred. In the engine run for each Mulank, the timelines covered between 100 years (Mulanks 1 and 9) and 107 years (Mulank 8), in 20 to 22 periods. These are artefacts of adding whole periods, not claims about a lifespan.

The book's own date, worked through

The engine was checked against Advanced Vedic Numerology's worked table for a birth on 1 April 1988 - Mulank 1, so the Sun opens with a full year to 1 April 1989. Run for this page, the engine gave this first round, every boundary on 1 April.

So on the day this page was written, 9 October 2026, the 1988 date was two and a half years into a nine-year Mars period. The same day, the calculator's sample, born in 1994 with Mulank 5, was also in Mars, from 2020; a 19 July 1996 birth with Mulank 1 was in Saturn, from 2024; and both a 1 November 1990 birth and a 1 February 1997 birth, Mulank 1 again, were in Saturn too, from 2018 and 2025. Same Mulank, different birth years, different points in the round.

The sample's timeline beyond the current period

For the calculator's own sample, born 14 August 1994 with Mulank 5, the engine's full timeline runs on from the current Mars period like this: the Sun from 14 August 2029, at age 35; the Moon from 2030; Jupiter from 2032; Rahu from 2035; and then, at age 45 in 2039, Mercury again, opening the second round exactly as the first opened at birth. The second round repeats the first lord for lord - Venus from 2044, Ketu from 2050, Saturn from 2057, Mars from 2065 - and the third begins with the Sun in 2074 and Mercury in 2084. The twentieth and last period the engine adds, Venus, runs from 2089 to 2095, taking the timeline to 101 years because whole periods are added until a hundred are passed.

Seen this way, the timeline is less a forecast than a calendar with nine repeating columns. What any period is taken to mean comes from outside the engine; what the engine guarantees is that the dates are the book's rule applied to your birthday, consistently, every time it is asked.

Sub-periods: the Antardasha the Numerology page adds

The calculator's own answers note that this page does not split a period into sub-periods, though the engine can. The Numerology page does. Each main period is cut into nine Antardashas, starting from the main period's own lord and running on in the same fixed order, each taking a share of the period equal to its lord's years over forty-five - the same proportional rule Vimshottari uses over 120. The split is in real calendar time, not in whole days.

The proportions produce some tidy results. A Mars period is nine years, so Mars itself takes nine forty-fifths of it, 1.8 years, and the Sun one forty-fifth, 0.2 years; together they are exactly two years. For the calculator's sample that put the end of the Sun sub-period on 14 August 2022, the second birthday of the period. Run for this page, the sample's Mars period divides like this.

Because every share is a fixed fraction, the length of any sub-period can be worked out for any main period without running the engine. The table gives each lord's fraction and what it comes to inside three main periods of different lengths. The one-year column is in days on a 365-day year; the engine itself splits the real span between two birthdays, so a leap year stretches each figure very slightly.

The last column will look familiar to anyone who has read the Personal Year page. The book's Pratyantar table gives the Sun 8 days up to Mars 72, eight days per year of dasha length, a 360-day year in all - exactly the one-year Antardasha proportions in whole days. That is why the engine comment calls the Pratyantar table identical to a one-year Mahadasha's own Antardasha, and why both are now split over the real year rather than laid end to end.

A short main period gives very short sub-periods. The Sun's one-year Mahadasha at the start of the 1988 timeline splits into nine pieces from about eight days for the Sun to seventy-two for Mars: the engine dated the Moon sub-period from 9 April 1988 and the Mars sub-period from 18 January 1989. At the other end, the seven-year Ketu period of the same timeline gives Ketu itself about thirteen months, from 1 April 2009 to 3 May 2010.

Below the Antardasha the Numerology page has one further level, the Pratyantar, which this app builds inside the birthday-to-birthday Vedic personal year rather than inside the Antardasha. The Personal Year calculator explains that year and its nine Pratyantar periods, and the article on Antardasha and Pratyantar explains the astrological original of the nesting.

Five people on one day

To see the levels together, the engine was run for five birth dates on 9 October 2026, reading the main period, the Antardasha within it and, from the Personal Year engine, the Pratyantar running that day. Four of the five share Mulank 1.

The table shows how little a shared Mulank fixes. Three Mulank 1 people are in Saturn Mahadashas, but one is near the end of it and about to enter Mars on 1 November 2026, one is two years in, and one began in February 2025. Two of them, born six months apart in 1996 and 1997, happen to share a Saturn-Mars combination at both upper levels on this day while differing at the third. The fourth Mulank 1 person, born in 1988, is a full round further on, in Mars. None of these coincidences means anything beyond the arithmetic; they are what a fixed nine-lord cycle anchored on birthdays produces.

Why the first period is whole

The calculator's introduction notes that this system opens with a complete first period where Vimshottari opens with a part period. The reason lies in the input. Vimshottari starts from the Moon's position within its nakshatra, a continuous quantity: a Moon a third of the way through the nakshatra has used up a third of the first lord's years before birth, and the rules document gives the formula for the balance that remains. The Mulank is not continuous. It is a whole number from the day of the month, with nothing inside it to say how far through the first period a person was born, so there is nothing to subtract. Advanced Vedic Numerology's worked table starts the 1988 example on a full Sun year at birth, and the engine follows it.

A practical consequence is that a numerology timeline can never be finer than its inputs. It knows the birth date and nothing smaller, so it dates its boundaries to the day and not to the hour, and two people born on the same day share a timeline exactly, wherever and whenever on that day they were born.

The same nine lords elsewhere in numerology

The lord-to-number pairing that orders this dasha runs through the rest of the app's Vedic numerology too, which is why the systems hang together. The Mulank's ruling planet on the Numerology page uses it. So does the weekday table that Advanced Vedic Numerology uses twice, for the Vedic personal year and for the hidden number: each weekday takes the number of its planet, Sunday the Sun's 1, Monday the Moon's 2, Tuesday Mars's 9, Wednesday Mercury's 5, Thursday Jupiter's 3, Friday Venus's 6, Saturday Saturn's 8. Rahu's 4 and Ketu's 7 have no weekday, so those two numbers can never come from a weekday.

The Hidden and Shadow Numbers calculator shows the weekday table at work on a birth date, and the Numerology Profile shows the Mulank's ruler beside the rest of the core reading. One number-to-planet assignment, in other words, drives the dasha's order, its period lengths, the Mulank's ruler and the weekday values. If the assignment were changed in one place and not the others, the readings would stop agreeing - which is why the engine keeps the dasha table as its own fixed constant rather than re-deriving it.

What the calculator returns, and in which language

Each period in the timeline carries five fields: the lord, a display label for the lord, its length in years, and its start and end as timestamps. The current period is the same object, picked out by checking which start and end straddle the moment of the request. The label is what a reader sees, and it is translated; the lord itself stays as an English planet name in every language. The engine comment explains why: other parts of the app read the lord back - the sub-period function looks it up in the fixed order, and the convergence check compares it with the astrological dasha lord - and a translated name would silently stop those comparisons matching.

This calculator does not take a language at all, and returns English labels. The Numerology page passes the reader's language, so the same timeline appears there in Hinglish or Hindi with the lord values unchanged underneath.

How this app sets the numerology dasha against astrology

The numerology dasha is one of four layers in the app's timing-convergence check, alongside the Vimshottari Mahadasha, the calendar personal year and the current Pinnacle. The check makes no new claim of its own. For the two dashas it assigns each lord a tone by a fixed rule the code says it shares with the AI engine: Jupiter, Venus, Mercury and the Moon are read as favourable, Saturn, Rahu and Ketu as testing, and the Sun and Mars as mixed, since classically they are neither one nor the other. It then counts how the rated layers lean.

One comparison is singled out. Because both dashas use the same nine lords, the check can ask a plain question: are the astrological and numerological Mahadashas ruled by the same lord right now? When they are, the headline says so, and calls it an alignment between two independent traditions. The code's comment describes the match as rare. It is a coincidence of two calculations from unrelated inputs - the Moon's nakshatra on one side, the day of the month on the other - and the app reports it as that, not as a stronger forecast.

The public Convergence page runs the same comparison forward over twelve months without an account, and the Timing feature shows both dashas inside a signed-in profile. Where the systems split, the article on when astrology and numerology disagree explains why the app shows the disagreement rather than resolving it.

Reading a numerology dasha period

The calculator above attaches no reading to any period, and says so. Nothing in this engine does either: the numerology dasha module computes lords and dates and stops there. The only place a lord is given a quality is the convergence check's three-way tone, which is a sorting rule rather than a description of what a period will hold. That restraint is deliberate. A table of dates is checkable; a paragraph about what a Saturn period brings is not, and the app would rather show the first than invent the second.

If you want the qualities numerology books attach to each number, they are on the number pages - for the lord of 8, the Number 8 page, and for the lord of 9, the Number 9 page - each with its sources. They describe the number, not a period of years, and the app does not stretch them to cover one.

What the timeline depends on, and what it does not

• It depends on the birth day only for its starting lord. A birth on the 5th, 14th or 23rd of any month starts on Mercury, so the order of lords is shared by everyone with the same Mulank.
• It depends on the full birth date for its calendar dates, since every boundary is a birthday. Two people with the same Mulank born in different years have the same lords at the same ages, on different dates.
• It does not depend on the birth time, the place, or the name. Nothing in the timeline moves if those change.
• It does depend on which calendar date you were born on, read as typed. The engine's date handling pins the date you enter to midnight UTC, so a pre-dawn birth in India is not moved to the day before - an error that once shifted the Mulank, and with it the starting lord, for births in that window.

The Mulank itself, and why the 29th of a month gives 2, is covered on the Life Path calculator. The rest of the reading the dasha belongs to is on the Numerology feature page.

Why might an older copy of this example show a boundary on the 13th?

Because it was computed before the engine was changed to date every boundary on the birth anniversary. The example above was regenerated on 12 October 2026 and gives the sample's Mars period as 14 August 2020 to 14 August 2029. The change followed the book's own worked table, which runs anniversary to anniversary.

How is this different from my Vimshottari dasha?

Almost everything but the names differs: the order of lords, their lengths, the total of 45 years against 120, the starting point - your Mulank against your Moon's nakshatra - and whether the first period is whole. The Vimshottari Dasha calculator needs a birth time; this one does not.

Do two people with the same Mulank have the same dasha?

The same lords at the same ages, yes. Everyone with Mulank 1 starts on the Sun and reaches Saturn at 28 and Mars at 36. Their calendar dates differ because each boundary is their own birthday.

How long is each sub-period?

Each lord takes its years over forty-five of the main period. In a nine-year Mars period that is 1.8 years for Mars and 0.2 for the Sun; in a one-year Sun period, about eight days for the Sun and seventy-two for Mars. The sub-periods are shown on the Numerology page, not on this calculator.

What does it mean when both my dashas share a lord?

The app's convergence check flags it because it is a directly comparable fact: both systems use the same nine lords. It is a coincidence of two unrelated calculations, and the app attaches no special forecast to it.

Which lord is favourable?

The engine itself rates none. The convergence check sorts lords into favourable, testing and mixed by a fixed convention - Jupiter, Venus, Mercury and Moon; Saturn, Rahu and Ketu; Sun and Mars - but that is a sorting rule for comparing layers, not a judgement of any period of your life.

At what time of day does the running lord change?

The boundaries are stored as the start of the birthday in UTC, and the current period is found by comparing them with the moment of the request. So the switch happens at 00:00 UTC on the birthday, which is 5:30 in the morning on India time, not at local midnight. The Personal Year calculator reads the reader's own calendar date instead, so on a birthday morning in India the two can briefly disagree about whether the new year has begun.

Why does the timeline run past a hundred years?

Because the engine adds whole periods until at least a hundred years are covered, and the last one is rarely an exact fit. Depending on the Mulank the timeline ends between 100 and 107 years after birth. The extra years are a by-product of the rule, not an estimate of anything.

I was born on 29 February. When do my periods change?

On 29 February in leap years and on 1 March in common years, because the engine rolls a missing anniversary to the next day. For a 29 February 2000 birth, the first Moon period runs to 1 March 2002.