Reading the clock above
Every label on the panel maps to something you will meet in real systems. Here is what each piece tells you.
- The trailing
Z - Zero offset. Pilots, sailors, plus the military say "Zulu" out loud, from the NATO letter for Z. In an ISO 8601 string,
Zmeans the same thing as+00:00. - Your clock
- Wall time in the zone your operating system reports, such as
Asia/KarachiorAmerica/New_York. No location lookup happens. - The gap
- Hours plus minutes between the two hands. A positive gap means your day started earlier than UTC's. Near midnight the two clocks sit on different calendar dates, which the line under your clock flags.
- HTTP Date header
- The format web servers send in
Date:responses. The spec still spells the zone asGMT, yet every server means UTC. Leave the word alone when you write one by hand. - Unix time
- Seconds since 1970-01-01T00:00:00Z. The count ignores leap seconds, so one Unix "day" is always 86,400 seconds.
- ISO week
- Week numbers start on Monday, with week 1 holding the year's first Thursday. Payroll and sprint planning tools lean on this format, written like
2026-W39-4.
Who keeps UTC
No single master clock exists. The International Bureau of Weights and Measures (BIPM), outside Paris, collects readings from more than 400 atomic clocks in roughly 80 national labs. A weighted average of those clocks produces International Atomic Time, known as TAI.
UTC equals TAI minus a whole number of leap seconds. Today the difference is 37 seconds. BIPM publishes the official result once a month in a bulletin called Circular T, which means "true" UTC arrives weeks after the fact. Labs such as NIST in the US or NPL in the UK broadcast their own real-time versions, each within a few billionths of a second of the final figure.
Your laptop never talks to those clocks directly. Windows, macOS, plus most Linux distributions poll a Network Time Protocol server every so often, which traces back to one of those labs. Over normal internet links the result lands within tens of milliseconds, close enough for meetings, logs, plus cron jobs.
From Greenwich to atomic time
- 1884
Delegates from 25 nations meet in Washington, D.C. to pick Greenwich as the prime meridian. Mean solar time there becomes the world reference, GMT.
- 1960
The first version of UTC appears, built to keep radio time signals from different countries in step.
- 1967
The second gets a new definition: 9,192,631,770 oscillations of a caesium-133 atom. Earth's spin no longer defines the unit.
- 1972
UTC switches to the atomic second plus occasional leap seconds, starting 10 seconds behind TAI. The name UTC settles the order between English CUT and French TUC by picking neither.
- 2016
The 27th leap second lands on 31 December at 23:59:60. No leap second has been added since.
- 2035
The deadline set by the General Conference on Weights and Measures in 2022 to stop inserting leap seconds. UTC will drift slowly from the sun instead of jumping.
Offsets off the whole hour
Plenty of code assumes offsets land on whole hours. These zones prove otherwise, plus they mark the two ends of the range. If a scheduler rounds any of them, meetings slip by 30 or 45 minutes.
| Place | Standard offset | Worth knowing |
|---|---|---|
| Baker Island (US) | UTC−12:00 | Uninhabited. The last spot on Earth to finish a calendar day. |
| Marquesas Islands | UTC−09:30 | One of the few half-hour zones west of UTC. |
| Newfoundland | UTC−03:30 | Shifts to −02:30 in summer. |
| Iran | UTC+03:30 | Dropped daylight saving in 2022, so the offset holds all year. |
| India | UTC+05:30 | One zone for the whole country, over 1.4 billion people. |
| Nepal | UTC+05:45 | The 45-minute offset breaks most hand-rolled date code. |
| Chatham Islands (NZ) | UTC+12:45 | Moves to +13:45 during the southern summer. |
| Kiribati, Line Islands | UTC+14:00 | First to see each new date. 26 hours separate this zone from Baker Island. |
UTC stamps in the wild
Three places you will read UTC today, each written a little differently.
2026-09-24T14:32:08Z api.toolexe.com GET /json/beautifier 200 41msStore logs in UTC. Dashboards convert for whoever holds the pager.
METAR EGLL 241420Z 24012KT 9999 FEW030 17/09 Q1015241420Z reads as day 24, 14:20 Zulu. Heathrow reports in UTC even while London runs on BST.
Date: Thu, 24 Sep 2026 14:32:08 GMTThe word GMT here is fixed by the spec. The value is UTC. For the longer story on GMT versus UTC, read our UTC guide.
Where this clock falls short
- Your device sets the time. The page reads your system clock. A laptop off by two minutes shows UTC off by two minutes.
- Leap seconds never appear. Browsers smear or skip them, so you will never see
23:59:60here. Fine for scheduling, wrong for timing lab work or legal evidence. - One local zone only. The converter uses the zone your OS reports. Travel laptops pinned to a home zone show home time, not the airport you landed in.
- No past or future rule changes. Offsets follow the zone database shipped with your browser. A country changing its rules next year will not show up until your browser updates.
If your clock drifts
Compare the seconds above with a phone on mobile data. If the two disagree by more than a second or two, force a resync.
Windows 11
Settings, then Time & language, then Date & time. Turn on "Set time automatically", then press Sync now.
macOS
System Settings, then General, then Date & Time. Turn on "Set time and date automatically" with time.apple.com as the source.
Linux (systemd)
Run timedatectl set-ntp true, then check timedatectl status for "System clock synchronized: yes".
