Complete guide to world time zones in 2026

What is a time zone, really?

A time zone is a contract: a region of the Earth has agreed that, at any given moment, the wall clocks inside that region will show the same value. The contract is between the people in that region and a government — usually the national one, sometimes a state or province — and the contract is recorded, in machine-readable form, in the IANA Time Zone Database, the dataset that every operating system, programming language, and timekeeping service in the world ultimately reads from.

The IANA database — also called the Olson database, after its original maintainer Arthur David Olson — does two things. It assigns each civil time zone a stable identifier of the form `Region/City`: `America/New_York`, `Europe/Paris`, `Asia/Kolkata`, `Pacific/Auckland`. And it records, for each identifier, the entire historical and projected sequence of offset rules: when standard time changes, when daylight saving time starts and ends, what abbreviation is in use during each part of the year, and when, historically, the offset itself was changed by legislation.

A time zone identifier is therefore not a static piece of information like "this place is at UTC-5". It is a small program, encoded as data, that takes a UTC instant and returns the local civil time at that place. That is the layer of abstraction that makes everything else work.

The reason this matters: any system that stores time as a fixed UTC offset rather than an IANA identifier will silently produce wrong answers when DST starts, when DST ends, when a country changes its rules, and at every leap second. The IANA database is updated several times a year — `tzdata` releases like 2025a, 2025b, 2025c are published as countries adjust their policies — and consumers need to keep their copies current.

UTC, Coordinated Universal Time, is the reference signal. UTC ticks forward at the rate of International Atomic Time (TAI), which is the weighted average of about 400 atomic clocks distributed across national metrology labs, with leap seconds added when necessary to keep UTC within 0.9 seconds of the Earth's actual rotation. Every civil time zone on Earth is defined as a positive or negative offset from UTC.

How time zones evolved

Before 1884, there were no time zones. Each city kept its own local mean solar time, defined by the moment the sun was directly overhead at the local meridian. London ran twelve minutes ahead of Bristol; Pittsburgh was twenty minutes behind Philadelphia. The railways made this untenable: a railway timetable that listed departures in dozens of incompatible local times was a recipe for collisions.

The British railways adopted Greenwich Mean Time as a single standard in 1847. The American railroads followed in November 1883, dividing the country into four "Standard Railway Time Zones" by industry agreement, with no government involvement. A year later, in October 1884, the International Meridian Conference in Washington — twenty-five participating nations — voted 22 to 1, with two abstentions, to adopt the Greenwich meridian as the prime meridian and to base universal time on it. France abstained and continued to use Paris Mean Time until 1911.

The 1884 conference did not impose time zones. It adopted a reference. National adoption of zone-based civil time took another half-century: most countries had switched by 1930, but Liberia held out on a +0:44:30 offset until January 1972. Saudi Arabia ran on solar time at every locality until 1962. Nepal still uses a +05:45 offset — exactly the meridian time at Kathmandu — and has no plans to change.

The modern UTC standard was introduced on January 1, 1972. Before that, there were several civil-time references coexisting (GMT, GMT0, ephemeris time, atomic time as broadcast). The 1972 standard fused the steady-rate atomic-second of TAI with the slow drift of the Earth's rotation by introducing the leap second. Twenty-seven leap seconds have been added since 1972 — none subtracted — and the practice was officially scheduled for retirement at the 2022 General Conference on Weights and Measures, with the last leap second expected by 2035.

How many time zones are there?

The popular answer is 24 — once per hour around a 24-hour day. The popular answer is wrong.

There are 38 standard time zones currently in use. The discrepancy is in the half-hour and quarter-hour offsets. India, Sri Lanka, parts of Australia, and parts of Canada (Newfoundland, some indigenous communities) sit on half-hour offsets — UTC+05:30, UTC+09:30, UTC-03:30. Iran is on UTC+03:30 in winter. Nepal is on UTC+05:45. The Chatham Islands in New Zealand are on UTC+12:45. North Korea moved to a half-hour offset of UTC+08:30 in August 2015, then reverted to UTC+09:00 in May 2018 to align with South Korea. Venezuela ran on UTC-04:30 from 2007 to 2016, then reverted to UTC-04:00.

The minimum offset is UTC-12:00, used by Baker Island and Howland Island (uninhabited U.S. territories). The maximum is UTC+14:00, used by the Line Islands of Kiribati. The maximum difference between two places on Earth is therefore 26 hours, not 24. When it is noon Sunday in Kiritimati, it is 10:00 Saturday on Baker Island.

The number of zones is not even fixed. The total grew on December 30, 2011 when Samoa skipped a day to switch from UTC-11:00 to UTC+13:00, putting itself on the same calendar day as its main trading partners (Australia, New Zealand). The total will likely shrink again the next time a nation simplifies its civil-time policy.

For everyday work, the lookup that matters is the IANA identifier, not the offset. If you tell a calendar that a meeting is "at UTC+05:30", the calendar will be right today and wrong in three months when the host's country changes its rules. If you tell the calendar that the meeting is at "Asia/Kolkata", the calendar will continue to compute the right local time forever, because the rules update with every tzdata release.

DST: who observes it, and why

Daylight saving time is observed in roughly 70 countries, mostly in North America, Europe, and parts of Australia, New Zealand, Chile, and Paraguay. Most of the world does not observe it. China, India, Japan, South Korea, Russia, Turkey, most of Africa, most of the Middle East, and most of Southeast Asia keep their clocks on a fixed offset year-round.

Within the United States, every state except Hawaii and most of Arizona observes DST. The Navajo Nation, which spans Arizona, observes DST while the surrounding Arizona land does not, producing one of the most disorienting time-zone seams in the world. Within Australia, Queensland, the Northern Territory, and Western Australia do not observe DST while the southern and southeastern states do. Within Canada, most of Saskatchewan does not observe DST. Within Brazil, DST was abolished in 2019.

The legislative trend is uniformly toward abolition. Mexico abolished nationwide DST in October 2022, leaving only the northern border strip on the U.S. schedule. Iran abolished DST in 2022. Russia abolished DST in 2014. The European Parliament voted in 2019 to end mandatory clock changes by 2021, but the Council of the EU never adopted the proposal and as of 2026 every member state still switches.

The U.S. Sunshine Protection Act, which would lock the country on permanent daylight saving time, passed the Senate by unanimous consent in March 2022 but expired in the House without a floor vote. It was reintroduced in 2023 and 2025; it has not passed as of this writing. Several U.S. states have passed conditional legislation that would adopt permanent DST if federal law allowed it, which it does not.

Practical: how to think about time zones for travel and work

The most useful mental model for working with time zones is this: a moment in time is unambiguous; a wall-clock value is not. "16:00 UTC on Tuesday" describes a single instant on Earth. "4 PM on Tuesday" describes a different instant in every zone, and the same instant in zones with the same offset.

This has a few practical consequences.

For travel. Your phone will update to the local zone automatically as long as airplane mode was off when you crossed a boundary. Your laptop, if it is not connected to the cellular network, will not. Manually setting a laptop's clock to the local time is a mistake — it desynchronizes the laptop from servers and produces baffling errors in calendar invites. Use the operating system's "Set time zone automatically" toggle, or set the zone explicitly to the IANA identifier of your destination.

For booking. Hotel and airline systems display times in the local zone of the property or the airport. A 23:55 departure from JFK and a 02:30 arrival at LHR are described in JFK-local and LHR-local time respectively, not in your home zone. The booking system does not adjust for your home zone, and adding the events to your calendar without specifying the source zone will produce wrong reminders.

For distributed work. Use a time zone converter or meeting planner for any cross-zone scheduling, and pin recurring meetings to a single canonical zone (usually the host's). Read more in Meeting across time zones: the practical playbook.

For development. Store all timestamps in UTC. Convert to the user's zone at the very edge of the system — the rendering layer — and never anywhere else. The opposite mistake (storing in local time) introduces a permanent bug that surfaces every DST transition and every time a user travels.

For everyday reference. A world clock gives you the live state of major cities at a glance, city comparison gives you side-by-side overlap data, and market hours gives you trading-session windows for global exchanges. These are the spoke pages this guide aggregates.

Common mistakes

UTC vs GMT. UTC is the global atomic-time reference. GMT is the British civil time zone for Western Europe in winter. They agree to within a fraction of a second by design but they are not the same thing. Servers should log in UTC. Use "GMT" only as a human label for the United Kingdom and a handful of West African countries during their winter.

EST vs EDT. EST is Eastern Standard Time (UTC-5), used in winter. EDT is Eastern Daylight Time (UTC-4), used in summer. New York is on EST from early November to early March and on EDT for the rest of the year. Software that stores "EST" as if it meant New York time year-round is wrong by one hour for eight months a year. The only safe identifier is `America/New_York`.

Fixed UTC offsets. Storing "+05:30" as the user's time zone is wrong, because the offset is not the rule. India happens to be on +05:30 today, but if India ever changes its rules — and it has been debated several times — every "+05:30" record needs to be migrated. Store the IANA identifier; let the consumer compute the offset at render time.

Daylight saving as a regional concept. "DST starts on March 8" is a U.S.-specific statement. The EU starts DST on March 29 in 2026; Australia starts its own DST on October 4. Do not assume a date works globally — see the DST 2026 global overview for the per-country breakdown.

The International Date Line as a straight line. It is not. The line bends east around Kiribati to keep the country on a single calendar day, west around Samoa for the same reason, and east around the Aleutian Islands to keep all of Alaska on the same calendar day. The line zigzags by thousands of miles in the Pacific.

"My laptop is on UTC, so I'm fine." Until you fly somewhere and your calendar's recurring meetings drift, because the calendar was using UTC offsets rather than IANA identifiers internally. The fix is at the data-model level, not at the laptop level.

For more depth on any of these mistakes — and for live tools to fix them — see the time-zone reference index, the DST tracker, the meeting drift checker for recurring meetings, and the find-meeting-time tool for one-off scheduling. For trading-hours questions specifically, the market hours and market overlap pages are the ones to bookmark.