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.
Want the answer for your own birth? The free summer-time check charts it twice, with and without the extra hour, and shows both lagnas when they differ.
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.
Summer time dates by year, with sources
Marriage-age charts are mostly for people born from about 1987 to 2006, so the US rule for those years matters more than today’s. The dates below are the statutory ones; a tool should read the time-zone history for your exact birth date rather than any table.
| Place | Years | Summer time in force | Source |
|---|---|---|---|
| United States | 1967 to 1973 | Last Sunday in April to last Sunday in October | USNO |
| United States | 1974 | Started 6 January (energy-crisis year-round summer time) | USNO, Smithsonian |
| United States | 1975 | Started 23 February | USNO |
| United States | 1976 to 1986 | Last Sunday in April to last Sunday in October | USNO |
| United States | 1987 to 2006 | First Sunday in April to last Sunday in October | USNO |
| United States | 2007 onward | Second Sunday in March to first Sunday in November | USNO, timeanddate |
| United Kingdom | 1968 to 1971 | Clocks stayed an hour ahead of GMT all year | Wikipedia, History of BST |
| United Kingdom | 1972 to 1980 | Day after the third Saturday in March to the day after the fourth Saturday in October | Wikipedia |
| United Kingdom | 1981 to 2001 | Set by European directives, dates varied | Wikipedia |
| United Kingdom | 2002 onward | Last Sunday in March to last Sunday in October | Wikipedia |
The UK row for 1968 to 1971 is the one calculators most often miss. The time-zone database files it as standard time, so a simple “is daylight saving on?” test says no for a January 1970 London birth, even though clocks were an hour ahead of GMT.
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 New Jersey on 15 March 1995 was on standard time, while a birth there on 15 March 2010 was on summer time. 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.
To see it for your own birth, run the free summer-time check. It shows whether summer time was in effect and, if it was, your lagna both ways. To ask whoever made your existing chart, request the UTC offset they used: for a July birth in London, +0:00 means the summer-time hour was missed and +1:00 means it was used.