Mahadasha, antardasha and pratyantar: period levels

One timeline, three levels of detail

Mahadasha, antardasha and pratyantar describe different sizes of period within the same dasha timeline. They are not three unrelated calendars. A mahadasha is the enclosing major period. Its antardashas are smaller periods inside it. Each antardasha can then contain pratyantars. For a family reading a chart together, the simplest question is, “Which larger period contains this smaller one?” That question keeps the structure clear before anyone discusses traditional interpretation. You can think of opening a folder, then a folder inside it, then another inside that. The contents become more specific, but the outer context remains attached to everything you open.

This guide explains the labels, order and proportions used for those three levels. It does not assign outcomes to particular combinations of lords. Astrology (jyotish) is a traditional interpretive practice; the observable calculation here is the division of a stored time span into smaller spans. Keeping those two matters separate helps you read a timeline without treating its arithmetic as proof of a prediction. If you are beginning with the wider subject, the Dasha guides provide the parent collection. Here, stay with one practical goal: identify the enclosing period, identify its child, and understand how the next child receives its share of time. Once that is comfortable, even a long label becomes manageable.

What each period name tells you

The word mahadasha identifies the major level. Antardasha identifies the next level inside a mahadasha. Pratyantar identifies the next level inside an antardasha. The planet attached to a level is its period lord. A lord name therefore needs a level or an enclosing path to be fully clear. “Venus period” could mean a Venus mahadasha, a Venus antardasha within another major period, or a Venus pratyantar within an antardasha. Before comparing two notes, establish which of those meanings the writer intended. This is a question of labelling, not a disagreement about the chart or about what someone expects to happen.

A useful reading habit is to name the container first and the contained period second. For example, say “Venus mahadasha, Venus antardasha” rather than simply repeating “Venus period.” When discussing the third level, include the antardasha as well. This may feel slightly formal at first, but it prevents confusion when the same lord appears at different depths. A repeated name does not merge the levels into one period. Each occurrence still has its own enclosing span and position in the hierarchy. In a notebook or family message, even a short heading that identifies the level can make a copied label much easier to understand later.

• Mahadasha names the enclosing major period.
• Antardasha names a child period within that mahadasha.
• Pratyantar names a child period within that antardasha.
• A lord name identifies the assigned planet, while the level identifies its place in the hierarchy.

Read a slash label from left to right

A slash label is a compact way to preserve the enclosing path. In Venus/Moon, Venus is the mahadasha lord and Moon is the antardasha lord. In Venus/Moon/Mars, Mars is the pratyantar lord within that Moon antardasha, which itself belongs to the Venus mahadasha. Read from the broadest span towards the smallest span. Do not read the names as three consecutive major periods. They describe periods that contain one another. When a label is copied without column headings, its number of names is a useful clue, but the original context should still confirm what the display intended.

The complete path matters because a final name alone does not identify a unique place in the timeline. A Mars pratyantar under one antardasha is structurally different from a Mars pratyantar under another. Likewise, Venus/Moon is not interchangeable with Moon/Venus. Changing the order changes which period contains which. No interpretation is needed to establish that difference. When checking a screenshot, read the label aloud in full before looking at dates. This small pause is particularly helpful when several relatives have sent cropped images with similar planet names. The table below shows how much information each label preserves and what still needs checking before you compare it with another entry.

Use the enclosing period as your starting point

Every subdivision needs a parent span. Here, parent means the immediately enclosing period, not always the mahadasha. When calculating an antardasha, its parent is the mahadasha. When calculating a pratyantar, its parent is the antardasha. This distinction is central to the arithmetic. If you use the mahadasha duration again while trying to find a pratyantar, you have skipped a level. The result would describe a share of the wrong container. Start by writing the parent label, its stored beginning and its stored ending together. Only then identify the child level you want to examine within that particular span.

For reading rather than calculating, the same approach works well. Find the larger entry first, then locate the smaller entry beneath it. Check whether the smaller entry is actually attached to that parent or merely appears nearby in a copied list. Indentation, headings and complete paths can help, but a screenshot may omit them. If the connection is unclear, return to the original timeline instead of guessing from a repeated lord name. This is especially important when several antardashas have their own lists of pratyantars. Each list starts from its own parent and should be read as a separate subdivision, even though the planetary weights remain the same throughout.

1. Identify whether you are examining an antardasha or a pratyantar.
2. Find its immediately enclosing period and retain that full label.
3. Record the enclosing span before checking the child's duration or dates.
4. Compare the child only with entries belonging to that same parent.

The Vimshottari weights total 120

Vimshottari uses the sequence Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn and Mercury. Their assigned years are 7, 20, 6, 10, 7, 18, 16, 19 and 17 respectively. Together they total 120. These numbers do two jobs in this guide. They identify the theoretical major period weights, and they provide the proportions used to subdivide an enclosing span. A lord with an assigned weight of 20 receives 20/120 of the parent span when that parent is split. The number is not a statement that every appearance of that lord lasts 20 calendar years.

Keep the whole set of weights available rather than remembering only the planet you are currently reading. The complete set explains why nine children can fill one parent span: their shares total 120/120. It also explains why the children are not normally equal in duration. An equal division into nine would ignore the assigned weights. At the antardasha and pratyantar levels, use the same weight for a given lord, but apply it to a different parent span. The table is therefore a reference for both levels, not a separate timetable for each. Its last column reminds you what must change when you move deeper into the hierarchy.

Child order begins with the parent lord

Within a parent period, the child sequence begins with the parent's lord. It then continues through the Vimshottari sequence and wraps around when necessary. In a Venus mahadasha, the antardasha sequence begins with Venus, followed by Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury and Ketu. Ketu is last in this particular list because the list began at Venus rather than at Ketu. The underlying sequence has not changed. Only its starting point has moved. This is why a reference list beginning with Ketu should not be copied unchanged beneath every mahadasha.

The same principle applies one level deeper. Within a Moon antardasha, the pratyantar sequence begins with Moon, regardless of which mahadasha contains that antardasha. Continue from Moon through the sequence, then wrap around until all nine lords have appeared. The immediate parent's lord controls the start at each subdivision. A practical way to check your work is to write the nine names in a circle and place your finger on the parent lord. Move forward until you have included each name once. This checks order only; it does not assign dates or interpret outcomes. You still need the parent span and each lord's weight to determine the sizes of those ordered children.

Subdivision changes the span, not the weights

The basic rule is child span equals parent span multiplied by the child lord's assigned years divided by 120. At KismatAstro, antardashas and pratyantars recursively split the stored date span using this rule. Recursively means that the same method is applied again to the smaller span produced at the previous level. The input container changes, but the set of planetary weights does not. First divide a mahadasha span to obtain antardashas. Then divide a chosen antardasha span to obtain its pratyantars. This is a structural calculation and should be understood separately from any traditional meaning assigned to the resulting labels.

The parent span is the interval represented by its stored beginning and ending, not necessarily the full theoretical duration associated with the parent lord. That distinction is easy to miss when a chart begins partway through a major period. If you are checking an actual site timeline, use its stored parent interval as the basis of the subdivision. If you are learning with an ideal full period, clearly call it a theoretical example. Both exercises can teach the hierarchy, but they answer different questions. One asks how an existing interval is divided; the other asks what the proportions would be within a complete ideal period before any birth balance clipping or date rounding enters the picture.

• The divisor remains 120 at both subdivision levels.
• The child lord supplies the proportional weight.
• The immediate parent supplies the interval being divided.
• Moving to pratyantar means applying the rule to an antardasha, not directly to the mahadasha.

A hypothetical full Venus period

Take a hypothetical full Venus mahadasha of 20 years. This is an illustration of proportions, not a dated birth chart (janam kundli). Its Venus antardasha receives 20/120 of the full major period. The theoretical calculation is 20 × 20/120 = 10/3 years. The result belongs to the second level, so its complete label is Venus/Venus. Notice that the second Venus does not create another 20 year major period. It names the child receiving the Venus share inside the original major period. Keeping the label beside the fraction makes the role of each repeated name easier to follow.

Now subdivide that hypothetical Venus antardasha. Its Venus pratyantar receives 20/120 of the antardasha span, giving 10/3 × 20/120 = 5/9 years. Its full label is Venus/Venus/Venus. These fractions demonstrate repeated proportional subdivision without requiring a calendar convention or a birth date (janam tarikh). Do not turn them into claimed dates for a real person, and do not assume that a stored Venus interval necessarily represents the complete 20 year theoretical span. The purpose of the example is narrower and more useful: you can see that each deeper level uses the result of the previous level as its parent. Repeated Venus names preserve the same weight while the container becomes smaller at each step.

Order and duration answer different questions

The sequence tells you which child follows which. The weight tells you how much of the parent each child receives. These are separate pieces of information, and both are necessary. Knowing that Venus starts a Venus mahadasha's antardasha list does not tell you its endpoint by itself. Knowing that Venus has weight 20 does not tell you where its interval begins within every possible parent. The starting lord determines the rotated order. The stored parent span and the proportional weights determine the subdivision sizes. Keep these tasks separate when checking a hand copied timeline, because an error in one can be hidden by correct information in the other.

For example, a list can contain all nine correct lords yet begin with the wrong one. It can also begin correctly but mistakenly allocate equal shares. Neither list follows the specified method completely. Review the names first, then review the proportions, rather than trying to judge everything from the visual length of rows. Printed layouts and mobile screens may give equal space to periods of unequal duration. A row's height is not a time measurement. When explaining this to someone at home, use the simple distinction “order is the queue, weight is the share.” That keeps the method approachable without turning the labels into claims about favourable or unfavourable experiences.

How stored boundaries become child boundaries

For an actual stored interval, subdivision begins at the parent's stored start. Children are arranged in the appropriate lord sequence, and their proportional spans are accumulated in that order. Each child's ending becomes the boundary from which the next child proceeds. The process is repeated inside an antardasha when pratyantars are computed. This explains why the enclosing start and end matter as much as the lord names. Names tell you the structural path, while stored boundaries tell you which interval that path occupies. A label copied without its boundaries is useful for identifying the level, but it is insufficient for checking the actual dated subdivision.

KismatAstro sets the last child's ending to the parent's ending. That rule keeps the completed subdivision aligned with its enclosing span. When reviewing dates, check this final alignment rather than expecting separately rounded proportional calculations to reproduce every displayed boundary exactly. The closing child is still part of the same ordered subdivision; its endpoint is explicitly anchored to the parent. You do not need to invent an extra interval to fill a small apparent remainder from a hand calculation. Instead, distinguish the proportion rule from the handling of the final stored endpoint. Together, these explain how the sequence is kept within one complete parent interval in the site's calculation method.

1. Begin with the stored start and end of the immediate parent.
2. Arrange the nine children beginning with the parent lord.
3. Apply each child's weight to the parent span and accumulate the boundaries in order.
4. Confirm that the final child's ending matches the parent's ending.

Read stored UTC dates with care

The site uses stored UTC date strings for these intervals. UTC identifies the time reference of the stored values. An Indian reader should therefore avoid assuming that a stored date string is already an Indian local date or time. Preserve the original string when comparing records. If another source presents a local calendar date, first establish what each representation means before deciding that the timelines disagree. This guide does not supply a conversion rule or claim a particular display format. Its practical point is simpler: a stored boundary and a casually rewritten date are not automatically the same piece of evidence.

When sharing a period with a family member, keep the full label and the original date representation together. Removing a time reference or shortening a boundary can make two otherwise matching records look different. It can also hide which exact parent interval was used for the subdivision. For a careful comparison, retain the start and end rather than only the month or year. If you need to understand why dated outputs differ across tools, use the Dasha date comparison guide. That topic is separate from learning the hierarchy. Here, the important skill is recognising that the same nested label may need additional date context before it can be compared responsibly with another timeline.

Birth balance can shorten the available parent

A timeline beginning at birth need not begin at the start of a complete theoretical mahadasha. The available parent interval can reflect birth balance clipping rather than the lord's full assigned duration. This matters because the site's child calculation divides the stored parent span. A clipped span and a full theoretical span are different inputs, even if both carry the same major lord's name. You should not replace the stored interval with the lord's full assigned years merely because the label looks familiar. Doing so changes the question from “How is this recorded interval divided?” to “What would a full ideal period contain?”

The hypothetical Venus example therefore remains a teaching example, not a shortcut for reconstructing every Venus entry in a real timeline. Before applying its fractions to actual dates, establish whether your parent is complete or clipped and whether you are using stored boundaries. Date rounding can also make a displayed result differ from a clean theoretical fraction. These issues do not alter what mahadasha, antardasha and pratyantar mean. They affect the interval to which the proportional rule is applied or how its boundaries are represented. A helpful note beside your working is “stored parent” or “full theoretical parent.” That small distinction prevents much confusion without requiring you to resolve every calendar question while learning the period levels.

Keep calculation separate from traditional interpretation

A hierarchy explains where a period sits, not what it guarantees. Traditional astrology (jyotish) may interpret a lord combination, but this guide does not turn a sequence or a fraction into a prediction. The fact that an antardasha receives a stated proportion is a mathematical feature of the method. It is not evidence that a particular family event must occur during that span. Likewise, a shorter pratyantar is not automatically a more certain forecast. It is simply a more deeply nested interval. Reading the label accurately is useful even when you choose not to make any interpretive claim about it.

For traditional textual context, the supplied Phaladeepika text and translation on Wisdom Library is a reference to consult alongside this explanation. Keep traditional discussion distinct from the site's implementation details, such as stored UTC strings and final child endpoint handling. Those implementation details describe how this timeline is organised; they should not be presented as quotations from a classical source. In conversation, use modest wording such as “this is the period label in the traditional system.” There is no need for fear, certainty or dramatic conclusions. A family can understand the full nested structure while leaving questions about personal meaning open and avoiding assumptions about anyone's future.

Avoid the most common label mix ups

Many reading errors arise from missing context rather than difficult arithmetic. One person says “Moon is running,” while another points to a Venus heading. Both may be referring to different levels of the same path. Before deciding that the records conflict, ask whether Moon is the antardasha and Venus is the mahadasha. Another common error is reversing a path while retelling it. Venus/Moon and Moon/Venus contain the same names but do not describe the same nesting. Copy the order exactly, especially when translating a spoken explanation into a written message. The first name is the outer level, not whichever planet someone wishes to emphasise.

Repeated names can cause the opposite problem. A reader sees Venus/Venus/Venus and assumes that the label is redundant. It is not: each name belongs to a different level. Keep all three when the third level is actually the subject. Also avoid treating a standalone date as proof of a level. The same boundary can be shared by a parent and its first child, so a matching start does not make them the same interval. Compare both the complete path and the span. These checks are practical safeguards for reading information accurately, not rules for interpreting combinations or deciding which lord is more important in a person's life.

• Do not drop the enclosing names when identifying a pratyantar.
• Do not reverse the order of names in a slash label.
• Do not mistake repeated lord names for a single repeated period.
• Do not use a shared starting boundary as proof that two levels are identical.

Use the timeline without assuming extra features

The Free dasha timeline is the existing destination for working with the site's timeline. This educational page explains how to understand the period hierarchy and the stated subdivision method. It does not replace that tool or promise that every concept discussed here appears as a visible interface feature. In particular, explaining how pratyantars are computed does not establish that a current pratyantar is shown. Keep the distinction between a calculation method and a displayed selection clear. A reader should describe only the entries and labels actually available in the output they are examining.

The scope here ends with mahadasha, antardasha and pratyantar. Do not infer that a fourth level is computed because the proportional rule can be described recursively. A general mathematical pattern and a site's implemented features are different matters. When taking notes from an output, record what you can verify rather than adding imagined columns or deeper periods. If you want to learn the third level using a hypothetical example, you can do so on paper without claiming the interface displayed it. This approach keeps the guide useful and honest. You gain the conceptual understanding needed to read nested periods while avoiding assumptions about current highlighting, automatic selection or additional depths that have not been established.

Check reference material by the question it answers

Different references serve different reading tasks. A traditional discussion may help you understand dasha terminology, while a site's implementation description explains which stored interval is subdivided. The supplied VedicPupil dasa library is another reference for the traditional subject. Use such material with a specific question in mind, such as identifying the names of levels or checking the sequence being discussed. Do not assume that every reference uses the site's stored date handling. Equally, do not present a site calculation rule as though it settles every issue in traditional interpretation. Keeping the question narrow makes reference checking more productive.

For this page, the questions are deliberately limited: what contains what, where the child sequence begins, and how each child receives its proportional share. Differences in dasha year conventions belong to the existing comparison guide rather than being expanded here. Meanings attributed to named lord combinations belong to their own interpretive discussions. This boundary is helpful for readers, not a missing piece of the explanation. You can fully understand the hierarchy without choosing between calendar conventions or reading a prediction for every combination. When a source introduces another topic, note that change of scope and return to the task you were checking. A tidy separation between terminology, arithmetic, dates and interpretation makes the whole subject less intimidating.

Build a clear note for your own reference

A good personal note should let you reconstruct the nesting without relying on memory. Begin with the full path, then name the level you are examining. Add the immediately enclosing path and preserve its stored start and end if you are working from actual output. Record whether the exercise uses a stored interval or a hypothetical full period. This small amount of context is more valuable than a page of isolated planet names. It allows you to return later and see exactly which container supplied the span and which lord supplied the weight. It also makes discussion with family members more straightforward.

When checking the note, read it in two directions. From left to right, the path should move from mahadasha to antardasha to pratyantar. From the smallest interval outward, each child should belong to the parent you recorded. Then inspect the order of siblings separately from their durations. If your note includes dates, preserve their UTC context rather than quietly rewriting them as local dates. If it includes theoretical fractions, label them hypothetical instead of attaching them to a real person's chart. You do not need extra interpretive language to make the note useful. Accurate structure, a clear basis for the span and faithful boundaries are enough for the educational task covered here.

1. Write the complete path and explicitly name the level under review.
2. Identify the immediate parent and whether its span is stored or hypothetical.
3. Check the starting lord, sequence and proportional weight separately.
4. Preserve original date strings or clearly labelled theoretical fractions in your final note.

Bring the three levels together

You can now read the hierarchy as one connected structure. A mahadasha supplies the outer interval. Its antardashas begin with its lord and follow the planetary sequence, taking shares based on the assigned years divided by 120. Each antardasha can be subdivided by the same method to obtain pratyantars, beginning this time with the antardasha lord. The weights stay constant, while the immediate parent changes. For stored site intervals, the calculation uses the stored date span and fixes the last child to the parent's end. These points explain the structure without requiring a prediction or a real dated example.

When a label feels confusing, return to three questions: which level is this, what contains it, and which span is being divided? Those questions usually reveal whether you are looking at a naming issue, a proportional calculation or a date comparison. Keep the hypothetical full Venus example for understanding fractions, and keep actual stored boundaries for checking an actual timeline. Neither needs to be forced into the role of the other. Most importantly, treat the system as a traditional framework rather than a fixed account of anyone's future. With the enclosing path intact and the calculation basis clear, you can discuss mahadasha, antardasha and pratyantar calmly, accurately and without making the subject heavier than it needs to be.

Frequently asked questions