How time zones actually work — the complete beginner's guide
If you've ever stared at a flight ticket showing a departure of 10:30 PM and an arrival of 6:00 PM the same day (a flight that takes 13 hours and went west across the Pacific), you've encountered the strangeness of time zones. The math seems wrong but it isn't — you're crossing zones faster than time is "passing."
For the practical answer to "what time is it in [city]," the world clock is the fastest tool. The rest of this post explains why time zones exist at all.
The basic mechanic — Earth rotates
Earth turns once every 24 hours. The sun is overhead at any given longitude exactly once per rotation. Local solar noon — the moment the sun is at its highest point — happens at different absolute times for every longitude.
Time zones standardize that fact. Instead of every town having its own slightly different "local time" based on the sun, the world is divided into roughly 24 zones, each one hour different from its neighbors. Within a zone, everyone's clock shows the same time even if the sun is technically at a slightly different angle.
Each 15° of longitude corresponds to one hour. Earth's circumference is 360°; 360° ÷ 24 = 15°. So if you know how many degrees east or west of the prime meridian you are, you know roughly how many hours your zone is from UTC.
The prime meridian — UTC zero
The prime meridian runs through Greenwich, London. It was internationally agreed upon in 1884 at a conference of 25 nations. Before then, every country had its own arbitrary "zero point" for longitude. Greenwich won partly because the British Empire had the most ships, partly because British nautical charts were the most widely used, and partly because the meeting was held in Washington and the alternative French candidate (Paris) was politically inconvenient.
UTC is anchored to the prime meridian. Everywhere east of Greenwich is UTC+something; everywhere west is UTC-something.
Why it's not just longitude
If time zones were strictly geographical, the boundaries would be straight north-south lines every 15° of longitude. They aren't. Real time-zone boundaries follow:
- Country borders. France is one zone (UTC+1) even though western France is technically closer to the UK's longitude.
- Political decisions. China is one zone (UTC+8) even though the country spans 5 longitudes that "should" be different zones. Spain is on Central European Time (UTC+1) despite being roughly aligned with the UK.
- Historical accidents. Newfoundland is UTC-3:30. Nepal is UTC+5:45. India is UTC+5:30. None of these are at "natural" 15° boundaries.
Half-hour and 45-minute offsets
A few places use offsets that aren't whole hours:
| Place | Offset |
|-------|--------|
| India | UTC+5:30 |
| Sri Lanka | UTC+5:30 |
| Iran | UTC+3:30 |
| Afghanistan | UTC+4:30 |
| Nepal | UTC+5:45 |
| Myanmar | UTC+6:30 |
| Newfoundland | UTC-3:30 |
| Lord Howe Island (Australia) | UTC+10:30 / +11 |
| Marquesas Islands | UTC-9:30 |
| Chatham Islands (NZ) | UTC+12:45 |
Each one has a story. India unified its multiple British-era zones into a single half-hour-offset zone after independence. Nepal shifted from UTC+5:30 to UTC+5:45 in 1986 to differentiate from India. Iran's UTC+3:30 reflects the country's geographic center.
DST inside zones
Many zones observe daylight saving time, which adds another layer. The US East Coast is UTC-5 in winter (EST) and UTC-4 in summer (EDT). London is UTC+0 in winter (GMT) and UTC+1 in summer (BST). The zone is the same; the offset shifts.
This is why naming a zone with just an offset (like "GMT-5") is ambiguous — it doesn't tell you whether DST is in effect. Better to say `America/New_York`, which encodes both the base offset and the DST rules.
Crossing zones
When you fly across zones, your wall clock changes but your body's time hasn't. That's jet lag.
Going east, you "lose" hours: a flight from London to Tokyo (9 hours flight time, 9 zones east) departing at 10 AM lands at 7 AM the next day local time. From your body's perspective, only 9 hours passed. From your watch, 22 hours did.
Going west, you "gain" hours. The Tokyo-to-London flight returning home arrives at 2 PM the same day local time after departing at noon — you "gained" 9 hours back.
The international date line resolves the apparent contradiction (sailing west around the world, you'd "gain" 24 hours and arrive a day later than expected). The line zigzags through the Pacific to keep certain island groups on the same date as their geographic neighbors.
When time zones change
Countries adjust time zones occasionally. Examples:
- Samoa moved from UTC-11 to UTC+13 in 2011 to align with Australia/NZ for trade.
- North Korea briefly used UTC+8:30 (2015–2018) before re-aligning with South Korea at UTC+9.
- Russia moved from observing DST to permanent winter time in 2011, then to permanent summer time, then back to permanent winter time — multiple shifts in a few years.
- Egypt added and removed DST several times in the 2010s and 2020s.
Each change ripples through the IANA database, OS updates, and software libraries.
FAQ
Why are some time-zone offsets in 30-minute increments?
Mostly historical and political reasons. India, Iran, Afghanistan, Newfoundland — each picked its offset based on local political or geographic decisions, not strict 15°-longitude math. The 30-minute and 45-minute offsets persist because changing them would cause more disruption than benefit.
How does the world agree on time-zone boundaries?
It doesn't, exactly. Each country sets its own rules. The IANA tz database catalogs them all. International coordination happens through ITU and IANA but enforcement is per-country.
Why does China have only one time zone for such a big country?
A 1949 political decision. Mao's government unified China onto Beijing time as a symbol of national integration. The result is that the sun rises at 10 AM in western Xinjiang in winter — a real practical hardship for residents there.
What's the difference between a time zone and a UTC offset?
A UTC offset is just a number ("UTC+5"). A time zone is a named region with a current offset, DST rules, and historical rules ("America/New_York" = UTC-5 winter, UTC-4 summer, with specific transition dates). Time zones contain offsets; they're more informative.
Can I just always use UTC and ignore time zones?
For storage, yes — that's the recommended practice for servers. For display, you almost always need to convert to local time so users see what they expect. The time converter handles the math either way.
Bottom line
Time zones exist because Earth rotates and we want clocks to roughly track the sun. The 15° hour rule is the rough geometry; the actual boundaries follow politics, history, and country borders. Half-hour offsets, fractional zones, and seasonal DST shifts add complications that the IANA tz database manages so you don't have to.
For looking up the current time anywhere in the world, the world clock does the lookup. For converting a specific time between zones, the converter handles the math.