Skip to content
Basetime

Time zone abbreviations — what the letters actually mean

63 abbreviations, 5 of which mean more than one thing. CST is Central Standard Time in Chicago, China Standard Time in Shanghai and Cuba Standard Time in Havana — fourteen hours between the extremes and nothing in the letters to tell them apart. Every code here has its own page that reads a timestamp as all of its meanings at once, in your own clock.

63 of 63

The ones that mean more than one thing

Ordered by how much a wrong guess costs. The number is the gap between the furthest-apart meanings.

Three letters, no authority

Time zone abbreviations feel official. They are printed on flight confirmations, stamped into log files and offered in dropdowns, which gives the impression that somebody somewhere maintains them. Nobody does. They came out of railway timetables and radio schedules, region by region, decades before anything needed to parse them mechanically, and by the time software cared the collisions were already fixed in habit.

The IANA time zone database — the one your operating system ships — records which abbreviations a zone uses, but it cannot resolve them the other way. Given the string CST there is no correct answer, only three candidates. Most software handles this by picking whichever meaning its locale suggests, silently. That is where the missed meetings come from: not from an error message, but from a confident wrong answer.

The half that is not ambiguous has a subtler trap. Almost every code names one side of the daylight-saving year: CET is the winter form and CEST the summer one, EST winter and EDT summer, GMT winter and BST summer. Writing CET for a date in July is not obviously broken — it parses, it produces a time, and that time is an hour out. Software that emits the abbreviation from a server's own locale rather than the event's makes this mistake constantly.

The fix costs nothing. Write the IANA zone name, or an ISO 8601 timestamp with a numeric offset. A zone name carries the rules and survives the clocks changing; a numeric offset is unambiguous for the instant it describes. Three letters are neither, however familiar they look.

How to use this
  1. Search by the letters, by the country, or by the offset — “india”, “+05:30” and “IST” all find the same row.
  2. The filters narrow to the ambiguous codes, the summer-time forms, or the ones that never change.
  3. Open any code to convert a timestamp written with it into your own clock.

Worth knowing: This list covers the abbreviations in common use, not every string that has ever been emitted. Some software invents its own; when in doubt, trust the numeric offset over the letters.

FAQ

Are time zone abbreviations standardised?

No. There is no registry and no authority. They grew up regionally in timetables and broadcasting, and several regions independently landed on the same three letters, which is why a handful of them are genuinely ambiguous today. The IANA time zone database records them but does not adjudicate between them.

Which abbreviations are ambiguous?

5 of the ones in common use: AMT, BST, CST, IST, WST. The worst is CST, whose meanings are 14 hours apart.

What should I write instead?

The IANA zone name — Europe/Oslo, America/New_York — or an ISO 8601 timestamp with a numeric offset such as 2026-03-14T15:00:00+01:00. The zone name is the stronger of the two because it carries the daylight-saving rules and not just today's number.

Why does my calendar show a different abbreviation in summer?

Because most abbreviations name one half of the year. CET becomes CEST, EST becomes EDT, GMT becomes BST. They are one hour apart and both correct, on the right dates, which is exactly why a timestamp labelled with the wrong half is an hour out rather than obviously broken.