Time Zone Abbreviations: Why CST, IST and BST Are Ambiguous
CST, IST, BST and AST each name several different time zones, and EST is often used in summer when it is wrong. What the common abbreviations mean and what to use instead.
Time zone abbreviations are not standardised and not unique. CST can mean US Central Standard Time (UTC−6), China Standard Time (UTC+8) or Cuba Standard Time (UTC−5); IST can mean India, Ireland or Israel; BST can mean British Summer Time or Bangladesh Standard Time. For anything that matters, give a UTC offset or an IANA zone name such as America/Chicago instead.
EST, EDT and ET
The most common mistake is not an ambiguous abbreviation but a wrong one. US Eastern time has two offsets:
- EST, Eastern Standard Time: UTC−5, used from early November to mid-March.
- EDT, Eastern Daylight Time: UTC−4, used for the rest of the year.
Many people write “EST” all year to mean “whatever the clock in New York says”. In summer that is wrong by an hour: 15:00 EST is 16:00 in New York in July. Software that takes the label literally will put the event at the wrong time.
When the season does not matter, ET (Eastern Time) — or CT, MT, PT — is the correct generic label: it means the local time in that zone, whichever offset is in force. The same pattern applies elsewhere: GMT and BST in the UK, CET and CEST in much of Europe, AEST and AEDT in eastern Australia.
The ambiguous ones
These meanings are taken from the IANA time zone database, which supplies the abbreviations shown by most operating systems, and checked against the offsets it gives for 2027.
| Abbreviation | Meaning | UTC offset | Example zone |
|---|---|---|---|
| CST | Central Standard Time (North America) | −6 | America/Chicago |
| CST | China Standard Time | +8 | Asia/Shanghai |
| CST | Cuba Standard Time | −5 | America/Havana |
| IST | India Standard Time | +5:30 | Asia/Kolkata |
| IST | Irish Standard Time (summer time in Ireland) | +1 | Europe/Dublin |
| IST | Israel Standard Time | +2 | Asia/Jerusalem |
| BST | British Summer Time | +1 | Europe/London |
| BST | Bangladesh Standard Time (common usage) | +6 | Asia/Dhaka |
| AST | Atlantic Standard Time | −4 | America/Halifax |
| AST | Arabia Standard Time (common usage) | +3 | Asia/Riyadh |
| GST | Gulf Standard Time (common usage) | +4 | Asia/Dubai |
A few notes on the table:
- Cuba uses CST and CDT (UTC−4) in summer, so in July “CDT” can mean Chicago (UTC−5) or Havana (UTC−4).
- Ireland is unusual. Irish law defines “standard time” as UTC+1, so IST is the summer label and the winter time is GMT. The time is the same as London’s all year; only the name differs.
- Israel uses IST in winter and IDT (UTC+3) in summer.
- For Bangladesh, Saudi Arabia and the UAE, the abbreviations BST, AST and GST are in everyday use, but the IANA database itself shows numeric labels (
+06,+03,+04) for these zones. The site’s GST page covers the Gulf meaning.
Context usually resolves the ambiguity — an Indian company writing “IST” means India — but a calendar invite, log file or parser has no context. A program that reads “CST” has to guess, and different libraries guess differently.
The IANA database is moving to numbers
The IANA time zone database (also called the tz or Olson database) is the reference most computers use for time zones. Its abbreviations are for display only and were never a registry. Older releases contained abbreviations that the maintainers had invented for zones with no established English one.
The current policy, set out in the database’s own documentation, is the opposite: if there is no common English abbreviation, use a numeric offset. Release 2017a, for example, switched South America to numeric abbreviations “as part of the ongoing project of removing invented abbreviations”. The same documentation warns application writers that abbreviations “are ambiguous in practice”, citing CST and IST, and recommends numeric offsets instead. Many zones now display that way. With the system tz data (version 2026c), these zones show:
| Zone | Displayed abbreviation |
|---|---|
| Asia/Dubai | +04 |
| Asia/Singapore | +08 |
| Asia/Dhaka | +06 |
| Asia/Kathmandu | +0545 |
| America/Sao_Paulo | -03 |
Zones with long-established abbreviations keep them: America/Chicago still shows CST/CDT, Asia/Tokyo shows JST, Europe/Moscow shows MSK.
Display libraries can add their own names on top. A browser formatting a Dubai time with the Intl API in British English shows “GST”, taken from the Unicode CLDR locale data, while the same browser in US English shows “GMT+4”. The abbreviation you see depends on the software and the language setting, which is one more reason not to rely on it.
Common abbreviations and their offsets
| Abbreviation | Name | UTC offset | Daylight counterpart |
|---|---|---|---|
| UTC | Coordinated Universal Time | 0 | none |
| GMT | Greenwich Mean Time | 0 | BST (UK), IST (Ireland) |
| WET | Western European Time | 0 | WEST, +1 |
| CET | Central European Time | +1 | CEST, +2 |
| EET | Eastern European Time | +2 | EEST, +3 |
| MSK | Moscow Time | +3 | none |
| IST | India Standard Time | +5:30 | none |
| SGT | Singapore Time | +8 | none |
| JST | Japan Standard Time | +9 | none |
| KST | Korea Standard Time | +9 | none |
| AEST | Australian Eastern Standard Time | +10 | AEDT, +11 (not Queensland) |
| NZST | New Zealand Standard Time | +12 | NZDT, +13 |
| AST | Atlantic Standard Time | −4 | ADT, −3 |
| EST | Eastern Standard Time | −5 | EDT, −4 |
| CST | Central Standard Time | −6 | CDT, −5 |
| MST | Mountain Standard Time | −7 | MDT, −6 (not most of Arizona) |
| PST | Pacific Standard Time | −8 | PDT, −7 |
| AKST | Alaska Standard Time | −9 | AKDT, −8 |
| HST | Hawaii Standard Time | −10 | none |
The full list includes the remaining abbreviations the site covers.
What to use instead
- In software, store an IANA zone identifier such as
America/Chicago,Asia/ShanghaiorEurope/Dublin. It is unique, and it carries the full history of the zone’s offsets and daylight saving rules. The IANA zone list has every identifier. - For timestamps, store UTC or include the offset:
2027-03-20T14:00:00-05:00is unambiguous;2027-03-20 14:00 CSTis not. - For people, use a city or zone name, with UTC alongside: “14:00 Chicago time (19:00 UTC)”. The offset tells the reader the exact moment; the city tells them how it will move when the clocks change.
- If you must use an abbreviation, use the generic form (ET, CT, PT) or the one that matches the season, and only where the audience shares the context.
A bare offset is precise for a single moment but does not say when it will change: UTC−5 is Chicago in summer, New York in winter, and Bogotá all year. That is why software needs the zone identifier and people benefit from both.
Sources
- Theory and pragmatics of the tz code and data (IANA)
- IANA Time Zone Database
- Daylight Saving Time (NIST Time and Frequency Division)
Dates, offsets and astronomical times quoted here are computed with the same code that powers the site's tools — see data sources and methods. Found an error? Tell us.