Skip to main content

Reference chart

Time Zone Abbreviations and UTC Offsets

By &Pixels, the studio that builds MyCalculator.to. Offsets are standard time. The note column says what happens in summer, where anything does.

Sixteen common zones with their offsets, and the five abbreviations that mean more than one thing, which is the reason meetings get missed.

What is a UTC offset?

A UTC offset is how far a local clock runs ahead of or behind Coordinated Universal Time, written as UTC-6 or UTC+5:30. It is unambiguous, which the three-letter abbreviations are not: those are conventions with no standards body behind them, and several of them collide outright.

CST is the worst. It is Central Standard Time at UTC-6, China Standard Time at UTC+8, and Cuba Standard Time at UTC-5. An invitation that says 3pm CST is fourteen hours ambiguous before anyone has considered daylight saving.

Common zones

AbbrNameOffsetNote
UTCCoordinated Universal TimeUTC+0the reference, never shifts
GMTGreenwich Mean TimeUTC+0UK winter; the UK uses BST in summer
BSTBritish Summer TimeUTC+1late March to late October
CETCentral European TimeUTC+1CEST, UTC+2, in summer
EETEastern European TimeUTC+2EEST, UTC+3, in summer
ISTIndia Standard TimeUTC+5:30also Irish and Israel Standard Time
CSTChina Standard TimeUTC+8one zone for the whole country
JSTJapan Standard TimeUTC+9no daylight saving
AESTAustralian Eastern StandardUTC+10AEDT, UTC+11, in southern summer
NZSTNew Zealand Standard TimeUTC+12NZDT, UTC+13, in summer
ESTEastern Standard TimeUTC-5EDT, UTC-4, in summer
CSTCentral Standard TimeUTC-6the other CST, and the collision
MSTMountain Standard TimeUTC-7Arizona stays on it year round
PSTPacific Standard TimeUTC-8PDT, UTC-7, in summer
AKSTAlaska Standard TimeUTC-9AKDT in summer
HSTHawaii Standard TimeUTC-10no daylight saving

The calculators behind this

Abbreviations that mean more than one thing

AbbrCould meanOffsets
CSTCentral, China, Cuba Standard TimeUTC-6, UTC+8, UTC-5
ISTIndia, Irish, Israel Standard TimeUTC+5:30, UTC+1, UTC+2
AMTAmazon, Armenia TimeUTC-4, UTC+4
BSTBritish Summer, Bangladesh StandardUTC+1, UTC+6
ECTEcuador, European Central TimeUTC-5, UTC+1

Writing a time that cannot be misread

  1. Write the offset, not the abbreviation. UTC-6 is unambiguous. CST could be three different zones fourteen hours apart.
  2. Use a city or an IANA zone name. America/Chicago carries its own daylight saving rules. A three-letter code carries none.
  3. Check whether either end observes daylight saving. Arizona, Japan and most of Asia do not, so the gap to them changes twice a year.
  4. Watch the fortnight in March and the one in October. Europe and North America switch on different dates, so the gap is briefly unusual.
  5. Store timestamps in UTC and convert on display. Every scheduling bug of this kind comes from storing a local time and losing the context.

For a specific pair of cities on a specific date, the time zone converter handles the daylight saving rules for both ends, which is the part a table cannot do. The abbreviation lookup resolves a code when somebody has sent you one and not said where they are.

Formula & Methodology

💡

Did you know? Nepal runs at UTC+5:45, one of a handful of zones offset by three quarters of an hour. It was set relative to the longitude of Kathmandu rather than rounded to a neat boundary, which is why scheduling software that assumes whole or half hours occasionally gets Nepal wrong.

Sources

  • IANA Time Zone Database, the reference implementation of zone rules and historical changes
  • International Telecommunication Union recommendation on Coordinated Universal Time
  • National Institute of Standards and Technology, time and frequency division

Common questions

Frequently Asked Questions

Both, and also Cuba Standard Time. Time zone abbreviations are conventions rather than a standard, and several collide: Central Standard Time is UTC-6 and China Standard Time is UTC+8, fourteen hours apart. If a meeting invitation says CST and the participants are on different continents, the abbreviation alone cannot tell them when it is.

In everyday use they name the same clock time, but they are not the same kind of thing. UTC is a time standard, maintained by atomic clocks and kept within a second of the Earth’s rotation. GMT is a time zone, the one the UK uses in winter before it moves to BST in summer. UTC never shifts for daylight saving; GMT as a zone effectively does.

Because daylight saving starts and ends on different dates in different places, and many countries do not observe it at all. London and New York are usually five hours apart, but for about two weeks in March and one in October they are four, because the two switched on different days. Japan, India and most of Asia never switch, so the gap to them moves whenever the other end does.

Most of Asia including Japan, China and India; most of Africa; Hawaii and most of Arizona in the United States; Queensland and Western Australia; and Saskatchewan in Canada. Because their clocks stay put, their offset from anywhere that does switch changes twice a year, which surprises people who assume the fixed-clock end is the stable one.

Give the UTC offset or an IANA zone name, not an abbreviation. "15:00 UTC-6" and "15:00 America/Chicago" are both unambiguous; "3pm CST" is not. For anything stored rather than displayed, keep it in UTC and convert at the point of display, which is the only approach that survives a daylight saving change without a migration.

More time tools

1 / 6