Skip to main content
  • AstroZiviVedic Astrology
  • New Kundli
  • Today
  • All Tools
  • Technique Index
  • Kundli
  • Divisional Charts
  • KP System
  • Varshphal
  • Synastry
  • Dashas
  • Strength
  • Yogas
  • Jaimini
  • Doshas
  • Horoscope
  • Transits
  • Event Forecast
  • Panchang
  • Muhurta
  • Festivals & Calendar
  • Moon Phase
    New
  • Matching
  • Numerology
  • Remedies
  • Nadi
  • Baby Names
Event Forecast
  1. AstroZivi
  2. Event Forecast
AstroZivi

All calculations are performed in-house with Lahiri (Chitrapaksha) ayanamsha, accurate to a fraction of an arc-second. No paid APIs required.

Charts & Analysis

  • Kundli
  • Divisional Charts
  • Dashas
  • Strength
  • Matching

Panchang

  • Panchang
  • Muhurta
  • Festivals
  • Horoscope

Company

  • All Tools
  • Reports
  • Learning Center
  • Privacy Policy
  • Terms of Service
  • Contact
  • Refunds

© 2026 AstroZivi. All rights reserved.

Powered by the Ganita engine
TodayKundliToolsMantrasProfile

Event Forecast

Multi-decade forecast walking your dasha periods with transit windows.

Birth Details
Forecasts future life-event windows from dasha & transits

What the forecast actually computes

This tool walks your Vimshottari dasha tree down to the antardasha level and evaluates every future sub-period inside the horizon you choose, using that period's own two dasha lords together with the positions of Jupiter and Saturn at the middle of the period. For each event type it keeps the strongest windows and reports them as date ranges with your age across them and the two lords whose period they are. The horizon can run from one to sixty years and the page starts at twenty.

The method is the double transit and dasha combination used in modern Indian practice, and it is named as modern practice rather than presented as a verse.

The classical components inside it are cited where they exist: the Vimshottari tree, the ashtakavarga bindus of BPHS ch. 66, and the full drishtis, which here means the seventh for every graha plus Mars on the fourth and eighth, Jupiter on the fifth and ninth, and Saturn on the third and tenth. The way those components are combined into one number is this application's own construction, and the next section says so plainly.

The four inputs, and what each one can contribute

Every window is assessed on four inputs with fixed caps. The dasha connection contributes up to 30 points and asks whether the mahadasha and antardasha lords connect, by occupation, aspect or lordship, to the houses and karakas the event is read from. The double transit contributes up to 30 and asks whether Jupiter and Saturn, at the midpoint of that period, activate the event's primary houses reckoned from the lagna, from the Moon and from the Sun.

Ashtakavarga support contributes up to 20 and reads the sarvashtakavarga total of the event's primary house, with 30 or more bindus counted as strong, 25 or more as good and 20 or more as adequate.

Natal promise contributes up to 20 and looks at whether the event's natural karaka and the primary house lord stand in exaltation, own sign or moolatrikona, whether the karaka is combust, whether the house lord is vargottama, and whether the relevant Jaimini chara karaka connects to those houses. The four caps add to 100, which is where the percentage comes from.

The percentage is this application's composite, not a classical quantity

No classical text weights a dasha connection against a double transit, or either of them against an ashtakavarga total or a natal dignity.

The 30 / 30 / 20 / 20 split is this application's own, and the labels attached to the total are a threshold table rather than a verse: 70 and above reads very likely, 50 and above likely, 30 and above possible, and anything lower unlikely. Those bands order windows; they are not a probability in the statistical sense and they are not a promise.

This matters most when a number would be least appropriate, which is why the same forecast is stripped of its percentage and its classification when it is reused on the health page. There, only the window's dates, the age span and the two dasha lords survive the crossing, because those are facts about the Vimshottari tree while the number is an ordering device. On this page the number is shown, because the page is about ranking windows and hiding the criterion would be worse than showing it.

Nine events by default, and a tenth behind a gate

Nine event types are forecast for every chart: marriage or partnership, career breakthrough, children, education, wealth gain, foreign travel or relocation, property, spiritual growth, and legal matters. Each is defined by its primary houses, its secondary houses, its natural karakas, a relevant Jaimini chara karaka where one applies, and a divisional chart used for confirmation, and each of those definitions is visible in the reading rather than hidden in the score.

A tenth type, a health-shaped window, is computed only when you explicitly ask for it. It reads the sixth and eighth houses against maraka dashas, which puts it in the same class as the other sensitive techniques in this app, and all of those sit behind consent. Handing someone an unrequested health window on page load is exactly what that gate exists to prevent, so it ships opt-in rather than either shipping unannounced or being quietly dropped.

Which windows survive, and what a window is not

Not every period is shown. For each event the tool keeps only windows scoring 45 or more and then keeps at most the five strongest of those, so an event with no qualifying period in your horizon shows nothing rather than showing its least bad option. The combined timeline is stricter still: it takes windows scoring 55 or more across all events and shows at most twelve. An empty tab is therefore information, not a failure.

A window is an antardasha, bounded by the Vimshottari tree, not a date on which something happens. Its edges are dasha boundaries, so they move if your birth time moves; a shifted birth time shifts the whole tree. The tool names no dates for events, gives no guarantee that an event occurs in a window, and offers no muhurta: choosing a date is a different technique with a different engine, and it has its own pages on this site.

Frequently asked questions

What does the event forecast do?
It walks your Vimshottari dasha tree down to the antardasha level and assesses every future sub-period within your chosen horizon, using that period's own two dasha lords and the positions of Jupiter and Saturn at the midpoint of the period. For each event it reports the strongest windows as date ranges, with your age across them and the two lords whose period they are. The horizon can be set anywhere from one to sixty years.
What does the percentage next to a window mean?
It is this application's own composite of four inputs with fixed caps: the dasha connection up to 30 points, the double transit up to 30, ashtakavarga support up to 20, and natal promise up to 20, adding to 100. No classical text weights those four against each other, so the split and the labels are this app's construction rather than a verse. The bands are 70 and above very likely, 50 and above likely, 30 and above possible, below that unlikely. They order windows; they are not a statistical probability.
Which events are forecast?
Nine by default: marriage or partnership, career breakthrough, children, education, wealth gain, foreign travel or relocation, property, spiritual growth, and legal matters. Each is defined by its primary and secondary houses, its natural karakas, a Jaimini chara karaka where one applies, and a divisional chart used for confirmation. A tenth, health-shaped event type exists but is computed only when you explicitly opt in.
Why does an event show no windows at all?
Because no period in your horizon met the threshold. For each event the tool keeps only windows scoring 45 or more and then at most the five strongest of those, and the combined timeline is stricter still at 55 or more with at most twelve rows. An event with nothing to show is therefore reporting that honestly rather than filling the tab with its least bad period. Widening the horizon can bring further periods into range.
What is the double transit method?
It asks whether Jupiter and Saturn together activate the houses an event is read from. In this tool their positions are computed for the midpoint of each antardasha, and activation is checked from the lagna, from the Moon and from the Sun. Only full drishtis count, meaning the seventh house for every graha plus Mars on the fourth and eighth, Jupiter on the fifth and ninth, and Saturn on the third and tenth, so a partial aspect does not quietly widen the connection.
Is a window a prediction that the event will happen on those dates?
No. A window is an antardasha bounded by the Vimshottari tree, and its edges are dasha boundaries rather than event dates. The tool states which period scored highest for an event and why, using four named inputs. It does not guarantee an occurrence, does not name a date within the window, and does not choose an auspicious date; that last is muhurta, a different technique with its own pages on this site.
Why is there no health window unless I ask for it?
Because it reads the sixth and eighth houses against maraka dashas, which places it with the other sensitive techniques in this app, all of which sit behind explicit consent. Showing an unrequested health-shaped window the moment a page loads is exactly what that gate prevents. When the health page reuses this forecast it also strips the percentage and the classification, keeping only the window's dates, the age span and the two dasha lords.
Does the accuracy of my birth time matter here?
Yes, more than on a page that only reads houses. Every window edge is a Vimshottari dasha boundary computed from the Moon's exact longitude at birth, so a shifted birth time shifts the whole tree and every date with it. The whole-sign house placements underlying the event definitions are more forgiving, since they change only when the lagna changes sign, roughly every two hours.