World Time Zones and Daylight Saving Time: A Complete Guide

How Time Zones Were Born

Before railways, every city kept its own local solar time. When the sun was directly overhead, it was noon — and noon in London was a different moment from noon in Bristol, just 120 miles west. This worked fine when travel was slow, but railways changed everything.

In 1840, Britain's Great Western Railway adopted "Railway Time" (Greenwich Mean Time) to simplify timetables. By 1880, GMT became the legal time for all of Britain.

The global system was formalised in 1884 at the International Meridian Conference in Washington, D.C. Delegates from 25 nations agreed to divide the world into 24 time zones, each 15° of longitude wide, centred on the Prime Meridian at Greenwich, England.

UTC: The World's Reference Clock

Coordinated Universal Time (UTC) replaced GMT as the global time standard in 1972. Key facts:

• UTC is based on atomic clocks, not solar observation (unlike GMT)
• UTC and GMT show the same time in practice, but UTC is the formal standard
• All time zones are expressed as offsets from UTC: UTC+5:30 (India), UTC−5 (US Eastern), etc.
• The abbreviation "UTC" is a compromise between English ("CUT") and French ("TUC") — neither language "won"
• Leap seconds are occasionally added to UTC to keep it aligned with Earth's slowing rotation

Major Time Zones Explained

Unusual Offsets: Half-Hours and 45 Minutes

Not all time zones are whole-hour offsets from UTC. Several countries chose non-standard offsets to better align with their geographic position:

• UTC+5:30 — India (IST). A single zone for a country spanning ~30° of longitude. A compromise between east and west.
• UTC+5:45 — Nepal (NPT). Chose a 15-minute offset from India to assert national identity.
• UTC+9:30 — Australia's Northern Territory and South Australia (ACST).
• UTC+8:45 — Eucla, Western Australia (unofficial, used by ~200 people).
• UTC+12:45 — Chatham Islands, New Zealand. The most unusual offset in a sovereign territory.
• UTC+6:30 — Myanmar (MMT).
• UTC+3:30 — Iran (IRST).

China is the most extreme example of a single-zone policy: despite spanning five geographic time zones, all of China uses UTC+8 (Beijing Time). When it's noon in Beijing, it should be 9:00 AM in far-western Xinjiang by solar time — yet clocks show noon there too.

The International Date Line

The International Date Line (IDL) runs roughly along the 180° meridian in the Pacific Ocean. When you cross it:

• Travelling west (Asia → Americas): Skip ahead one day (Monday → Tuesday)
• Travelling east (Americas → Asia): Go back one day (Tuesday → Monday)

The IDL zigzags to avoid splitting countries. Kiribati pushed the line east in 1995 to keep all its islands on the same date, making it the first country to enter each new year (UTC+14 — the highest offset on Earth).

Daylight Saving Time

Daylight Saving Time (DST) is the practice of setting clocks forward by one hour during warmer months to extend evening daylight. The idea is attributed to Benjamin Franklin (1784), though the modern system was first implemented by Germany in 1916 during World War I to save coal.

How it works in the Northern Hemisphere:

• Spring forward: Clocks move ahead 1 hour (2:00 AM → 3:00 AM), typically in March
• Fall back: Clocks move back 1 hour (2:00 AM → 1:00 AM), typically in November

In the Southern Hemisphere (Australia, Brazil, Chile), the dates are reversed — DST runs from October to March/April.

The Debate: Is DST Still Worth It?

Arguments for DST:

• More evening daylight encourages outdoor activities and reduces crime
• Reduces artificial lighting costs (though savings are minimal with modern LEDs)
• Benefits retail and hospitality industries (more shopping hours in daylight)

Arguments against DST:

• Health studies show a spike in heart attacks and car accidents in the days after spring transitions
• Disrupts sleep cycles and circadian rhythms
• Creates scheduling chaos for international business and software systems
• Energy savings are negligible — increased air conditioning offsets reduced lighting
• Farmers generally oppose it (livestock don't observe clock changes)

Who Observes DST?

DST is observed by about 40% of the world's countries, concentrated in:

• North America: US (except Arizona and Hawaii), Canada (except Saskatchewan), Mexico (border regions only since 2022)
• Europe: All EU member states, UK, Switzerland, Norway
• Southern Hemisphere: Parts of Australia, New Zealand, Chile, Paraguay

Countries that do not observe DST include: most of Asia (China, Japan, India, South Korea), Africa, Russia (abolished in 2014), Iceland, and most equatorial nations (where daylight hours barely change year-round).

Tips for Scheduling Across Time Zones

1. Always specify the time zone. "Let's meet at 3 PM" is meaningless without a zone. Use "3 PM EST" or "3 PM UTC−5." Even better, use UTC for clarity.
2. Use the IANA time zone database. Instead of abbreviations (which can be ambiguous — "CST" is both US Central and China Standard), use location-based names like "America/Chicago" or "Asia/Shanghai."
3. Account for DST transitions. During the two weeks when the US has changed clocks but Europe hasn't (and vice versa), the usual time difference shifts by an hour.
4. Find overlapping work hours. For teams spanning more than 8 hours apart, consider async communication instead of meetings.
5. Use UTC for deadlines. "Due March 30, 23:59 UTC" is unambiguous worldwide.
6. Add multiple clocks to your phone/desktop. Keep your most frequent collaborators' time zones visible at a glance.

Time Zones in Programming

Time zones are one of the most error-prone areas in software development. Key principles:

• Store times in UTC. Always convert to UTC before storing in a database. Convert to local time only for display.
• Use the IANA tz database (e.g., "America/New_York") — never hardcode UTC offsets, because offsets change with DST.
• Never assume an offset is constant. "EST" is only valid half the year; the rest of the time it's "EDT."
• Don't assume 1 day = 24 hours. DST transition days are 23 or 25 hours long.
• Don't assume 1 year = 365 days — and similar for months. Use proper date libraries.
• Use established libraries: JavaScript's Intl.DateTimeFormat, Python's zoneinfo / pytz, Java's java.time.ZonedDateTime.

Tom Scott's famous "The Problem with Time & Timezones" video is required viewing for any developer who will work with time.