Put the same date, time and place into two apps and the kundlis can disagree: a different rising sign, planets in different houses, Mahadasha dates months apart. Usually neither app has made an arithmetic slip. They read a slightly different birth moment, or made a different choice about a convention, and your chart happened to sit near a line where that choice shows.
There are seven causes worth knowing: the time zone, the place, the ayanamsa, the house system, the node, the chart style and the length of a dasha year. This page sizes each one on a single chart with this app's engine. If only your nakshatra or pada differs, that is a narrower question with its own page: why two apps give you two different nakshatras.
The test chart
Every figure below comes from one birth: 15 August 1990, 10:30 India time, New Delhi. Anyone can enter it in the birth chart calculator. This app puts the ascendant at 178.71 degrees, the last degree and a quarter of Virgo, in Chitra pada 2. The Moon is at 48.92 degrees, Taurus, Rohini pada 3, in the 9th house; the Sun is in the 11th and Saturn in the 4th.
That ascendant is the reason this chart is a good test. Virgo rose that morning from 08:20 to 10:36 India time, 136 minutes in all, and the birth sits six minutes before Libra rises. Most charts are not this close to a line; this one shows what happens when one is.
Cause 1: the time zone and summer time
An app turns your clock time into a universal instant using a time zone. If it picks the wrong zone, or misses a summer-time hour, it computes a different moment. The ascendant (lagna) is the fastest-moving point in the chart, so it shows the error first.
| Birth time read as | Ascendant | Moon | Moon in house | Moon Mahadasha ends |
|---|---|---|---|---|
| 09:30 (one hour early) | 165.54, Virgo, Hasta 2 | Rohini 3 | 9th | 17 May 1994 |
| 10:30 (as given) | 178.71, Virgo, Chitra 2 | Rohini 3 | 9th | 5 December 1993 |
| 10:34 (four minutes late) | 179.59, Virgo, Chitra 2 | Rohini 3 | 9th | 24 November 1993 |
| 11:30 (one hour late) | 191.74, Libra, Swati 2 | Rohini 3 | 8th | 26 June 1993 |
One hour late is enough to make Libra the ascendant. Because this app counts houses from the rising sign, every planet then moves back one house: the Moon from the 9th to the 8th, the Sun from the 11th to the 10th, Saturn from the 4th to the 3rd. The Moon stays in Rohini pada 3, so the dasha sequence is the same, but the Moon has moved half a degree further through Rohini and every Mahadasha boundary arrives about 163 days earlier. Four minutes alone moves those dates by about 11 days.
This app's calculators use the time zone of the birth place they resolve, which carries that date's summer-time rule, and assume India Standard Time only when no zone can be found. With no birth time at all they read 12:00 noon. What a missing birth time costs covers that case, and how accurate a birth time needs to be gives the rate for each part of the chart.
Cause 2: the place and its coordinates
The planets do not depend on where you were born in this engine, only on when. The ascendant and the houses do. Typing the nearest big city, or picking a town of the same name in another state, moves them.
| Place used, same instant | Ascendant | Change from New Delhi |
|---|---|---|
| New Delhi (28.61 N, 77.21 E) | 178.71, Chitra 2 | - |
| Half a degree further east | 179.15 | +0.44 degrees |
| Half a degree further north | 178.63 | -0.09 degrees |
| Mumbai (19.08 N, 72.88 E) | 176.31, Chitra 1 | -2.40 degrees |
Mumbai and New Delhi share India Standard Time, so the same clock time is the same instant, yet the ascendant moves 2.4 degrees and its pada changes. Longitude matters more than latitude here: half a degree east moved the ascendant almost five times as far as half a degree north.
Cause 3: the ayanamsa
A sidereal chart is a tropical chart minus one number, the ayanamsa. This app uses Lahiri alone; at this birth it is 23.7221 degrees. Another ayanamsa slides every point in the chart, all ten of them, by the same amount. A gap of D arcminutes changes the sign of a point only when the point sits within D arcminutes of a sign line: D/1800 of positions, so 10 arcminutes affects about 0.56% of points per point. The ayanamsa calculator shows this app's value for any date.
This engine computes no other ayanamsa, so this page gives no KP or Raman figure; Lahiri, KP and Raman compared is where those are discussed. Advanced Predictive Astrology Vol. II says in its preface that its author "followed Lahiri Ayanamsa only", and that its Navamsa positions did not change when the Krishnamurthy ayanamsa was used in its illustrations.
Cause 4: the house system
This app uses whole-sign houses: the rising sign is the whole 1st house, the next sign the 2nd, and so on. Other apps draw house cusps at computed degrees, so a planet early or late in a sign can fall in a different bhava from the one its sign suggests. This engine computes no cusp-based system, so this page cannot give you the size of that difference for the test chart.
BPHS does not settle the question for you. Ch. 11 Sl. 2 reads the first house through "the ascending Rāśi", a sign-based reading. Ch. 4 Sl. 25-30 speaks of the "Lagn Bhava (Madhya, or cusp)" and the cusp of the 9th Bhava. Whole-sign vs Placidus houses sets out what changes between the two.
Cause 5: the node
Rahu and Ketu can be the mean node, a smooth average, or the true node, which swings around it. This app uses the mean node everywhere, with Ketu exactly opposite. At the test birth the true node sat 0.83 degrees from the mean; checked daily through 2026, the gap reaches 1.73 degrees. Mean Rahu here is at 282.76 degrees, mid-Capricorn, so the sign does not change; a Rahu near a sign line would. Mean vs true node explains where it matters.
Cause 6: the chart style
A North Indian chart fixes the houses and moves the signs; a South Indian chart fixes the signs and moves the houses. The same positions look different on the page, and a planet can seem to be "somewhere else" when nothing has changed. The full chart in this app offers both, North by default. North vs South Indian charts shows how to read one in the other. This cause changes no number.
Cause 7: the length of a dasha year
BPHS Ch. 46 Sl. 12-14 gives the Vimshottari order, starting from Krittika, and Sl. 15 the periods: 6, 10, 7, 18, 16, 19, 17, 7 and 20 years. Those verses, in this translation, do not say how many days a year has. This app uses 365.2425 days. An app that used a 360-day year would put every boundary 5.2425 days earlier for each year after birth. For the test chart's Jupiter Mahadasha, ending on 5 December 2034, 44.31 years after birth, that is about 232 days.
If two apps agree on the Moon but their dasha dates drift further apart the later they go, a different year length is the first suspect. If the gap is the same size all the way through, look at the birth time or the ayanamsa instead. The Vimshottari Dasha calculator shows this app's dates.
What this app does, and why
- Time: the time zone of the resolved birth place, with that date's summer-time rule; India Standard Time only when no zone is found; 12:00 when no time is given.
- Ayanamsa: Lahiri, one straight-line formula, the same in every calculator.
- Houses: whole-sign, from the rising sign, the system the code uses throughout.
- Node: the mean node everywhere, with Ketu 180 degrees from Rahu.
- Dasha year: 365.2425 days.
Each is one fixed choice, applied the same way in every calculator, so that the birth chart, the dashas, the transits and the matching all read one chart. The methodology page describes the astronomy, and the sources page lists the texts the readings come from.
Limits: what no tool can settle
Comparing two apps can tell you which cause is at work. It cannot tell you which app is right, because most of these are conventions, not measurements. No text in this project's library says which node its rules were written for. BPHS speaks of both a rising sign and house cusps. The dasha verses give years, not days. And the ayanamsa is a chosen zero point, not something a telescope reads off the sky.
What can be settled is the input. A birth time from a hospital record, the correct town and the zone in force that day remove the first two causes. After that, pick one app's conventions and read every part of your chart from it, rather than mixing an ascendant from one tool with dasha dates from another.
- Which app is right when my ascendant differs?
- Neither can prove it from the chart alone. First check that both used the same birth time, place and time zone. If they did and the ascendant still differs, the birth sits close to a sign line, and the birth time's accuracy decides it.
- Why are all my planets in different houses in another app?
- Most often the ascendant changed sign, which moves every planet by one house under whole-sign houses. In the test chart, one hour did exactly that. A cusp-based house system can also move single planets near a sign's edge.
- Why are my dasha dates a few months off?
- A different birth time moves the Moon and every boundary with it: one hour moved the test chart's dates by about 163 days. A gap that grows with each later Mahadasha points instead to a different length of year.
- Does the North or South Indian style change my chart?
- No. It changes only how the same positions are drawn. Every degree, sign and house stays the same.
- Can I make this app use another ayanamsa or the true node?
- No. It computes Lahiri and the mean node only, in every calculator, so that all of its readings come from one chart.
Birth Chart (Kundli)
All nine grahas by sign, degree and nakshatra, with houses when the birth time is known and the place resolves to coordinates.
This one has its own page
This one runs on its own page, built for it, where the full result is laid out properly. No account is needed there either.