Why do two websites show different Kundlis?
Different charts can result from different inputs, calculation settings or display conventions. Compare the exact birth instant and coordinates first, then the zodiac reference, ayanamsa, house method, node option and position type. A different drawing or house label does not automatically mean that a planet was calculated incorrectly.
- Compare the same instant, not only the same typed clock time
- Match settings before comparing interpretation
- Use the numerical planet table alongside the drawing
Two sites can use the same ephemeris and still differ because they use different conventions. They can also contain real input or calculation errors. ‘Both must be right’ and ‘one must be fake’ are equally premature conclusions until the discrepancy is isolated.
This guide gives a reproducible calculation example and a troubleshooting order. It does not assign a ranking to named providers or determine which astrological interpretation will describe a life more accurately. The immediate task is to explain what changed in the calculation.
First match the birth instant and location
Write the date in an unambiguous form, such as 1 January 1990. A numeric date like 01/02 can mean 1 February or 2 January. Confirm AM or PM, the timezone that applied on that date, and whether the tool expects local civil time or UTC. Entering the same digits into fields with different time conventions does not specify the same instant.
For the example used here, 1 January 1990 at 12:00 IST is 06:30 UTC. Entering 12:00 UTC instead shifts the instant by five and a half hours. That is a substantial change to a horizon-based chart, not a small rounding discrepancy.
Match the actual coordinates too. A city centre, a hospital and a similarly named town may have different coordinates. Historical timezone and daylight-saving changes need date-specific handling. Do not apply today’s offset to every birth date without checking the location’s time history.
Tropical and sidereal zodiacs use different reference points
A tropical zodiac is referenced to the equinox; a sidereal zodiac uses an adopted offset called ayanamsa. Jyotisha commonly uses a sidereal reference, while many Western chart tools default to tropical. The same physical planet position can therefore receive a different zodiac longitude and sign label.
Our example is New Delhi, 1 January 1990, 12:00 IST, at 28.6139° N and 77.2090° E. With JPL DE440s, the geocentric Moon longitude is approximately 330.1860° in the tropical frame. Subtracting the example’s Spica-anchored True Chitra ayanamsa of 23.7038° gives approximately 306.4822° in the sidereal frame.
The tropical value is just inside Pisces; the sidereal value is in Aquarius. The Moon has not jumped in space. The reference from which its longitude is measured has changed. For comparison, keep the complete longitude as well as the named sign. Rounding near a boundary can otherwise hide the reason.
Ayanamsa options must also match
Lahiri, Raman, Krishnamurti and True Chitra are names readers may encounter in software. These are not interchangeable settings. A difference in the adopted offset can move a planet across a sign, nakshatra or subdivision boundary when its longitude is close enough to that boundary.
Our worked values use the explicitly named Spica-anchored True Chitra reference. They should not be advertised as a test of every implementation labelled ‘Lahiri.’ Record the actual method and version used by the provider. The reference point and its treatment can matter even when two setting labels look similar.
Ayanamsa selection changes a conventional coordinate reference; it does not establish an independently verified prediction. If an astrologer prefers a particular setting, ask them to state it so another reader can reproduce the chart. Changing settings until a description feels right is a different activity from checking a calculation.
House methods can change house labels without changing signs
A whole-sign Rashi presentation makes the sign containing the ascendant the first house. A Chalit presentation assigns planets according to the boundaries of its chosen bhava method. Different methods can give different house numbers for the same planetary longitude.
If the degree and sign agree but the house number differs, inspect the house settings before investigating the ephemeris. Check whether the ascendant is used as the beginning of a house or as its centre, and whether the method uses equal or unequal houses. ‘Bhava Chalit’ is not a sufficiently precise specification of every calculation.
A planet reassigned from house two to house one does not acquire a new sign. Keep sign-based dignity and house placement distinct. The detailed Rashi-versus-Chalit example shows this using visible boundaries and arithmetic.
Geocentric, topocentric and node options
Geocentric positions use Earth’s centre as the reference; topocentric positions use the observer’s location. The Moon is close enough that this distinction can noticeably alter its apparent longitude. Many natal conventions use geocentric positions, but the selected option needs to be checked rather than assumed.
The lunar nodes also have different calculation options. A mean node uses an averaged model; an instantaneous true node is derived from the orbital geometry at the instant. A programme’s ‘true node’ algorithm can have implementation details of its own. Record the option and compare like with like.
| Setting | Longitude | What changes |
|---|---|---|
| Tropical Moon | 330.1860° | Different zodiac reference |
| Sidereal, geocentric Moon | 306.4822° | Baseline for this comparison |
| Sidereal, topocentric Moon | 306.9578° | Observer-based position |
| Sidereal instantaneous true node | 293.1616° | Instantaneous orbital geometry |
| Sidereal mean node | 294.7400° | Averaged mathematical model |
In this example, the topocentric sidereal Moon differs from the geocentric Moon by about 0.4756°, while the two displayed node values differ by about 1.5784°. Both Moon options still lie in Aquarius here. A changed degree does not always produce a changed sign, and a changed sign is most likely when a boundary lies between the two values.
These are computed examples using our local astronomy engine, not copied screenshots. Its tropical geometry and Sun/Moon values were checked against the existing independent Swiss Ephemeris fixtures to within 0.02°. Node definitions and the chosen sidereal reference are stated separately so the comparison remains reproducible.
When the numbers agree but the chart looks different
North Indian, South Indian and other chart drawings arrange signs and houses differently. Sign numbers can be mistaken for house numbers, particularly when a reader is learning a new layout. Compare the numerical planet table and the marked ascendant before interpreting the drawing.
Also check whether you are viewing the same chart: D1, a divisional chart, a Chalit chart, or a chart counted from the Moon. A site might open a secondary chart by default. Different divisional-chart conventions or different reference frames are not resolved by comparing only the picture.
Display rounding matters at a boundary. A value printed as 30° may be the rounded end of one sign rather than exactly 0° in the next. Ask for unrounded longitude when the difference depends on seconds of arc.
A troubleshooting order that isolates the cause
- Save the complete inputs and settings from both providers, with personal details redacted if sharing publicly.
- Convert both inputs to the same UTC instant and verify the coordinates.
- Match tropical or sidereal reference and the exact ayanamsa method.
- Match geocentric/topocentric and mean/true-node options.
- Compare unrounded planetary longitudes, then the ascendant and house boundaries.
- Confirm the chart type, layout and house convention.
- Only after the inputs agree, investigate an unexplained numerical discrepancy with the provider.
Change one setting at a time and record the result. If you alter timezone, ayanamsa and houses together, you cannot tell which change solved the discrepancy. An ordinary spreadsheet with input, setting, output and difference columns is enough for a useful audit.
What an unresolved disagreement means
If all documented settings agree but a difference remains, ask for the provider’s calculation method, supported date range and precision. An older ephemeris, a hidden default, a timezone bug or an unsupported house calculation can matter. Do not assume that a few arcseconds and several degrees have the same significance.
Distinguish a reproducible numerical difference from two astrologers giving different interpretations of identical numbers. The first is a calculation question; the second involves the chosen interpretive rules. Agreement between software packages demonstrates consistency under matching conditions, not proof of a promised future event.
Continue with the chart guides
Read what changes when birth time is unknown, Rashi and Bhava Chalit, and the twelve houses. The Kundli tool is useful for exploring a known instant; keep its stated input and reference settings with any saved result.
Frequently asked questions
Does a different Kundli prove one site is wrong?
Not by itself. First compare the instant, location, zodiac, ayanamsa, house method and position options. An unexplained difference after matching settings deserves investigation.
Why do the Moon signs differ between two apps?
The zodiac reference, ayanamsa, input instant or position type can put the calculated longitude on different sides of a sign boundary.
Can a planet change house while staying in the same sign?
Yes. House systems can assign the same longitude to different houses without changing the sign.
Are mean and true Rahu identical?
No. They use different node models and can produce different longitudes. Match the option when comparing charts.
Should I compare screenshots or degree tables?
Use both, but start with the degree table and ascendant. Drawings and sign-number conventions can make identical data look different.
What if the birth time is only an estimate?
Record the possible interval and test changing outputs. Matching settings cannot remove uncertainty in the original birth time.