How Many Time Zones Are There?

The popular “24 time zones” answer comes from a textbook model: divide Earth into 24 wedges, each 15° of longitude wide and one hour offset from the next. The model is mathematically clean and was roughly true in the late 19th century when civil time zones were first standardised. It has not been true for a long time. The /learn/time-zones-explained pillar covers the system that grew out of the idealised model, with all its political and economic compromises. This article focuses specifically on the count itself — why the textbook answer is wrong, and what the real answer is.

The textbook model

When the 1884 International Meridian Conference established the prime meridian at Greenwich, the prevailing proposal was for 24 time zones each 15° of longitude wide. The first zone straddles 0° (UTC), the second covers 7.5°–22.5° E (UTC+1), and so on around the world. At the antimeridian (180°), UTC+12 meets UTC−12, with the date changing as the boundary is crossed.

The model has elegant properties:

• Exactly 24 zones, one per hour.
• Each zone is exactly 15° wide (corresponding to the 360°/24 hours of solar rotation).
• The Sun reaches the meridian at the centre of each zone at local noon (averaged over the year), neatly aligning civil time with apparent solar time.
• UTC offsets run from −12 to +12, covering 24 hours.

Late-19th-century cartography textbooks and atlases adopted the model widely, and it remains the picture most people retain from school. The problem is that countries did not actually adopt the textbook model strictly, and the deviations have multiplied over time.

The first complication: non-hour offsets

A handful of countries adopted non-hour offsets in the late 19th and early 20th centuries, and several more did so later:

| Offset | Region | Population | |---|---|---| | UTC+5:30 | India, Sri Lanka | ~1.4 billion + 22 million | | UTC+5:45 | Nepal | ~30 million | | UTC+6:30 | Myanmar (Burma), Cocos Islands | ~55 million + 600 | | UTC+4:30 | Afghanistan | ~40 million | | UTC+3:30 | Iran | ~90 million | | UTC+8:45 | Eucla (Western Australia) | ~50 | | UTC+9:30 | Australian Central (Northern Territory, South Australia) | ~2 million | | UTC+10:30 | Lord Howe Island (DST: +11:00) | ~400 | | UTC+12:45 | Chatham Islands (NZ); DST +13:45 | ~600 | | UTC−3:30 | Newfoundland and Labrador | ~520,000 | | UTC−9:30 | Marquesas Islands (French Polynesia) | ~9,000 |

That is 11 non-hour offsets already, and the list excludes historically used ones (Venezuela's UTC−4:30 from 2007 to 2016; several pre-1980s Australian and Canadian zones; the various Indian princely-state pre-1955 offsets).

India's UTC+5:30 is by far the most heavily populated non-hour offset, used by about 1.4 billion people. It was adopted at independence in 1947 as a compromise between the Calcutta (then roughly UTC+5:54) and Bombay (then roughly UTC+4:51) meridians; the single zone covers about 28° of longitude, the largest single-zone longitude span of any major country except China.

China's decision in 1949 to use a single UTC+8 zone for the entire country — about 60° of longitude — went the opposite way: unified the country on Beijing time at the cost of solar time deviation in the western provinces (Xinjiang sees solar noon at about 14:00 Beijing time).

The second complication: range past ±12

The textbook model ran UTC−12 to UTC+12, with the date line at ±180°. Kiribati broke that boundary in 1994.

The Republic of Kiribati straddles the antimeridian: the Gilbert Islands sit at around 173°E (UTC+12 in the original scheme), the Phoenix Islands at around 174°W (UTC−11), and the Line Islands at around 157°W (UTC−10). Before 1995 the country was therefore split across two calendar days — the western islands were 24 hours ahead of the eastern islands at any given moment. This was inconvenient for domestic governance.

In December 1994 the Kiribati government shifted the international date line eastward through its territory, bringing all the country onto a single calendar day. The Gilbert Islands stayed at UTC+12; the Phoenix Islands jumped from UTC−11 to UTC+13; the Line Islands jumped from UTC−10 to UTC+14 — the highest positive UTC offset on Earth and the first time the UTC range had extended beyond +12.

Samoa followed a similar logic in December 2011, switching from UTC−11 to UTC+13 to align with its main trading partners in Australia and New Zealand. The day “December 30, 2011” did not exist in Samoa — the country jumped directly from the end of December 29 to the start of December 31. Tokelau, a New Zealand dependency, made the same switch on the same date.

The current UTC offset range therefore runs from UTC−12 (Baker Island and Howland Island, both uninhabited US territories near the antimeridian) to UTC+14 (the Kiribati Line Islands and the Samoa-Tokelau region) — a span of 26 hours rather than 24. There are 26 single-hour positions in the range, plus the various half-hour and quarter-hour offsets, giving roughly 38–40 distinct standard offsets in current use.

DST overlays

Daylight saving time (covered in the /learn/daylight-saving-time-explained support) further complicates the count. A zone that observes DST effectively has two offsets per year: a standard offset (used in winter in the Northern Hemisphere) and a summer-time offset one hour larger. About 70 countries observe DST in 2026.

Counting both standard and DST offsets, the total number of UTC offsets used at some point during the year is closer to 50. The exact figure depends on the year because DST rules change frequently: countries adopt, modify, or abandon DST regularly (Mexico abandoned nationwide DST in 2022; Russia abandoned DST in 2011 then re-allowed some regional opt-outs in 2014; Turkey abandoned DST in 2016).

The IANA database — ~600 named zones

The IANA tz database (also called the Olson database, after its founder Arthur David Olson) lists about 600 named zones in Region/City format: Europe/Berlin, America/New_York, Asia/Tokyo, Pacific/Honolulu, and so on. The database is the authoritative reference for time-zone handling in every Unix-like operating system, the Java JVM, Python, Node.js, .NET, Go, Ruby, and most major databases.

Why 600 named zones for ~40 offsets? Because the database tracks history, not just current offsets:

• A current UTC+1 zone covers many EU countries. Each has its own IANA entry (Europe/Berlin, Europe/Paris, Europe/Madrid, etc.) to record its specific historical path: when it adopted UTC+1, what earlier offsets it used, what DST rules applied at various dates.
• A single country can have multiple zones if it has had different regional offsets historically. The US has Eastern, Central, Mountain, Pacific, Alaska, and Hawaii — six current zones — plus several historical zones (Indiana counties on Eastern vs Central before 2006; Pacific war-time DST).
• Some zones exist only as historical: America/Caracas spans both the pre-2007 UTC−4 era and the 2007–2016 UTC−4:30 experiment.

The IANA design philosophy is to keep one entry per administrative region whose UTC offset has ever differed from any other's. This proliferation produces ~600 zones but ensures that any past timestamp can be correctly converted between UTC and local civil time, no matter when or where.

China and the single-zone outlier

China's decision in 1949 to use a single UTC+8 time zone for the entire country is the most dramatic exception to the “15° = one hour” convention. The country spans about 60° of longitude (from ~73°E in westernmost Xinjiang to ~135°E in easternmost Heilongjiang), which under the textbook model would correspond to four time zones (UTC+5 through UTC+8). The 1949 decision unified the country on Beijing time (UTC+8) as a matter of political and administrative convenience.

The consequence is that solar noon in western Xinjiang occurs at about 14:00 Beijing time. The Uyghur population in Xinjiang has historically maintained an unofficial UTC+6 “local time” for daily life, even though all official institutions (schools, government offices, train schedules) use Beijing time. The split is a source of ongoing political tension in the region.

Russia at the other extreme uses 11 time zones — the most of any country — spanning UTC+2 (Kaliningrad) to UTC+12 (Chukotka). The choice reflects Russia's extreme east-west extent and the practical impossibility of running Vladivostok and Moscow on the same civil clock.

Historical adoption of standard time

The transition from local solar time to standardised UTC offsets was a slow process across the 19th and early 20th centuries:

• 1840s–1850s: British railway companies adopted “railway time” (Greenwich Mean Time) for scheduling, replacing the local mean time that had varied from town to town by a few minutes.
• 1858: Most of mainland Britain officially adopted GMT.
• 1879: Sandford Fleming, a Canadian engineer, proposed the global system of 24 standardised zones at the Royal Canadian Institute.
• 18 November 1883: The US and Canadian railway companies adopted five time zones (later four, after Atlantic was reduced). “The Day of Two Noons” — many places experienced two noon events as clocks were re-set.
• 1884: The International Meridian Conference in Washington formalised the prime meridian and recommended (but did not require) the 24-zone system.
• 1893: Germany unified on Mitteleuropäische Zeit (Central European Time, UTC+1).
• 1916: World War I drove most European countries to adopt fixed national time zones and DST.
• 1972: UTC formally replaced GMT as the international reference for civil time.

Each country's adoption involved trade-offs between solar accuracy and operational simplicity. By the late 20th century the “~40 distinct offsets” landscape of today had largely crystallised.

Operational summary

So the answer to “how many time zones?”:

• Textbook (idealised): 24
• Standard UTC offsets currently in use: about 38–40
• Including DST offsets observed during the year: about 50
• IANA tz database entries: about 600

Each number is correct for a different question. The textbook 24 is the right answer for explaining the rotational origin of time zones. The 38–40 is the right answer for “how many offsets do I need to handle?”. The 50 captures DST. The 600 is what you actually implement against if you are writing time-zone code.

Sources

• IANA time-zone database — the authoritative reference.
• BIPM, Coordinated Universal Time — UTC definition.
• NIST glossary — civil-time references.
• ITU-R Recommendation TF.460-6 — international time-signal standards.
• US Naval Observatory time — astronomical-time references.

For closely related topics, see /learn/time-zones-explained for the pillar covering how civil time zones work, the /learn/iana-time-zone-database support for the database itself, and the /learn/the-international-date-line support for the Kiribati and Samoa shifts that created the UTC+14 and UTC+13 zones.