Vimshottari Janma Dasa: how to use it, and how we check its accuracy

1. Choose the Moon-based system deliberately

Janma means the starting nakshatra is the one occupied by the Moon at birth. Its ruling planet supplies the first Mahadasa. The part of that nakshatra already traversed by the Moon determines how much of the first period has already elapsed.

Raman teaches this method in Hindu Predictive Astrology, chapter XII, and explicitly argues for the Moon-based start in My Experiences in Astrology. Rath defines Janma in section 5.3.1 of Vimsottari & Udu Dasas, while also discussing a strength comparison among Janma, Lagna and Utpanna. These are different starting choices. [1, 2, 4]

Use the period as a timing framework

In Raman’s interpretive method, start with a topic in the natal chart: for example, the seventh house for marriage. Examine the relevant planets’ house ownership, placement, associations and strength, then inspect their Mahadasa, Bhukti and finer periods. His chapter XXIV also considers aspects, Navamsa and transits, and cautions against applying general planetary descriptions mechanically. A running lord alone does not establish that a specific event must occur. [1, pp. 140–142]

1. Identify the chart factors relevant to your question.
2. Read the running Mahadasa and Bhukti together; request level 3 when a finer period is useful.
3. Compare the lords’ natal condition and the relevant transits before interpreting the window.
4. Keep the birth data, Ayanamsa, starting system and year convention consistent when comparing charts or software.

2. Learn the repeating 120-year sequence

The following cycle can be entered at any lord. The birth nakshatra determines that entry point; it does not always begin with Ketu. After Mercury, the sequence returns to Ketu. Both books give the same planetary allotments. [1, pp. 52–53; 2, §5.4.1]

3. Reproduce Raman’s birth-balance example

On printed page 54 of Hindu Predictive Astrology, the Moon is at Taurus 25°10′. Mrigashira begins at Taurus 23°20′ and belongs to Mars. The Moon has traversed 1°50′, or 110 arcminutes, out of the nakshatra’s 800 arcminutes. This is a supplied-longitude example; it does not supply a complete dated birth chart. [1]

The half-day difference is the book’s rounding. The corresponding test retains that difference and permits half a day plus a tiny numerical epsilon; it does not change the printed answer.

A Dasa year needs an explicit convention

The conversion above uses Raman’s tabular convention of 360 days per year and 30 days per month. Rath’s final Q3 defines the year through the Sun’s sidereal revolution. 360 degrees of solar motion is not 360 elapsed days. Changing the year convention changes dated boundaries even when the planet sequence and angular birth fraction agree. [1, pp. 55–58; 2, p. 247]

For Janma, VedAstro’s BySystem default resolves to Fixed360Days. Pass TrueSiderealSolar explicitly for Moon-started timing based on actual sidereal solar motion. Ayanamsa affects the zodiac positions; it does not choose the Dasa year length.

4. Divide each period proportionally

Each full Mahadasa contains nine Bhuktis, also called Antardasas. The first belongs to the Mahadasa lord, and the remaining lords follow the same cycle. Each Bhukti takes its lord’s share of 120. The same procedure repeats inside a Bhukti for level 3. [1, pp. 55–57; 2, §§5.4.2–5.4.4]

Raman’s table prints Moon/Jupiter as 1 year, 4 months, 0 days. His worked Ketu/Saturn/Jupiter example gives 1 month, 23 days, 4.8 hours: exactly 53.2 days with 30-day months.

5. Proof of accuracy: the checks and their limits

For this article, “accuracy” means reproducible agreement with specified book calculations. It is not a measured prediction-success rate. We reran the 124 Raman source cases on 25 October 2026: 120 passed and 4 failed. All 113 arithmetic cases passed; the full-chart group had 7 passes out of 11.

What the passing arithmetic cases check

The tests cover all 27 nakshatra-to-lord assignments, 77 unambiguous printed Bhukti durations, worked birth balance and third-level timing, five printed lunar-longitude balances, and selected narrative timing examples. Expected values come from the books rather than from the calculation under test.

These five checks begin with the printed Moon longitude. They verify period arithmetic, not the separate process of reconstructing that longitude from a historical birth time. The allowance is half a day of printed rounding plus the Dasa equivalent of one arcsecond of angular conversion.

Where full-chart calculations still disagree

The expected results and narrow tolerances remain unchanged. These results distinguish a correct proportional-period calculation from unresolved differences in natal positions or historical inputs. They do not establish which input or astronomical assumption should be changed.

6. Request Janma periods through the API

Install the Python client with pip install vedastro. This example requests a two-level timeline from the public API. The 1918 Bangalore birth is the documentation’s sample input, separate from the book’s supplied-longitude example above.

from vedastro import Calculate, Time, GeoLocation

Calculate.SetAPIKey("FreeAPIUser")
Calculate.SetAyanamsa("RAMAN")
Calculate.base_url = "https://vedastro.zaishi.net/api/Calculate"

location = GeoLocation("Bangalore", 77.5833, 12.9667)
birth = Time("14:20 16/10/1918 +05:30", location)
start = Time("00:00 01/01/2026 +05:30", location)
end = Time("00:00 01/01/2027 +05:30", location)

result = Calculate.DasaAtRange(
    birth, start, end, "VimshottariJanma",
    levels=2, yearConvention="Fixed360Days"
)

parents = {p["Id"]: p for p in result["Periods"]}
for period in result["Periods"]:
    if period["Level"] == 2:
        major = parents[period["ParentId"]]["Lord"]
        print(major, period["Lord"], period["Start"], period["End"])

The saved response for these inputs contains a Mars Mahadasa throughout the requested 2026 range, with Jupiter Bhukti followed by Saturn Bhukti at approximately 05:20 on 15 June 2026, +05:30. That is a software example, not an independently sourced historical prediction.

Read ResolvedSeed, StartingLord and YearConvention to confirm the calculation you requested. Root periods have ParentId=null; children reference a parent’s response-local Id. Results are clipped to your interval, so the returned Start may be later than a period’s natural beginning. Request from birth if you need the full birth balance.

Use DasaAtTime for one moment, DasaAtTimes for several moments and DasaForLife for a timeline from birth. These Dasa calls compute boundaries directly. The Events and LifePredictor paths retain their separate time-slice evaluation.

Book sources and further reading

1. B. V. Raman, Hindu Predictive Astrology. Chapter XII, printed pp. 52–58: nakshatra ownership, birth balance, Bhukti table and worked Antara. Chapter XXIV, printed pp. 140–142: interpreting periods through the natal chart. Page numbers refer to the printed book, not the OCR wrapper.
2. Sanjay Rath, Vimsottari & Udu Dasas. Sections 5.3–5.4, printed pp. 80–83: starting nakshatras and proportional subdivisions. Final Q3, printed p. 247: the solar-year definition. Janma and the strongest-seed selection are kept explicit rather than blended.
3. B. V. Raman, Notable Horoscopes. Entries 27, 36, 41, 58 and 59 supply the printed longitudes and balances shown above. Historical birth reconstruction and supplied-longitude arithmetic are tested separately.
4. B. V. Raman, My Experiences in Astrology. Discussion with N. C. Lall and Raman’s conclusion favoring the Moon’s nakshatra; supplied OCR lines 4881–4904. The memoir also supplies the approximate Col. Skipwith Saturn timing and Raman’s Rahu/Venus consultation narrative used in the test suite.

Explore the other supported Dasa systems →