How to Calculate Time Differences Across Time Zones
Quick answer: To find the time difference between two locations, convert both times to UTC using their respective offsets, then subtract. A city at UTC+5:30 and a city at UTC−5 have a raw difference of 10 hours and 30 minutes. During daylight saving time, that gap shifts by one hour — but only for the zones that observe DST. The sections below walk through each part of that calculation, including the edge cases that cause real mistakes.
Most conversion errors trace back to one of three things: ignoring DST, not knowing a zone uses a non-whole-hour offset, or forgetting that crossing the International Date Line changes the calendar date. Knowing the formula and its exceptions makes every future calculation faster.
The Basic Formula: UTC Offsets
The universal method is to express both times as UTC offsets and compute the arithmetic difference.
Every time zone is defined as a positive or negative offset from Coordinated Universal Time (UTC). UTC itself carries no offset — it is the reference point. Every other zone adds or subtracts hours (and sometimes minutes) from it.
Step-by-step
- Find the UTC offset for Location A. Example: New York during standard time is UTC−5.
- Find the UTC offset for Location B. Example: Berlin during standard time is UTC+1.
- Subtract one offset from the other: +1 − (−5) = +6. Berlin is 6 hours ahead of New York.
- To convert a specific time, add the difference to the source time or subtract it. If it is 9:00 AM in New York, it is 3:00 PM in Berlin.
Converting via UTC
An alternative approach that removes sign confusion: convert the local time in Location A to UTC first, then convert UTC to local time in Location B.
- New York, 9:00 AM EST → add 5 hours → 14:00 UTC
- 14:00 UTC → subtract 1 hour for Berlin → 15:00 (3:00 PM CET)
This two-step method is especially useful when comparing three or more locations, because everything anchors to the same reference. A reference for all current UTC offsets is maintained by the IANA Time Zone Database, the authoritative source used by operating systems and programming languages worldwide.
For a ready-to-use reference covering UTC, Eastern, and Pacific conversions, see the UTC to Eastern and Pacific cheat sheet.
How DST Complicates the Calculation
Daylight saving time changes a zone’s UTC offset by one hour — but the change happens on different dates in different countries, and not all countries observe DST at all.
This is the single biggest source of conversion errors. When DST transitions are out of sync between two locations, the time difference between them changes temporarily.
The US DST window in 2026
- Clocks spring forward: Sunday, March 8, 2026 at 2:00 AM
- Clocks fall back: Sunday, November 1, 2026 at 2:00 AM
The EU DST window in 2026
- Clocks spring forward: Sunday, March 29, 2026 at 1:00 AM UTC
- Clocks fall back: Sunday, October 25, 2026 at 1:00 AM UTC
Between March 8 and March 29, the US has already moved to summer time but Europe has not. During those three weeks, the US–Europe time difference is one hour narrower than usual. The same compression happens in autumn when the US falls back before Europe does.
Countries that do not observe DST
Large portions of the world keep a fixed UTC offset year-round. These include China (UTC+8 always), Japan (UTC+9 always), India (UTC+5:30 always), most of Southeast Asia, and much of Africa. When you are calculating a time difference between a DST-observing city and a non-DST city, remember that the gap between them changes twice a year even though the non-DST city never moves.
Google provides an overview of how DST affects its calendar product in the Google Calendar Help Center, which also explains how the system handles event times when a user’s local clock changes.
Half-Hour and 45-Minute Offset Zones
Not every time zone is on a whole-hour boundary. Several major locations use offsets of :30 or :45 minutes, which means your arithmetic must account for minutes, not just hours.
This surprises many people. The most common non-whole-hour offsets are:
| Location | UTC Offset |
|---|---|
| India (IST) | UTC+5:30 |
| Sri Lanka | UTC+5:30 |
| Afghanistan | UTC+4:30 |
| Iran | UTC+3:30 (UTC+4:30 during DST) |
| Nepal | UTC+5:45 |
| Chatham Islands (NZ) | UTC+12:45 (UTC+13:45 during DST) |
| Myanmar | UTC+6:30 |
| Marquesas Islands | UTC−9:30 |
Calculation example with minutes
New York (EST, UTC−5) to Mumbai (IST, UTC+5:30):
Difference: +5:30 − (−5:00) = 10 hours 30 minutes.
At 10:00 AM in New York, it is 8:30 PM in Mumbai.
When calculating with these zones, convert the offsets to total minutes to avoid arithmetic errors. UTC−5 is −300 minutes. UTC+5:30 is +330 minutes. Difference: 330 − (−300) = 630 minutes = 10 hours 30 minutes.
Crossing the International Date Line
When a time difference carries you past UTC+12 or past UTC−12, you have crossed the International Date Line, which means the calendar date changes by one day.
The International Date Line runs roughly along the 180th meridian in the Pacific Ocean. Time zones to the east of it are behind UTC; zones to the west of it are ahead of UTC. Crossing it in either direction changes the date.
Practical decision rule
If the sum of two UTC offsets, moving east from one city to the other, exceeds 24 hours, the arrival date is the next calendar day. If the eastward travel would be shorter going the other direction (west), the date difference reverses.
A simpler check: if one location is UTC+12 or higher and the other is UTC−10 or lower, there is likely a date change involved in the calculation.
Example: Los Angeles to Auckland
Los Angeles in summer (PDT) is UTC−7. Auckland in summer (NZDT) is UTC+13. The raw offset difference is 20 hours. At 5:00 PM Monday in Los Angeles, it is 1:00 PM Tuesday in Auckland. The time of day is 8 hours earlier in Auckland, but the date is one day ahead.
The IANA Time Zone Database catalogues both sides of the Date Line accurately, including the politically-motivated zone shifts (such as Samoa’s 2011 shift from UTC−11 to UTC+13) that can otherwise mislead automated calculators working from outdated data.
Common Mistakes
Mistake 1: Applying the same offset year-round
Using EST (UTC−5) for New York in July is wrong. New York switches to EDT (UTC−4) from mid-March through early November. Errors from this mistake are off by exactly one hour and are easy to miss.
Fix: Always check whether the current date falls within a DST window before using a zone’s standard offset.
Mistake 2: Assuming both cities change DST on the same date
Two cities can both observe DST but transition on different days. The US transitions on the second Sunday in March; most of Europe transitions on the last Sunday in March. During the gap between those two Sundays, the US–Europe difference is one hour narrower than it is the rest of the year.
Fix: Look up each city’s DST dates independently rather than assuming they are synchronized.
Mistake 3: Forgetting that Date Line crossings change the day
Scheduling a call between San Francisco and Sydney often produces a meeting that appears to be the same day on one calendar and the following day on the other. Sending an event invite without confirming the date in both locations causes missed calls.
Fix: When any pair of cities spans more than 12 hours of difference, verify the calendar date explicitly in both locations.
Mistake 4: Treating time zone abbreviations as globally unique
EST is Eastern Standard Time in the US but also stands for Australian Eastern Standard Time (UTC+10). CST is Central Standard Time (UTC−6) in the US and China Standard Time (UTC+8). Abbreviations are ambiguous.
Fix: Use UTC offsets or full IANA zone names (such as America/New_York or Australia/Sydney) whenever precision matters.
Mistake 5: Ignoring historical offset changes
Governments occasionally change time zone rules. In 2023, for example, several US state-level proposals to eliminate DST were under active consideration. Any calculation that reaches far into the future or far into the past should account for the possibility that the rules in effect today may not apply.
Tools That Help
No mental arithmetic is reliable when time zones, DST, and date crossings all interact. Tools that hold the IANA database eliminate the margin for error.
The right tool depends on the situation:
- Scheduling a one-off meeting: Google Calendar’s built-in time zone fields show the event time in each attendee’s local time zone automatically. For setup, see how to add a secondary time zone in Google Calendar.
- Comparing multiple zones for a team: A dedicated converter that displays several zones in a column view removes the guesswork. The time zone converter for meetings guide covers the most reliable options and when to use each.
- Quick one-off conversions: The TimeHopper converter handles direct pairs — for example, PST to EST or UTC to EST — and updates automatically for DST. The main converter index covers all supported pairs.
TimeHopper is built as a temporal workflow layer: it sits alongside Google Calendar and provides the offset arithmetic, DST awareness, and zone comparison that Calendar does not expose directly. It is useful when you need to verify a time across several zones at once or when you want to catch DST edge cases before they cause a missed meeting.
For teams managing recurring meetings across multiple continents, the playbook in mastering remote time zones covers overlap-hour strategies and async-first rules that reduce how often the calculation even needs to happen.
Quick Reference: Major Time Zones and UTC Offsets
This table shows standard and daylight time offsets for frequently used zones. The DST column reflects Northern Hemisphere summer (approximately late March through late October for European zones, mid-March through early November for US zones).
| Zone | City / Region | Standard Offset | Daylight Offset | Observes DST |
|---|---|---|---|---|
| UTC | Universal reference | UTC+0 | — | No |
| GMT | London (winter) | UTC+0 | UTC+1 (BST) | Yes |
| ET | New York, Miami | UTC−5 | UTC−4 | Yes |
| CT | Chicago, Dallas | UTC−6 | UTC−5 | Yes |
| MT | Denver, Phoenix* | UTC−7 | UTC−6 | Yes* |
| PT | Los Angeles, Seattle | UTC−8 | UTC−7 | Yes |
| AKT | Anchorage | UTC−9 | UTC−8 | Yes |
| HT | Honolulu | UTC−10 | — | No |
| BRT | São Paulo, Rio | UTC−3 | — | No (since 2019) |
| WET/CET | Lisbon / Paris | UTC+0 / UTC+1 | UTC+1 / UTC+2 | Yes |
| EET | Athens, Helsinki | UTC+2 | UTC+3 | Yes |
| MSK | Moscow | UTC+3 | — | No |
| GST | Dubai, Abu Dhabi | UTC+4 | — | No |
| IST | India | UTC+5:30 | — | No |
| ICT | Bangkok, Ho Chi Minh | UTC+7 | — | No |
| CST | Beijing, Shanghai | UTC+8 | — | No |
| JST | Tokyo | UTC+9 | — | No |
| AEST | Sydney, Melbourne | UTC+10 | UTC+11 (AEDT) | Yes (southern autumn/winter) |
| NZST | Auckland | UTC+12 | UTC+13 (NZDT) | Yes (southern autumn/winter) |
*Phoenix, Arizona does not observe daylight saving time. Most of the Navajo Nation within Arizona does observe it.
Checklist: Before You Schedule a Cross-Zone Meeting
- Identify the UTC offset for every city involved.
- Confirm whether each city is currently in standard or daylight time.
- Check that the US and EU DST transitions are not creating a temporary gap if both regions are involved.
- Verify the calendar date in every location, especially if any pair spans more than 12 hours.
- Use an IANA-compliant tool to confirm the final times rather than relying on memory or manual arithmetic.
- Send the calendar invite with the event time zone set explicitly, so each attendee sees their local time.
FAQ
What is the fastest way to calculate the time difference between two cities?
Find the UTC offset for each city, then subtract one from the other. The result is the hour (and sometimes minute) difference. For example, UTC+9 (Tokyo) minus UTC−5 (New York EST) equals 14 hours. Tokyo is 14 hours ahead. For instant results without arithmetic, a dedicated converter like the ones at TimeHopper handles DST automatically.
Why does the time difference between New York and London change twice a year?
The US and the UK both observe daylight saving time, but they switch on different dates. The US changes clocks in mid-March; the UK changes in late March. During those two weeks, and again in autumn when the dates diverge, the difference between the two cities is temporarily 4 hours instead of the usual 5.
How do I calculate a time difference when one city uses a half-hour offset?
Convert both offsets to total minutes, then subtract. India is UTC+5:30, which is +330 minutes. New York (EST) is UTC−5, which is −300 minutes. The difference is 330 − (−300) = 630 minutes = 10 hours 30 minutes. India is 10.5 hours ahead of Eastern Standard Time.
What happens to the calculation when I cross the International Date Line?
The calendar date changes by one day. If you are calculating the time in a city east of the Date Line (like Honolulu, UTC−10) from a city west of it (like Auckland, UTC+12 or +13), the eastern city will show a date that is one day earlier than the western city, even if the clock times are close together. Always verify both the time and the date when the gap between two zones exceeds 12 hours.
Sources
- IANA Time Zone Database: https://www.iana.org/time-zones — the canonical source for UTC offsets and DST rules used by most operating systems and programming languages.
- Google Calendar Help Center — Daylight Saving Time: https://support.google.com/calendar/answer/37064 — official documentation on how Google Calendar handles DST transitions.
- US Department of Transportation — Daylight Saving Time: https://www.transportation.gov/regulations/daylight-saving-time — federal reference for US DST policy and exemptions.
Add to Chrome - Free