GMT versus UTC —
What Is the Real Difference?
Greenwich Mean Time and Coordinated Universal Time are often used interchangeably — but they are not the same thing. The difference of up to 0.9 seconds may seem trivial, yet in aviation, GPS, stock trading, and internet infrastructure it matters enormously.
What does GMT mean — and what does UTC mean?
Both represent the "base time" against which every time zone on Earth is calculated, but the methods each uses to determine that time are fundamentally different — one is astronomical, the other is physical.
GMT is the mean solar time at the Prime Meridian (0° longitude), which passes through the Royal Observatory in Greenwich, London. It was defined in 1884 as the universal reference for navigation and railways.
"Mean" refers to the fact that it does not follow the real Sun (which moves unevenly due to Earth's elliptical orbit) but a fictitious "mean Sun" moving uniformly along the ecliptic.
GMT is an astronomical measure — it depends on Earth's rotation, which slows imperceptibly over time.
UTC is the official international time standard, adopted in 1960. It is based on TAI (International Atomic Time) — the weighted average of ~450 atomic clocks in 80 laboratories worldwide.
Atomic clocks measure the second based on energy transitions of caesium-133 atoms — accurate to 1 second in 300 million years.
UTC stays synchronised with Earth's rotation by periodically adding leap seconds — announced by IERS.
GMT vs UTC — side by side
A comprehensive table of all technical, historical, and practical differences between the two time reference systems.
Atomic clocks and the leap second
UTC is the result of a dual challenge: maintaining an extremely precise time (via atomic physics) AND staying synchronised with Earth's real, imperfect rotation. Here is how that tension is resolved.
Earth's rotation is not uniform. Tidal friction (the Moon's gravitational pull), redistribution of glacial masses, mantle convection, and even major earthquakes — all of these imperceptibly alter the rotation rate.
TAI atomic clocks (Temps Atomique International) run perfectly, but Earth "slips" against them by about 1–2 milliseconds per day. Over time, this difference accumulates.
The solution: IERS (International Earth Rotation and Reference Systems Service) continuously monitors the UTC−TAI difference and, when it approaches ±0.9 seconds, announces the addition or removal of a leap second.
What does a leap second look like?
→ 00:00:00
(60 seconds)
→ 23:59:60 ← the extra second!
→ 00:00:00
(61 seconds)
GMT and UTC in real time
Both displays show virtually the same moment — the sub-1-second difference is not visible at this level of precision.
Why does the difference matter in practice?
Confusing GMT with UTC — or using one in place of the other in technical contexts — can cause real errors in critical systems. Here are the domains where the choice counts.
ICAO (International Civil Aviation Organization) mandates UTC as the absolute standard for all flight plans, ATC communications, and flight logs. Pilots do not say "GMT" on the radio — they say "Zulu" (Z), which means UTC±0. Every commercial flight from New York to London uses UTC throughout its documentation.
UTC mandatoryThe GPS system has its own timescale (GPS Time), which is actually TAI minus 19 seconds — not UTC! GPS Time has no leap seconds, unlike UTC. Receivers calculate the conversion automatically. A 1-microsecond error in GPS equals ~300 m of positioning error.
GPS Time ≠ UTC ≠ GMTNTP (Network Time Protocol) synchronises servers to UTC. All Unix timestamps (Unix Epoch) are in UTC. ISO 8601 and RFC 3339 — the standards for date/time in APIs — use UTC. Server logs, databases, emails — all officially use UTC.
NTP · ISO 8601 · RFC 3339NYSE, LSE, Euronext and all major exchanges use UTC for transaction timestamps. MiFID II (the EU regulation) mandates microsecond-precision timestamps in UTC. A GMT/UTC mix-up in HFT (High Frequency Trading) systems can generate trades with invalid timestamps.
MiFID II · MicrosecondInternational contracts, treaties, and legislation use UTC as the reference. Writing "GMT+2" in a contract can be legally ambiguous when the UK is on BST (UTC+1) — which it is for roughly half the year. ISO 8601 format (2025-06-15T18:00:00+02:00) is unambiguous year-round.
ISO 8601 recommendedTelecoms networks synchronise base stations to nanosecond precision using UTC via GPS. A synchronisation error can cause radio interference or handover failures. PTP (Precision Time Protocol, IEEE 1588) uses UTC and explicitly manages leap seconds.
PTP · IEEE 1588 · ns precisionGMT and UTC — real-world examples
How does the GMT/UTC distinction play out in real situations? These examples are calculated dynamically based on the current date and time, including Daylight Saving Time transitions.
UT0, UT1, UT2, TAI, GPS — all forms of universal time
There is an entire family of time standards, each with a specific role in science, navigation, or computing. Here is how they all relate to GMT and UTC.
The raw universal time, calculated directly from astronomical observations of the Sun or stars at a specific observatory. Not corrected for polar motion of Earth.
UT0 corrected for polar motion (latitude variation). UT1 is the standard astronomical measure of Earth's rotation. UTC is kept within max ±0.9 s of UT1 via leap seconds.
UT1 further corrected for seasonal variations in Earth's rotation (caused by shifts in atmospheric and oceanic masses). Rarely used today; superseded by UTC.
Pure atomic time, with no leap seconds. TAI is 37 seconds ahead of UTC (as of 2025). The mathematical foundation of UTC. Used in metrology and fundamental physics; not directly mapped to time zones.
GPS Time = TAI − 19 seconds. No leap seconds — it started synchronised with UTC in January 1980 and has never been adjusted since. GPS Time is 18 seconds ahead of UTC (2025). Receivers convert automatically.
Used in astronomy for theoretical orbital calculations. TT = TAI + 32.184 seconds. The offset originates from the pre-atomic era when TT was defined relative to Ephemeris Time (ET). No direct link to time zones.
The UK's Daylight Saving Time = UTC+1. Important: London in summer is NOT on GMT — it is on BST (UTC+1). GMT is the UK's winter time zone. Confusing GMT with "London time" year-round is one of the most common misconceptions.
Military and aviation designation for UTC±0. Comes from the NATO phonetic alphabet (Z = Zulu). A pilot says "08:30 Zulu" = 08:30 UTC. ISO notation: 2025-06-15T10:30:00Z — the trailing Z means UTC.
The number of seconds elapsed since 1 January 1970, 00:00:00 UTC. The basis of timestamps in all Unix/Linux systems. Does not include leap seconds — hence it differs from TAI. Used in databases, APIs, and file systems worldwide.
How GMT and UTC apply to major global cities
The GMT/UTC distinction becomes concrete when you look at how major world cities relate to the reference — especially London, which only equals GMT in winter. All values are calculated dynamically, including DST transitions.
London is on GMT (= UTC±0) only in winter. In summer it switches to BST (UTC+1). Saying "London is always on GMT" is incorrect for roughly half the year.
The US switches DST on the 2nd Sunday of March; Europe on the last Sunday of March — creating a ~2-week window each spring when the NYC–London gap differs from the usual value.
Los Angeles follows US DST rules (2nd Sunday March / 1st Sunday November). The LA–London gap changes with the DST schedule of each region.
calculating…
When to use GMT and when to use UTC?
A simple rule for choosing correctly in any situation — from casual conversation to technical documentation.
Use GMT when…
- → Speaking informally about London time or the UTC±0 zone
- → Reading BBC schedules or British press releases
- → Discussing historical maritime navigation
- → General conversation — GMT = UTC in everyday use
Use UTC when…
- → Writing code, APIs, databases or any IT systems
- → Drafting international contracts or legal documents
- → Expressing any UTC offset (UTC+5:30, UTC−8, UTC+9, etc.)
- → Scheduling international meetings, flights, live broadcasts
- → Any technical or official context
From the Greenwich Meridian to atomic clocks
The transition from GMT to UTC took almost 80 years and involved technological revolutions, geopolitical negotiations, and a surprising naming decision (why not CUT or TUC?).
FAQ — GMT vs UTC
The most common questions and misconceptions about GMT, UTC, and their application in everyday life.
• Winter (last Sunday October → last Sunday March): London is on GMT = UTC±0
• Summer (last Sunday March → last Sunday October): London is on BST (British Summer Time) = UTC+1 — NOT GMT!
The common error: "London is always on GMT" — false! In summer, London is 1 hour ahead of GMT/UTC.
• Full format: 2025-06-15T14:30:00Z (Z = UTC)
• With explicit offset: 2025-06-15T09:30:00−05:00 (New York in winter)
• Informal format: "14:30 UTC" or "14:30 UTC±0"
• Avoid: "14:30 GMT" (ambiguous in summer), "14:30 GMT+2" (non-standard)
For meetings: use a Global Meeting Planner to calculate the correct time for every participant.