If you were born during daylight saving time, one specific data-entry mistake can quietly shift your entire chart, and it is common enough to be worth calling out directly.
The mistake: using standard time zone instead of the DST offset
Most people know their birth city’s standard time zone (like Eastern Time, UTC-5), but during daylight saving periods, clocks are set an hour ahead. A birth certificate or hospital record showing “2:15 PM” during DST means the actual standard-time equivalent is 1:15 PM, a full hour earlier. A calculator that applies the standard offset to a DST-recorded time will compute the wrong sidereal time, and every downstream calculation shifts with it.
Why this matters more than it sounds
An hour of error moves the lagna (which changes roughly every two hours) meaningfully, and can shift finer details in nakshatra pada and dasha timing too. For a birth close to a DST transition (the specific hour when clocks change), this becomes even trickier, since that hour may occur twice or not at all on the transition date.
Historical DST rules also matter
Some countries have added, removed, or changed their DST rules entirely over the decades. A tool needs to apply the DST rule that was actually in effect on the specific birth date, not today’s rule for that location.
The countries where this bites the hardest
India does not observe daylight saving time, so births in India aren’t affected at all. But births in the US, Canada, most of Europe, Australia, and New Zealand all have DST complications, and each country has changed its rules at least once over the past few decades. The US, for example, extended DST by several weeks in 2007 (starting three weeks earlier in March and ending one week later in November), so a birth in April 1995 and a birth in April 2010 fall under different DST rules for the same city. Germany and most EU countries have followed a consistent DST schedule since 1996, but individual countries before that were inconsistent. Australia is particularly tricky because each state sets its own DST rules, and some states (Queensland, Western Australia, Northern Territory) do not observe DST at all. If your birth was in Brisbane in January 1990, there is no DST to worry about. If it was in Sydney on the same date, DST was in effect. A one-hour error from DST mishandling will shift your lagna by roughly half a sign and can move nakshatra pada boundaries enough to change your dasha timeline by months.
The repeated hour on fall-back night
There’s a trickier edge case than the standard offset error: births during the “fall back” transition, when one specific hour occurs twice. In the US this happens in early November at 2:00 AM, which becomes 1:00 AM again. A baby born at “1:30 AM” that night could mean two different moments an hour apart, and a hospital record doesn’t always specify which. Some hospitals note “CDT” versus “CST” explicitly; older records sometimes just say “1:30 AM.” If your birth falls in this window, ask family what else was happening then, since context can help settle which side of the transition it landed on.
Southern Hemisphere DST runs backward
Countries south of the equator that observe DST, Australia, New Zealand, parts of South America, flip the calendar relative to the Northern Hemisphere. Sydney observes DST October through April, covering the southern summer, while London observes it March through October. A birth in Sydney in December is during DST; one in June is not. If you’re used to thinking of DST as a spring-and-fall Northern Hemisphere thing, this reversal is easy to miss when working out a Southern Hemisphere birth by hand.
Make sure your tool handles this correctly
A reliable kundli tool should account for DST automatically based on the birth date and location, rather than asking you to do the conversion yourself.