Before 1883, every city in the United States kept its own time. Chicago ran on Chicago solar time. New York ran on New York solar time. Boston ran about 11 minutes ahead of New York. None of this was a problem when travel between cities took days by horse or weeks by ship. It became a catastrophic logistical problem when the railroads arrived.

The Louisville and Nashville Railroad, operating in the 1870s and 1880s, published a schedule that required passengers to reconcile times in Louisville, Nashville, Memphis, and New Orleans, each running on its own local solar standard. A passenger changing trains in Louisville needed to know that the connecting departure was given in Louisville time, not the city they had come from. The same train could depart at different times depending on which station clock you were looking at. Collisions happened. Not metaphorically.

The solution did not come from governments. It came from railroad companies.

Noon at the telegraph office

On November 18, 1883, at exactly 12:00 noon Eastern Standard Time, the United States Naval Observatory transmitted a time signal by telegraph to cities across the country. Railroad stations set their clocks to the new standard. In Chicago, the city had been running 9 minutes and 32 seconds ahead of what would now be Central Standard Time. At noon, the clocks were adjusted.

Newspapers called it “the day of two noons.” Chicago experienced noon twice: once at local solar noon, and once when the railroad time signal arrived.

The system divided North America into four zones: Eastern, Central, Mountain, and Pacific. Each was exactly one hour apart. The boundaries followed railroad networks, not geographic meridians. This is why time zone boundaries have always looked like strange political borders rather than clean north-south lines.

The United States Congress did not formalize the time zone system until the Standard Time Act of 1918, thirty-five years after the railroads had already made it work.

The 1884 conference

The railroad solution was national. But ships, telegraphs, and international commerce needed something global.

In October 1884, forty-one delegates from twenty-five nations gathered in Washington D.C. for the International Meridian Conference. The agenda was simple: establish a single prime meridian from which all longitude and time would be measured.

The British delegation made the obvious argument. More ships already used Greenwich charts than any other reference. The British Empire covered a quarter of the globe’s surface. Adopting Greenwich as the prime meridian would require the minimum number of adjustments to existing navigational infrastructure.

The French delegation proposed a neutral meridian, one running through Paris or through the Azores, to avoid giving any one nation symbolic dominance. They were outvoted.

Greenwich was confirmed as the prime meridian. The conference recommended dividing the world into 24 time zones of one hour each, centered on meridians 15 degrees apart (since the Earth rotates 15 degrees per hour). Time zones would be expressed as positive or negative offsets from Greenwich.

The conference also recommended that the universal day begin at midnight, not at noon as astronomical convention had it. This was a practical concession to civilian usage.

France refused to adopt Greenwich Mean Time until 1911, and even then framed it in official communications as “Paris Mean Time retarded by 9 minutes 21 seconds.” The grudge took decades to fully dissolve.

Why 37 offsets, not 24

The theory was 24 zones. The reality is considerably messier.

The IANA timezone database, which is the authoritative source for timezone information used by operating systems, programming languages, and services worldwide, currently contains offsets that deviate from clean one-hour increments in ways that make any map look like it was drawn by committee. Which it was, repeatedly, over many decades.

India uses UTC+5:30. Its refusal to split into two zones, which would put the eastern and western coasts in different hours, is a deliberate act of national unity. The country is wide enough that UTC+5:30 puts sunrise at different times in Assam versus Gujarat, but political considerations won out over solar precision.

Nepal uses UTC+5:45. This is 15 minutes ahead of India, a distinction Nepal maintains partly to assert its independence from its neighbor’s time standard. Nepal is the only country in the world on a 45-minute offset.

Iran uses UTC+3:30. Afghanistan uses UTC+4:30. Myanmar uses UTC+6:30. The Chatham Islands, a New Zealand territory in the Pacific, use UTC+12:45 in standard time and UTC+13:45 during daylight saving.

Australia has three standard time zones (UTC+8, UTC+9:30, UTC+10) and the state of South Australia adds the half-hour offset to its own region. Lord Howe Island, a small Australian territory in the Tasman Sea, observes a 30-minute daylight saving adjustment rather than the standard 60 minutes.

These are not accidents. Each is the product of a specific political, geographic, or historical decision.

China’s single time zone

China spans five natural geographic time zones. China observes exactly one.

After the 1949 revolution, the People’s Republic of China unified the entire country under Beijing Standard Time, UTC+8. This was a deliberate centralizing decision: one country, one government, one time.

The practical consequences at the western edge are extreme. In Kashgar, a city in Xinjiang province, UTC+8 means the sun rises after 10am in winter. People in Xinjiang largely operate on informal “Xinjiang time,” two hours behind Beijing time, for daily life. Schools and businesses may post two times on their schedules: official Beijing time and local practice time. The Chinese government officially recognizes only one.

This is time as a political instrument. The refusal to acknowledge regional time differences is a statement about national cohesion.

The International Date Line and the 37th offset

The date line introduces the final complication. As time zones advance eastward from UTC, they eventually reach UTC+14, which is 14 hours ahead of London. This is not a typo. It exists because of Kiribati.

In 1995, the Republic of Kiribati moved its eastern islands, which straddle the 180-degree meridian, from UTC-12 to UTC+14. Before this, the Phoenix Islands and Line Islands were in the previous calendar day from the main Gilbert Islands. A country spread across three time zones was operating in three different calendar days.

The decision meant Kiribati was the first nation to enter the year 2000. It also created UTC+14, making the theoretical maximum offset 26 hours (from UTC-12 to UTC+14), which is the actual span of time zones on Earth at any given moment.

The full timezone list shows all current offsets and the territories that observe them.

Railroads, empires, and coordinates

The shape of every time zone boundary reflects the historical moment in which it was drawn.

In colonial Africa, time zone boundaries often follow the borders inherited from the 1884 Berlin Conference, which divided the continent among European powers. Those borders frequently cut across ethnic, geographic, and linguistic lines. Time zones followed those borders rather than geographic logic.

In the Middle East, Saudi Arabia uses UTC+3, which is geographically reasonable. But the Arabian Peninsula has been subject to enough political realignment that neighboring countries like Yemen, Oman, and the UAE have slight variations that reflect the independent paths of their modernization processes.

In North America, the mountain time zone runs in jagged lines through the western states and Canada, following railroads that were built through specific mountain passes. The shape of the Pacific time zone through Idaho reflects a political battle between agricultural and coastal commercial interests in the 1880s.

Daylight saving: the additional layer

Time zones describe the standard offset. Daylight saving time adds another variable.

Most countries in the northern hemisphere, and some in the southern hemisphere, advance their clocks by one hour during summer months. The rationale, first seriously proposed by George Vernon Hudson, a New Zealand entomologist, in 1895 and separately by British builder William Willett in 1907, was to align working hours with available daylight.

Germany and Austria-Hungary adopted it first during World War I, in 1916, as a fuel conservation measure. Britain followed weeks later. The United States adopted it during both World Wars and made it permanent with the Uniform Time Act of 1966.

The result is that the same location may observe two different UTC offsets in the same year. New York is UTC-5 in winter (Eastern Standard Time) and UTC-4 in summer (Eastern Daylight Time). London is UTC+0 in winter (GMT) and UTC+1 in summer (BST, British Summer Time).

Countries at or near the equator generally skip daylight saving entirely. The variation in sunrise time between their winter and summer is small enough to make the transition pointless. Singapore, which sits just north of the equator, tried daylight saving in the 1970s and abandoned it. The annual clock change caused more disruption than it prevented.

The IANA database: the actual source of truth

Every modern operating system, programming language, and internet service that handles time zones correctly does so by referencing the IANA timezone database, also called the Olson database after Arthur David Olson, who created and maintained it from 1986 until IANA took over management.

The database contains not just current timezone rules but the complete historical record of every timezone change made since roughly 1970, and in many cases earlier. It tracks not just offsets but the specific rules by which daylight saving transitions occur, including historical changes to those rules.

This is more important than it sounds. In 2007, the United States extended daylight saving time by three weeks. Every device that handled calendar appointments needed to know that meetings scheduled for March 2007 in New York would have a different UTC offset than the same calendar appointment in previous years. The IANA database provided the historical rule.

Turkey moved from UTC+2 to UTC+3 permanently in 2016, abolishing daylight saving time in the same move. Brazil abolished daylight saving in 2019. Russia moved several regions in various years. Each of these changes is a versioned entry in the IANA database, which releases updates multiple times per year.

The timezones reference page on this site reflects the current IANA database. The database itself is available at the IANA website and is updated any time a government changes its time rules.

Solar time never fully went away

GPS satellites carry atomic clocks. Your phone gets its time from those satellites and from network time servers. The accuracy is within milliseconds.

And yet. Farmers in rural parts of many countries still orient their days around solar noon, regardless of what the clock says. Fishing schedules follow tides, which follow the Moon, not time zones. Religious observance in Judaism, Islam, and some Christian traditions ties prayer times to sunrise and sunset, which are celestial events rather than civic ones.

The railroad time that replaced solar time was itself a kind of fiction: a social agreement that a place called Chicago would pretend it was not nine minutes and thirty-two seconds earlier than the sun suggested. The agreement was useful. It enabled industrialization, global trade, and coordinated communication. But it was a negotiated reality, not a natural one.

Time zones are, in the end, a political product distributed over a geographic surface. The lines on the map are decisions made by governments, railroad companies, colonial administrators, and international conferences, each optimizing for a different combination of commercial convenience, national unity, and geographic logic. The result is a system that works well enough for most purposes and fails interestingly at the edges.

Sources

  • Bartky IR. Selling the True Time: Nineteenth-Century Timekeeping in America. Stanford University Press, 2000.
  • International Meridian Conference. Proceedings of the International Conference Held at Washington for the Purpose of Fixing a Prime Meridian and a Universal Day. 1884.
  • Downing M. Spring Forward: The Annual Madness of Daylight Saving Time. Counterpoint, 2005.
  • IANA Time Zone Database. iana.org/time-zones
  • Howse D. Greenwich Time and the Longitude. Philip Wilson Publishers, 1997.
  • United States Standard Time Act, 1918. Public Law 65-106.
  • Uniform Time Act of 1966. Public Law 89-387.
  • Blaise C. Time Lord: Sir Sandford Fleming and the Creation of Standard Time. Pantheon Books, 2000.