The Complete Guide to World Time Zones

Quick answer: The world is divided into 24 primary time zones, each roughly 15° of longitude apart and one hour offset from the next, anchored to Coordinated Universal Time (UTC). But the real map is messier than 24 neat slices: there are around 38 distinct offsets in use once you count half-hour and 45-minute zones, offsets range from UTC−12 to UTC+14 (a 26-hour spread), and about 70 countries shift their clocks twice a year for Daylight Saving Time while roughly 180 do not. This guide explains how the system actually works, why the exceptions exist, and how to stop getting caught out by them.

Convert any two cities instantly: Skip the mental math - open the BestSyncTime converter and drag the Overlap Dial to see your shared working hours in real time.

Why time zones exist at all

Before the 1800s, every town kept its own "local mean time," set by the sun: noon was whenever the sun sat highest overhead. That worked fine when the fastest thing on Earth was a horse. It broke the moment railways arrived.

A train leaving one city and arriving in another a few hundred miles east or west would find the local clock several minutes different - and every station along the line kept its own time. Timetables became impossible, and near-misses on shared tracks became dangerous. The railways needed a shared clock.

In 1884, the International Meridian Conference in Washington, D.C. established the Greenwich Meridian (0° longitude, running through Greenwich, London) as the world's reference line, and divided the globe into standardized zones stepping outward from it. That's why the system is still anchored to Greenwich today, and why the modern global reference - UTC - sits at that same meridian.

The core rule: 15 degrees per hour

The Earth rotates 360° in 24 hours, which works out to 15° of longitude per hour. That's the backbone of the whole system:

• - Every 15° you travel east, local time moves forward one hour.
• - Every 15° you travel west, local time moves back one hour.
• - The reference point is UTC±0 at the Greenwich Meridian.

So a city at 75° east of Greenwich is, in principle, UTC+5. A city at 120° west is UTC−8. Simple - in theory.

UTC, GMT, and why they're not quite the same

People use "GMT" and "UTC" interchangeably, and for everyday purposes they're the same clock. But they come from different places:

For scheduling, treat them as identical. The distinction only matters to astronomers, navigators, and the people who decide when to insert a leap second. When in doubt, use UTC - it's the standard every operating system, airline, and server actually runs on.

The offsets that break the "one hour per zone" rule

Here's where the tidy 24-zone model falls apart. Not every zone is a whole hour off UTC.

These exist because a country's ideal solar time didn't line up neatly with a whole-hour boundary, and its government chose precision over convention. Nepal's UTC+5:45, for instance, is set so that noon roughly matches the sun over its central meridian near Kathmandu - and it deliberately sits 15 minutes off India's UTC+5:30 as a marker of independence from Indian Standard Time.

The extremes: from UTC−12 to UTC+14

The inhabited world stretches across a 26-hour span, not 24. The extra two hours come from the edges:

• - UTC−12 - Baker Island and Howland Island (uninhabited US territories): the last place on Earth to see any given calendar date.
• - UTC+14 - the Line Islands (part of Kiribati): the first place to enter each new day.

That means at certain moments, three different calendar dates exist on Earth simultaneously. When it's Monday afternoon in the Line Islands, it can still be Sunday evening in Baker Island.

The International Date Line

Running roughly down the 180° meridian in the Pacific is the International Date Line - the boundary where the calendar date changes. Cross it going west and you jump forward a day; cross it going east and you repeat a day.

It isn't a straight line. It zig-zags to keep individual countries on a single date. The most famous kink: Kiribati moved the line in 1995 so its entire territory would share one calendar day, pushing its easternmost islands all the way to UTC+14. That's how the Line Islands became the first place on Earth to ring in each New Year.

Why some giant countries use one time zone (and some don't)

Geography says a country should have as many zones as it has 15° bands of longitude. Politics often says otherwise:

• - China spans five geographic zones but runs entirely on a single clock (UTC+8, "Beijing Time"). In its far-western Xinjiang region, this means the sun doesn't rise until around 10 AM by the official clock - so many locals quietly keep an unofficial "Xinjiang time" two hours behind.
• - India uses one zone (UTC+5:30) across a span that geographically covers two, a deliberate choice for national unity - at the cost of very early sunrises in the northeast.
• - Russia, by contrast, embraces its width with eleven time zones, from UTC+2 in Kaliningrad to UTC+12 in Kamchatka.
• - The United States spans six zones (from UTC−5 Eastern to UTC−10 Hawaii), plus territories.

The lesson: a time zone is a political decision as much as a geographic one. You can't reliably guess a country's offset from a map - you have to look it up.

Daylight Saving Time: the moving target

About 70 countries advance their clocks by an hour in the warmer months to shift daylight into the evening, then move them back in autumn. The rest - including most of Asia, Africa, and the equatorial world - never change.

This is the single biggest source of scheduling errors, for one reason: countries that observe DST don't all switch on the same day. In 2026, for example:

Because the US springs forward three weeks before Europe and falls back one week after it, there are two "danger windows" each year when the New York-London gap is off by an hour from its usual five. A meeting that's normally 2 PM New York / 7 PM London silently becomes 2 PM New York / 6 PM London - and someone shows up an hour wrong.

Note also that the Southern Hemisphere runs the opposite schedule: when the north springs forward, Australia and New Zealand are falling back.

This is exactly what a good converter is for. Instead of tracking who's on DST this week, drop your two cities into BestSyncTime - it applies every region's current DST rules automatically, so the overlap you see is always the real one.

How to read a UTC offset like "UTC+5:30"

An offset tells you how far a place's clock is from UTC, not which country it is:

• - UTC+5:30 means "5 hours and 30 minutes ahead of UTC." If it's 12:00 noon UTC, it's 5:30 PM there.
• - UTC−8 means "8 hours behind UTC." 12:00 noon UTC is 4:00 AM there.

To find the difference between two places, compare their offsets. India (UTC+5:30) and New York on standard time (UTC−5) differ by 10 hours 30 minutes. Do that subtraction in your head under deadline pressure and you'll eventually get it wrong - which is the whole reason conversion tools exist.

Time zone abbreviations: a warning

EST, PST, CET, IST - these are convenient but genuinely ambiguous:

• - IST means Indian Standard Time (UTC+5:30) *and* Irish Standard Time (UTC+1) *and* Israel Standard Time (UTC+2).
• - CST means US Central (UTC−6) *and* China Standard Time (UTC+8) *and* Cuba Standard Time (UTC−5).
• - EST flips to EDT for half the year when daylight saving is active - same region, different offset.

For anything that matters, use the UTC offset or the full IANA zone name (like `America/New_York` or `Asia/Kolkata`), never the three-letter abbreviation alone.

Putting it to use

The system comes down to a few durable facts:

• - Everything is measured from UTC at the Greenwich Meridian.
• - The base rule is 15° = 1 hour, but half-hour and 45-minute exceptions exist.
• - Offsets run from UTC−12 to UTC+14, so up to three dates coexist at once.
• - Country borders and DST override the tidy geographic map, so always verify rather than guess.
• - Abbreviations are ambiguous; offsets and IANA names are not.

Once you internalize those, the only remaining hard part is the arithmetic - and that's the part worth handing to a tool. Open BestSyncTime, add every city on your team, and drag the Overlap Dial to see the exact window when everyone's awake. It handles DST, half-hour offsets, and the date line automatically - no mental math required.