Published July 2026 · 7 min read
Every time you open a meeting scheduler and see "UTC+1" or "GMT-5," you're looking at the result of a 150-year struggle to make time predictable. Before 1883, if you traveled from New York to Chicago by train, you would have encountered at least 144 different local times — every town set its own clock by the sun. Getting a train schedule right was nearly impossible. Getting a train to not collide with another train was harder still.
This is the story of how we went from solar noon to coordinated atomic time — and why it still matters every time you schedule a meeting across time zones.
The Age of Solar Time
For most of human history, time was a local affair. Each town set its clocks to "high noon" — the moment the sun reached its highest point in the sky. Since the Earth rotates 15 degrees every hour, towns just a few miles apart would have slightly different solar times. This worked fine when travel was limited to the speed of a horse or a walking pace. Nobody needed Cleveland's time to match Pittsburgh's.
By the mid-1800s, North America had a patchwork of thousands of local times. A traveler moving from east to west would encounter a slightly different clock in every town. For railroads, which were rapidly stitching the continent together, this created chaos. A single train timetable in a major station might list dozens of different arrival and departure times for the same train — each tied to a different local time zone. Passengers missed connections. Worse, trains operating on a single track with conflicting time standards collided.
Britain Leads the Way: Railway Time
The United Kingdom faced this problem first. The world's first modern railway opened in 1825 with the Stockton and Darlington line, and by the 1840s the expanding rail network had made local timekeeping untenable. Stations couldn't list different times for every stop along a route. The solution came in 1847 when all British railway companies adopted a single "Railway Time" — what we now know as Greenwich Mean Time (GMT), based on the Royal Observatory in Greenwich, London.
In 1880, Britain became the first country to standardize time nationwide. GMT was adopted as the legal time for the entire country, making the UK the world's test case for coordinated timekeeping. The experiment worked: scheduling became predictable, rail accidents dropped, and passengers could actually make their connections.
The Man Who Missed His Train (and Changed the World)
Across the Atlantic, a Canadian railway engineer named Sir Sandford Fleming had a personal encounter with the timekeeping chaos. In 1876, Fleming missed a train in Ireland after misreading a timetable that listed the departure as "p.m." instead of "a.m." — a consequence of the inconsistent time notations used across different regions. Frustrated and stranded, Fleming didn't just grumble about it. He designed a solution.
Fleming proposed dividing the entire world into 24 time zones, each one hour apart, with a single prime meridian as the reference point. It was brilliantly simple: since the Earth rotates 360 degrees in 24 hours, each 15-degree band of longitude would correspond to one hour. He advocated tirelessly for the idea, and on November 18, 1883, the railroad companies of the United States and Canada adopted his system, creating four continental time zones: Eastern, Central, Mountain, and Pacific. At exactly noon on that day, every railroad clock in North America was synchronized to the new standard.
The dividing lines drawn that day are remarkably close to the ones we still use. The railroad companies — not governments — had effectively created the American time zone map.
The World Gets on the Same Clock
The North American experiment was a success, and the world took notice. In 1884, Fleming helped organize the International Meridian Conference in Washington, D.C. Delegates from 25 nations gathered to decide on a global standard. The outcome: Greenwich was chosen as the prime meridian (the zero-degree line of longitude), and the 24-time-zone system was adopted internationally. GMT became the world's reference time.
Not everyone adopted it immediately, though. The U.S. federal government didn't officially recognize the railroad time zones until 1918 — 35 years after the railroads had been using them. France held out until 1911, using Paris Mean Time retarded by 9 minutes and 21 seconds (essentially GMT in denial). Liberia was among the last holdouts, finally adopting a GMT-based time zone in 1972.
GMT vs. UTC: What's the Difference?
For most of the 20th century, GMT was the gold standard. But GMT has a problem: it's based on astronomical observation — the average time the sun crosses the prime meridian. The Earth's rotation isn't perfectly consistent; it slows down, speeds up, and wobbles. For precise scientific work, astronomers needed something better.
Enter atomic clocks. In 1955, the first practical caesium atomic clock was built at the UK's National Physical Laboratory. Atomic clocks measure time by counting the vibrations of caesium atoms — and they are staggeringly accurate, losing less than one second every 100 million years.
In 1960, the international community introduced Coordinated Universal Time (UTC), based on International Atomic Time (TAI). The name "UTC" itself is a diplomatic compromise: English speakers wanted "CUT" (Coordinated Universal Time), French speakers wanted "TUC" (Temps Universel Coordonné). UTC was the in-between that offended no one and satisfied nobody.
In practice, UTC and GMT display the same time. The difference is technical: GMT is an astronomical time standard, while UTC is an atomic time standard. When you see "UTC+5:30" for India or "UTC-8" for Los Angeles, you're using the atomic system — even though most calendars and meeting schedulers still colloquially say "GMT."
The atomic system also introduced leap seconds — occasional one-second adjustments added (or theoretically subtracted) to keep UTC aligned with the Earth's slightly irregular rotation. Since 1972, 27 leap seconds have been added. They're mostly invisible to end users, but they've caused notorious software bugs, including a 2012 outage that took down parts of Reddit, Mozilla, and Qantas's check-in system.
Why It Still Matters
The next time you're staring at a meeting invitation trying to figure out if 3 PM your time works for a colleague in Singapore, remember: you're participating in a system that was wrestled into existence by frustrated railway engineers, a Canadian who missed his train, and a room full of diplomats in 1884.
The 24-time-zone grid they designed isn't perfect. China, which spans five geographic time zones, uses a single Beijing time (UTC+8) nationwide — meaning sunrise in western China can happen at 10 AM. Nepal is offset by 45 minutes (UTC+5:45) rather than a full hour. Daylight saving time adds another layer of complexity that varies by country and even by year.
But for all its quirks, the system works. When you add San Francisco, London, and Tokyo to a meeting planner and instantly see the overlap, you're benefiting from 150 years of incremental progress — from solar noon to steam engines to caesium atoms. Not bad for a system born from missed trains and near-collisions.
Ready to put 150 years of time zone history to work? Add your team's cities — no railroad timetables required. Try the Time Zone Meeting Planner →