A meeting invite that says “10:00 IST” looks precise. It isn’t. IST is India Standard Time (UTC+05:30), Irish Standard Time (UTC+01:00) and Israel Standard Time (UTC+02:00). In July, the first two are four and a half hours apart. CST can mean Chicago or Shanghai, 14 hours apart. BST is British Summer Time to a Londoner and Bangladesh Standard Time to someone in Dhaka. Three letters were never designed to identify a time zone uniquely, and a surprising number of scheduling mistakes come from treating them as if they were.

The most common collisions

The spread within a single abbreviation can be enormous. The two meanings of PST are 16 hours apart. The four meanings of CST span 15 and a half hours, from Chicago to Adelaide.

A time zone abbreviation is a label, not an identifier. “IST” alone points to three different UTC offsets on three continents, and only context says which one was meant. worldtimedata

IST: three countries, three offsets

India Standard Time is the most widely used meaning, covering well over a billion people at UTC+05:30 all year. Israel Standard Time applies in winter at UTC+02:00; in summer, Israel switches to Israel Daylight Time (IDT, UTC+03:00), so “IST” in July from an Israeli colleague is technically a winter label used out of season.

Ireland adds a legal twist. Under the Standard Time Act 1968, Ireland’s “standard time” was set one hour ahead of Greenwich. When the country returned to Greenwich time in winter, the Standard Time (Amendment) Act 1971 did not change that definition; it created a separate “winter time” instead. The result is that in Ireland, the S in IST stands for Standard, but Irish Standard Time is what the country observes in summer (UTC+01:00), while winter is legally GMT. The tz database, which computers use for local time, records exactly this: Europe/Dublin shows IST from late March to late October and GMT the rest of the year.

The practical consequence is seasonal. From late October to late March, “IST” cannot refer to Ireland at all, since Irish clocks are on GMT. From late March to late October, it can mean either Dublin or Bengaluru. A 10:00 IST call proposed from Dublin in July is 14:30 in India; the same time read as India’s IST is 05:30 in Dublin.

CST: Chicago and Shanghai are 14 hours apart

North America’s Central Standard Time is UTC−06:00. China Standard Time is UTC+08:00. That puts 14 hours between them in winter, and the gap is large enough that an error doesn’t just shift a meeting; it can move it to a different calendar day. Cuba Standard Time (UTC−05:00) sits an hour ahead of Chicago in winter. In Australia, the official abbreviation for the central zone is ACST (UTC+09:30), used in Darwin and, in winter, Adelaide, but its full name is Australian Central Standard Time, and the shortened “CST” still turns up in everyday use.

North American CST has its own internal problem. Most of the US and Canadian Central zone switches to Central Daylight Time (CDT, UTC−05:00) from March to November, but people keep writing “CST” all summer. Read literally, “3 p.m. CST” in July means 3 p.m. at UTC−06:00, which is 4 p.m. in Chicago. Saskatchewan, which stays on CST all year, is one of the few places where the label is always literally correct. The same standard-versus-daylight mix-up drives many Eastern and Pacific errors too, covered in our guides to EST and EDT and PST and PDT.

BST: summer in Britain, standard in Bangladesh

In the United Kingdom, BST is British Summer Time, UTC+01:00 from the last Sunday in March to the last Sunday in October. In Bangladesh, BST is Bangladesh Standard Time, UTC+06:00 all year. The two are five hours apart, and because the British meaning is seasonal, a “BST” timestamp in January almost certainly isn’t British.

The abbreviation has even changed meaning within Britain. From 1968 to 1971, the UK kept its clocks one hour ahead of GMT all year as an experiment, and during that period the time was officially called British Standard Time. Ireland ran the same experiment over the same years, which is how its summer offset ended up legally labeled “standard.”

PST and AST: the less obvious clashes

The Philippines made its abbreviation official by statute. The Philippine Standard Time (PST) Act of 2013, Republic Act No. 10535, requires government offices to display PST as supplied by the national weather and time service, PAGASA. Philippine PST is UTC+08:00, while the North American PST is UTC−08:00, so any team working between Manila and the US West Coast has to specify which PST it means.

AST is split between Atlantic Standard Time (UTC−04:00), used all year in Puerto Rico and in winter in Atlantic Canada, and Arabia Standard Time (UTC+03:00), used across much of the Arabian Peninsula and in Iraq. The gap is seven hours.

Why abbreviations were never unique

No international body assigns time zone abbreviations. Each country or community names its local time in its own language and habits, and three letters give only so many combinations. The one database that tracks civil time worldwide, the IANA tz database, treats abbreviations as display labels, not keys. Around 2016 and 2017, its maintainers began removing abbreviations that had been invented for convenience rather than drawn from real-world use, replacing them with numeric labels such as “+04.” Zones that genuinely use letters, like IST in Dublin and Kolkata or CST in Chicago and Shanghai, keep them, which is exactly why the same letters appear under several zones. That is also why the database names zones after cities, as explained in our article on the IANA time zone system: America/Chicago and Asia/Shanghai can never be confused, while CST can.

International standards avoid the problem by not using abbreviations at all. ISO 8601 and its internet profile, RFC 3339, express time zones only as numeric offsets, such as 2026-12-01T10:00+05:30.

How software guesses, and why it guesses wrong

When a program has to turn a bare abbreviation into an offset, it must pick one meaning, and different programs pick differently. Java’s documentation deprecates three-letter time zone IDs for precisely this reason, noting that CST could mean US Central Standard Time or China Standard Time and that Java can recognize only one of them. Its built-in mapping of short IDs then makes choices that surprise many users: “CST” becomes America/Chicago, “IST” becomes Asia/Kolkata, and “BST” becomes Asia/Dhaka, so a British Summer Time string parsed that way lands five hours off.

Email has its own bias. The internet message format standard, RFC 5322, recognizes only a handful of legacy North American names (EST, EDT, CST, CDT, MST, MDT, PST, PDT) plus UT and GMT, and treats them as obsolete. Any email header that says CST is, by that standard, US Central time, whatever the sender meant. Calendar apps, spreadsheets and scheduling tools each apply their own rules, so the same “09:00 IST” pasted into two tools can produce two different meetings.

Writing a time that nobody can misread

The fix is to give each time either a numeric UTC offset or a city. “10:00 UTC+05:30” or “10:00 India time (Kolkata)” can only mean one thing, and the same goes for “15:00 Dublin” or “09:00 America/Chicago.” For recurring meetings across borders, a city is safer than an offset, because a city carries its daylight saving rules with it: a weekly call set for “10:00 Chicago” stays at 10:00 in Chicago through the March and November clock changes, while one pinned to “UTC−06:00” drifts an hour for about eight months of the year. When an abbreviation arrives without context, the season is often the fastest tiebreaker. A “BST” in December is not British, an “IST” in December is not Irish, and a “CST” from a sender in Beijing is almost certainly not Chicago.