A weekly call set for 9:00 in New York and 14:00 in London works all winter. Then, one Monday in March, the London side joins an hour early and waits alone. Nobody typed anything wrong. The two cities changed their clocks on different Sundays, and for a few weeks the gap between them was four hours instead of five. Most time zone mistakes are like this one: the arithmetic is easy, and the rules underneath it are not where people expect them to be.
Clocks Change on Different Sundays
The United States starts daylight saving time on the second Sunday in March and ends it on the first Sunday in November, with each zone switching at 2:00 local time. The UK and the European Union start on the last Sunday in March and end on the last Sunday in October, and they switch all at once, at 01:00 UTC. That is 01:00 in London, 02:00 in Paris and 03:00 in Bucharest, the same instant everywhere.
The second Sunday in March falls between the 8th and the 14th, and the last Sunday between the 25th and the 31st, so in spring America is ahead by two or three weeks depending on the year. In autumn the gap is always exactly one week, since the first Sunday in November is always seven days after the last Sunday in October.
During those weeks every transatlantic meeting moves by an hour for one side. If the invitation was set in New York time, Europe sees it an hour earlier than usual. If it was set in London time, New York sees it an hour later.
New York and London in 2026
Dates from the tz database. The difference is London time minus New York time.
| Period | New York | London | Difference |
|---|---|---|---|
| 1 Jan to 7 Mar | UTC−5 | UTC+0 | 5 hours |
| 8 Mar to 28 Mar | UTC−4 | UTC+0 | 4 hours |
| 29 Mar to 24 Oct | UTC−4 | UTC+1 | 5 hours |
| 25 Oct to 31 Oct | UTC−4 | UTC+0 | 4 hours |
| 1 Nov to 31 Dec | UTC−5 | UTC+0 | 5 hours |
South of the Equator, the Seasons Run the Other Way
Where daylight saving exists in the southern hemisphere, it runs over the southern summer. Sydney moves forward on the first Sunday in October and back on the first Sunday in April. Combine that with New York's rules and the gap between the two cities takes three values over a year: 16 hours in the northern winter, 14 hours in the northern summer, and 15 hours in the weeks of March and October when both cities are on daylight time at once.
A recurring call between the two therefore shifts four times a year, in March, April, October and November. This is the case where converting with today's offset and saving the result goes wrong most often.
A Time That Never Happens, and One That Happens Twice
On the night the clocks go forward, an hour of local time is skipped. In New York on 8 March 2026 the clock went from 1:59:59 straight to 3:00:00, so 2:30 that morning does not exist. A reminder set for it cannot fire at the stated time, and a converter asked for it has to decide what you meant.
On the night they go back, an hour repeats. New York showed 1:30 AM twice on 1 November 2026, first at UTC−4 and then, an hour later, at UTC−5. In Bucharest the repeated hour is 03:00 to 03:59 on 25 October, since that is when 01:00 UTC lands there. A time in that hour names two different instants, and without the offset there is no way to tell which.
Software has to pick a rule. JavaScript's Date, and the newer Temporal API by default, move a skipped time forward by the length of the gap, so 2:30 becomes 3:30, and take the earlier of two repeated times. The converter on this site does the same for skipped times and asks you outright for repeated ones, since only you know which 1:30 you meant.
Scheduled jobs feel this too
A task set to run at 2:30 every night, in a zone that observes daylight saving, may run late, once, or twice on the change nights, depending on the scheduler. Running servers and cron jobs on UTC avoids the question entirely, since UTC never changes its clocks.
Offsets That Are Not Whole Hours
A converter that only adds and subtracts whole hours gets these wrong. All of the offsets below are current in the tz database.
India: UTC+5:30
One zone for the whole country, with no daylight saving. A 9:00 meeting in London in winter is 14:30 in Mumbai.
Nepal: UTC+5:45
Fifteen minutes ahead of India. Among the offsets in use today, it is one of the few that is not a multiple of half an hour.
Newfoundland: UTC−3:30, and −2:30 in summer
The half hour stays with it through daylight saving, so the gap to Toronto stays at 1 h 30 min outside the change nights themselves.
Chatham Islands: UTC+12:45, and +13:45 in summer
A small group of New Zealand islands, always 45 minutes ahead of the mainland.
Lord Howe Island: UTC+10:30, and +11 in summer
This Australian island moves its clocks by only half an hour for daylight saving, so in summer it matches Sydney and in winter it is half an hour ahead.
The Same Three Letters Mean Different Places
Time zone abbreviations are not unique, and the common ones collide. IST stands for India Standard Time (UTC+5:30), Israel Standard Time (UTC+2) and Irish Standard Time (UTC+1, the name Ireland uses for its summer time). CST is Central Standard Time in North America (UTC−6), China Standard Time (UTC+8) and Cuba Standard Time (UTC−5): fourteen hours separate the first two. BST can be British Summer Time or Bangladesh Standard Time.
The other common slip is writing the standard-time name in summer. EST is UTC−5, but New York spends most of the year on EDT, UTC−4. An invitation for "10:00 EST" in July is either an hour off or, more likely, means Eastern Time and is written loosely. Writing ET, or naming the city, avoids both problems. The tz database itself identifies zones by region and city, such as America/New_York, for exactly this reason.
Convert a time between cities
Daylight saving applied for the date you pick, with a planner that finds the hours that work for everyone.
Even the Calendar Can Skip a Day
Offsets are political decisions, and governments change them. Samoa used UTC−11 until the end of 2011, a day behind its main trading partners in Australia and New Zealand. To fix that it moved to the other side of the date line: Thursday 29 December 2011 was followed directly by Saturday 31 December, and Friday the 30th never happened there.
Kiribati had done the same in 1994 for a different reason. Its islands straddled the date line, so the capital and the eastern Line Islands could be on different days. The Line Islands moved from UTC−10 to UTC+14, skipping 31 December 1994, and Kiritimati became one of the first inhabited places to start each new day.
Where the Rules Come From
Nearly every computer and phone gets these rules from the same source, the tz database, also called the IANA time zone database. It records each region's offsets and daylight saving rules, including their history, and is maintained by volunteers who track government announcements, with coordinators designated by the IETF and the data published by IANA. A new release goes out whenever a country changes its rules, sometimes with only weeks of warning.
Browsers carry a copy of it, which is how a page can convert times correctly without asking a server. It also explains the odd failure where two devices disagree about the time in some city: one of them has an older copy of the rules.
Frequently Asked Questions
Related Tools
Keep Reading
Ten Digits or Thirteen: Reading a Unix Timestamp Without Guessing
Milliseconds read as seconds land in the year 55,840. Why the digit count gives the unit away, why JSON rounds off nanoseconds, and where 2038 still bites.
Five Fields, Three Traps: Where Cron Schedules Go Wrong
0 9 1 * 1 runs every Monday, */7 leaves a four-minute gap each hour, and a 02:30 job meets daylight saving. How cron really reads the five fields.
Inclusive or Exclusive: Why Day Counts Come Out One Off
Monday to Friday is four days or five. How court deadlines, Excel's NETWORKDAYS and hotel bills each count, and why a business day depends on where you are.
Date Arithmetic Is Harder Than It Looks: Leap Years and Feb 29
One month after 31 January has no single right answer. How months create ambiguity, and when a leap-day baby legally turns 18.