Time Zone Difference Calculator

Time Zone Guide

How Time Zones Work?

The world is divided into 24 standard time zones, each covering 15° of longitude (one hour apart). UTC (Coordinated Universal Time) is the global reference point — previously called GMT (Greenwich Mean Time), which still defines UTC+0. Time zones are expressed as offsets from UTC: New York is UTC-5 (EST) or UTC-4 (EDT during daylight saving), London is UTC+0 or UTC+1 (BST), Tokyo is UTC+9 year-round, Sydney is UTC+10 or UTC+11 (AEDT).

What should I know about Daylight Saving Time?

Around 70 countries observe daylight saving time (DST), shifting clocks forward one hour in spring and back in autumn. This creates a complication: a fixed UTC offset does not tell you the current local time without knowing whether DST is in effect. The EU has voted to abolish DST but implementation has stalled. The US shifts clocks on the second Sunday in March and first Sunday in November. The UK shifts on the last Sunday in March and October. Note that some countries — India, China, and Russia among them — do not observe daylight saving time at all, keeping a single fixed offset year-round.

What should I know about International Date Line?

The International Date Line runs roughly along the 180° meridian (with diversions for island nations). Crossing it westward adds a day; crossing eastward removes a day. This is why a flight from Los Angeles to Sydney crosses tomorrow, and why Samoa changed sides of the date line in 2011 to align itself with its main trading partners in Australia and New Zealand, skipping December 30, 2011 entirely — a date that never existed for that country.

What should I know about Scheduling Across Time Zones?

For international calls and meetings, always specify time zones explicitly (not just the city name, as large countries span multiple zones). Tools like Every Time Zone, World Time Buddy, or Google 'time in [city]' are reliable for current times. For business scheduling, early morning US East Coast overlaps with late afternoon UK — the most common working-hours overlap for transatlantic calls. US West Coast to UK requires someone working outside standard hours.

What should I know about Countries with Unusual UTC Offsets?

Most time zones are offset from UTC by a whole number of hours, but several countries deliberately use half-hour or even 45-minute offsets, which can catch travellers and schedulers off guard if they assume every zone lines up on the hour. India (UTC+5:30), several parts of Australia including South Australia (UTC+9:30), and Newfoundland in Canada (UTC-3:30) use half-hour offsets, while Nepal uses an unusual 45-minute offset (UTC+5:45). These aren't arbitrary — they're typically chosen so the country's clock aligns more closely with true solar noon at its particular longitude, given its position relative to neighbouring zones that use whole-hour offsets. For anyone scheduling a call or flight connection involving one of these regions, it's worth double-checking the exact offset rather than assuming a round number, since a half-hour miscalculation is an easy mistake to make and has caused plenty of missed calls and confused meeting invites when converting between a half-hour-offset zone and a neighbouring whole-hour zone.

What's the key thing to understand about Time Zone Abbreviations Being Ambiguous?

Three-letter time zone abbreviations like CST, EST, or IST are a common source of confusion because several unrelated time zones around the world share the same abbreviation. CST, for example, is used for both US Central Standard Time and China Standard Time, which are many hours apart — relying on the abbreviation alone to interpret a meeting invite or flight itinerary can lead to being hours off if the wrong region is assumed. IST similarly refers to both Indian Standard Time and Irish Standard Time. Because of this ambiguity, modern scheduling tools and calendar systems increasingly use the IANA time zone database format instead (such as 'Europe/London' or 'America/Chicago'), which unambiguously identifies a specific region and automatically handles that region's own daylight saving rules. When converting times across zones, especially for international meetings or flights, it's safer to confirm the full city or region name alongside any abbreviation, rather than assuming a three-letter code refers to the time zone you're most familiar with.

What Are Half-Hour and 45-Minute Time Zone Offsets?

While most of the world's time zones are set at whole-hour offsets from UTC, a number of countries deliberately use half-hour or even 45-minute offsets, which can catch travellers and schedulers off guard when converting times. India (UTC+5:30), parts of Australia including South Australia and the Northern Territory (UTC+9:30), and Iran (UTC+3:30) are among the more commonly encountered half-hour offset zones, generally chosen because the country's geographic position falls roughly midway between two standard whole-hour zones, and a half-hour offset was judged to better align daily life (daylight hours, working patterns) with the sun than rounding to the nearest full hour would. Nepal uses an even less common 45-minute offset (UTC+5:45), one of very few places in the world to do so, reportedly chosen partly to assert a distinct national time identity from neighbouring India's own half-hour offset, though various rationales are commonly cited. These unusual offsets matter practically for scheduling international calls or converting flight arrival times, since a mental shortcut of "add or subtract whole hours" will produce an error of 30 or 45 minutes when one of the zones involved uses a non-standard offset — a mistake that's easy to make and easy to miss until it causes a real scheduling problem. When scheduling anything time-sensitive across time zones, it's worth explicitly checking whether either location uses a half-hour or 45-minute offset rather than assuming all time zones differ by whole hours.

Worked Example: Converting a Flight's Departure and Arrival Times

Suppose a flight departs London (UK, UTC+0 in winter) at 10:30 and takes 8 hours 45 minutes to reach New York (UTC−5 in winter). To find the local arrival time, first add the flight duration to the departure time in the origin's time zone: 10:30 + 8:45 = 19:15 London time on arrival. Then convert that arrival moment into the destination time zone by applying the offset difference between the two zones. London is UTC+0 and New York is UTC−5, a difference of 5 hours, so subtract 5 hours from the London-time arrival: 19:15 − 5:00 = 14:15 New York time. So a passenger leaving London at 10:30 and flying for 8 hours 45 minutes lands locally at 14:15 in New York, even though just over 8 and a half hours have actually passed — the clock seems to move less than the real flight duration because the destination is 'behind'. The same subtraction works in reverse (add hours) when travelling eastward into a zone ahead of the origin.

Reference: Common UTC Offsets Worldwide

These offsets are the standard-time baseline; several of these locations shift by an extra hour for part of the year under daylight saving time, so always check whether DST is in effect on the specific travel dates rather than relying on a fixed offset year-round.

Why Some Countries Don't Observe Daylight Saving Time at All

Countries near the equator see little benefit from daylight saving time, since day length barely changes across the year, which is why most tropical nations never adopt it. Several countries further from the equator have also abandoned DST after deciding the costs (disrupted sleep, scheduling confusion, modest or disputed energy savings) outweighed the benefits, including most of Asia, nearly all of Africa, and Japan, which has not observed DST since shortly after World War II. This patchwork is exactly why a fixed UTC-offset lookup can go stale: a time zone converter needs to know not just the offset but also whether that specific location currently applies a seasonal DST shift at all.

Why Global Teams Often Schedule by UTC

Scheduling a recurring meeting by local time in either party's city seems simpler, but it silently breaks whenever either location changes its clocks for daylight saving — and the two locations often don't change on the same date, or one doesn't observe DST at all. Scheduling instead by a fixed UTC time (for example, '14:00 UTC every Tuesday') never moves, so each participant's calendar app converts it to their own correct local time automatically, including through DST transitions, without anyone needing to manually re-check or re-send the invite twice a year. This is standard practice for distributed software teams and international flight operations for the same reason: UTC has no daylight saving and no regional variation, making it the one timezone-free reference point every local clock can be reliably converted from, in either direction, at any time of year.