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 most operating systems, programming languages and timekeeping services ultimately read from (Windows keeps its own time-zone list, mapped to IANA identifiers by libraries such as ICU).

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, and whenever a country changes its rules. The IANA database is updated several times a year: 2026 alone had releases `2026a` to `2026f`, covering changes in Canada, Morocco and Cuba, among others. 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 computed by the BIPM from several hundred atomic clocks in national metrology laboratories, 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 about ten minutes ahead of Bristol; Pittsburgh was about 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 kept an offset of −0:44:30 until January 1972. Nepal has used +05:45 since 1986, based on the meridian of 86°15′ E (near the Gauri Shankar peak) rather than Kathmandu.

UTC in its current form dates from January 1, 1972. Before that, broadcast time signals were adjusted in small steps and frequency offsets. The 1972 definition kept the atomic second of TAI and handled the slow drift of the Earth's rotation by inserting whole leap seconds. Twenty-seven leap seconds have been added since 1972, none subtracted, and none since the end of 2016 ^[3]. The 2022 General Conference on Weights and Measures decided to allow a larger difference between UTC and the Earth's rotation by or before 2035, which in practice ends leap seconds ^[4].

How many time zones are there?

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

Counting the distinct UTC offsets that populated places use, the answer is around 38 to 40, depending on the date and on how you count summer offsets. In IANA tzdata 2026e, 39 distinct offsets appear across the database's populated zones during 2027, from UTC−11:00 to UTC+14:00 ^[1]. The extra ones are half-hour and quarter-hour offsets. India and Sri Lanka use UTC+05:30, Australia's Northern Territory and South Australia UTC+09:30, Newfoundland UTC−03:30, and Iran UTC+03:30 all year. 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 ^[2]. Venezuela ran on UTC-04:30 from 2007 to 2016, then reverted to UTC-04:00.

The lowest offset is UTC−12:00, nominally assigned to Baker Island and Howland Island (uninhabited U.S. territories) and used as "Anywhere on Earth" time for deadlines. 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 set of offsets is not fixed. Samoa skipped December 30, 2011 to move its standard time from UTC−11:00 to UTC+13:00 (its clocks, then on daylight time, jumped from UTC−10:00 to UTC+14:00), putting itself on the same calendar day as Australia and New Zealand, its main trading partners. In 2026 British Columbia, Alberta, the Northwest Territories and Manitoba each stopped changing clocks, and Morocco moved back to UTC+00:00.

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−07:00" for a host in Denver, it will be right in winter and an hour off from March to November, when Denver moves to UTC−06:00. If you tell it "America/Denver", it computes the right local time for every date, and keeps doing so when the rules change, as long as its tzdata is updated.

DST: who observes it, and why

Daylight saving time is observed in about 68 countries and territories (by the IANA database's country codes), mostly in Europe and North America, plus parts of Australia, New Zealand and Chile. Most of the world does not observe it. China, India, Japan, South Korea, Russia, Turkey, almost all of Africa, most of the Middle East and all of Southeast Asia keep one offset all year.

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 and Yukon already did not change, and in 2026 British Columbia, Alberta, the Northwest Territories and Manitoba stopped too. Brazil abolished DST in 2019.

The trend is toward ending the twice-yearly change, but not always toward standard time. Mexico dropped DST in October 2022, except for the border strip that follows U.S. dates. Iran stopped after 2022. Russia stopped changing clocks in 2011 and settled on permanent standard time in 2014 ^[5]. Paraguay (2024) and the four Canadian jurisdictions (2026) chose permanent summer time instead. The European Parliament voted in 2019 to end mandatory clock changes, but the Council of the EU has never agreed a position, and every member state still switches.

The U.S. Sunshine Protection Act, which would put the country on permanent daylight saving time, passed the Senate in March 2022 but expired without a House vote. The 2025 version, H.R. 139, passed the House on July 14, 2026; as of November 5, 2026 the Senate has not voted on it. Nineteen states have laws that would adopt permanent DST if federal law allowed it, which it currently 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 updates to the local zone automatically once it connects to a local network, or from its location if automatic time zone is enabled. A laptop without a cellular connection depends on its automatic time-zone setting and location services; if either is turned off, it keeps the old zone. 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 21:30 departure from JFK and a 09:30 arrival at LHR the next morning are given 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, the meeting planner shows where working hours overlap, and the time zone converter converts a single moment on any date.

Common mistakes

UTC vs GMT. UTC is the global atomic-time reference. GMT is a civil time: the UK and Ireland use it in winter, and several West African countries, including Ghana, Senegal and Côte d'Ivoire, use it all year. The two agree to within a second, but they are not the same thing. Servers should log in UTC. Use "GMT" only as a human label.

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 about 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 (a second Indian time zone has been debated several times), every "+05:30" record would need to be migrated. Records that stored "−08:00" for Vancouver were already wrong every summer; since British Columbia moved to permanent UTC−07:00 in 2026, they are wrong all year. Store the IANA identifier; let the consumer compute the offset at render time.

Daylight saving as a regional concept. "DST started on March 8" was a U.S.-specific statement in 2026. The EU started DST on March 29; Australia's southern states started theirs 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 and around Samoa, so that each is on the same calendar day as its western neighbours, and west around the Aleutian Islands to keep all of Alaska on the same day. At the Kiribati bulge it runs more than 3,000 km from the 180° meridian.

"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.

To check any of these in practice, the DST tracker lists each country's next clock change, the meeting planner finds a slot across zones, and the time zone converter checks one occurrence on a specific date, which is how to catch a recurring meeting that moves in a DST transition week. For trading hours, see the stock market hours guide.

Glossary

UTC

Coordinated Universal Time, the primary time standard by which the world regulates clocks and time. UTC is derived from International Atomic Time (TAI) with leap seconds added to keep it within 0.9 seconds of mean solar time at the prime meridian. It is the successor to Greenwich Mean Time as the global civil-time reference and is used as the basis for every IANA time zone offset.

GMT

Greenwich Mean Time, the mean solar time at the Royal Observatory in Greenwich, London. GMT is used as civil time in the United Kingdom and Ireland in winter and in several West African countries all year. It is not the same as UTC: GMT is a civil time zone, while UTC is a global time standard.

IANA Time Zone Database

A public, machine-readable catalogue of every civil time zone on Earth, including historical offset rules, daylight-saving transitions, and zone abbreviations. Also called the Olson database after its original maintainer Arthur David Olson, it is identified by names of the form `Region/City` such as `America/New_York` or `Asia/Kolkata`. Operating systems, programming languages, and timekeeping services rely on it as the canonical source for local-time computation.

Daylight Saving Time

A seasonal practice of advancing clocks by one hour during warmer months so that evening daylight lasts longer, then reverting to standard time in autumn. About 68 countries and territories observe daylight saving time, mostly in Europe and North America, plus parts of the Southern Hemisphere. Most of Asia, Africa, South America and the tropics do not.

Civil Time

The local time legally adopted by a region for everyday use, including any government-mandated offset from UTC and any seasonal daylight-saving rule. Civil time is the time shown on public clocks and used in schedules, contracts, and broadcasts. It is distinct from solar time and from UTC.

Solar Time

The time at a location based on the position of the Sun, with local solar noon defined as the moment the Sun is highest in the sky. Mean solar time averages out seasonal variation in the Sun's apparent motion. Civil time at most longitudes is offset from local solar time, sometimes by more than an hour, as a side effect of zone consolidation.

Time Zone

A region of the Earth that has agreed to use the same standard time, defined as a fixed offset from UTC plus an optional set of daylight-saving rules. Around 38 to 40 distinct UTC offsets are in use, including half-hour and quarter-hour offsets such as India's UTC+05:30 and Nepal's UTC+05:45. The largest difference between two offsets in use is 26 hours, between UTC−12:00 (uninhabited Baker and Howland Islands) and UTC+14:00; between inhabited places it is 25 hours.

Leap Second

A one-second adjustment occasionally added to UTC to keep it aligned with the Earth's rotation. Twenty-seven leap seconds have been added since 1972, all positive; none has ever been subtracted. None has been added since 2016. The General Conference on Weights and Measures decided in 2022 to end the need for leap seconds by or before 2035.