Most of the world's clocks differ from Coordinated Universal Time by a whole number of hours, which makes mental arithmetic easy and lulls software into assuming it is always true. It is not. Half-hour time zones cover more than a fifth of humanity, and a handful of places go further still, keeping clocks forty-five minutes off the hour. Any system that stores an offset as an integer will eventually be wrong about India.

This article lists the regions that keep half-hour time zones and quarter-hour offsets, explains the history that put them there, and sets out the practical problems they expose in software and in scheduling. Every value, whole or fractional, appears in the UTC offsets table.

Which Places Use Half-Hour Time Zones?

A little over a dozen regions do, and India is by far the largest. Its single offset of UTC+05:30 applies from the Arabian Sea to the border with Myanmar, and Sri Lanka keeps the same clock.

  • UTC+05:30: India and Sri Lanka, together well over a billion people on one fractional offset.
  • UTC+03:30: Iran, which held this offset through the abolition of its seasonal clock change in 2022.
  • UTC+04:30: Afghanistan, sitting between the Gulf and Pakistan on a value neither neighbour uses.
  • UTC+06:30: Myanmar and the Cocos (Keeling) Islands.
  • UTC+09:30: the Northern Territory and South Australia, the latter moving to UTC+10:30 for daylight saving.
  • UTC−03:30: Newfoundland and Labrador in Canada, the best-known fractional offset in the Americas.
  • UTC−09:30: the Marquesas Islands in French Polynesia.

Lord Howe Island deserves its own mention. It keeps UTC+10:30 in winter and shifts by only thirty minutes for daylight saving, to UTC+11:00, making it the only inhabited place anywhere whose seasonal transition is not a full hour.

The Quarter-Hour Zones

Three regions use offsets ending in :45, and they are the sharpest test of any date library. Nepal keeps UTC+05:45, the Chatham Islands of New Zealand keep UTC+12:45, and the tiny settlement at Eucla in Western Australia keeps UTC+08:45.

Nepal's value is the most quoted. The country moved to UTC+05:45 in 1986, a choice aligned to a meridian close to the Gaurishankar massif, and one that distinguishes its clocks from India's UTC+05:30 by exactly a quarter of an hour. The Chatham Islands sit forty-five minutes ahead of mainland New Zealand and observe daylight saving alongside it, so their summer offset is UTC+13:45 — among the highest in regular use anywhere.

Why Do Half-Hour Time Zones Exist?

Because standard time replaced local solar time, and some countries rounded to the nearest half hour rather than the nearest hour. Where the sun's true position fell awkwardly between two whole-hour meridians, a fractional offset kept civil noon closer to solar noon.

Before the late nineteenth century every town kept its own mean solar time, set by the sun's position on that longitude. Standardisation, driven by railways and telegraphs, replaced thousands of local times with a small set of shared ones — but the choice of which shared one was political as much as astronomical. India adopted a single national clock in 1906 based on the meridian at 82°30′ east, which lands exactly five and a half hours from Greenwich; Calcutta kept its own local time until 1948 before conforming. The fractional offset is not an accident but an accurate compromise for a country too wide for one hour and too narrow, politically, for two. The same reasoning produced most other half-hour time zones: a national clock closer to the sun than either neighbouring whole hour would have been.

Odder values than these once existed. Amsterdam kept a local mean time nineteen minutes and change ahead of Greenwich until 1937, and Liberia used an offset of forty-four and a half minutes behind it until 1972, the last country to move onto a round value. Historical records from those periods carry offsets with seconds in them, which is one reason the IANA time zone database stores rules at second precision rather than assuming minutes.

What Problems Do Half-Hour Time Zones Cause in Software?

They break every assumption that an offset is a whole number of hours. The failures are quiet: a dropdown that only lists hours, a stored integer column, a date library that rounds, an interface that renders 05:30 as 05:00 and loses half an hour.

  • Integer storage: an offset column typed as hours cannot hold +05:45 at all, so the value is truncated on write and never recovered.
  • Minute conventions: browsers report the offset in minutes and with an inverted sign, so a naive conversion produces a value that is both wrong in magnitude and wrong in direction.
  • Rounded pickers: meeting schedulers that snap to the hour make it impossible to express a slot that is sensible in Kathmandu.
  • Duration arithmetic: assuming that adding a day preserves the wall-clock time fails wherever a fractional offset combines with a daylight saving shift, as it does in South Australia and on Lord Howe Island.

The remedy for all of them is the same one that fixes most other time bugs: store an instant in Coordinated Universal Time along with a zone identifier, and let a maintained library work out whether the answer lands on the hour or on one of the half-hour offsets. That approach is set out in full in time zones for developers.

Are Any Offsets Not Multiples of Fifteen Minutes?

Not today. Every offset in current civil use is a multiple of fifteen minutes, which is why :00, :15, :30 and :45 are the only endings you will encounter. Historical rules are another matter, and pre-standardisation records contain values with seconds.

The fifteen-minute grid is a consequence of the Earth's rotation rather than a rule anyone wrote down: fifteen degrees of longitude correspond to one hour, so a quarter-hour step is a neat 3.75 degrees. No country has chosen a five- or ten-minute value in the modern era, though North Korea did briefly adopt UTC+08:30 between 2015 and 2018 before returning to UTC+09:00 — a half-hour zone that existed for barely three years.

How to Work With Half-Hour Time Zones

Treat the minutes as significant and never round them. When quoting a time to someone in India, Nepal or Newfoundland, give the full local value rather than the nearest hour, and state the zone by name rather than by abbreviation.

For scheduling, the practical trick is to fix the meeting in one participant's local time and convert outward, rather than trying to find an hour that is round everywhere — it will not exist. The time zone converter handles fractional offsets directly, and the world clock shows the live minutes as well as the hours, so an off-the-hour reading is immediately obvious. The way these values inflate the apparent number of zones is covered in how many time zones there are.

Conclusion

Half-hour time zones are not curiosities. India, Iran, Afghanistan, Myanmar, parts of Australia and Newfoundland all keep clocks thirty minutes off the hour, and Nepal, the Chatham Islands and Eucla go a quarter of an hour further. They exist because standard time had to compromise with solar time, and they persist because the compromise still fits. Assume fractional offsets in any system you build, quote the minutes when you write a time, and check the exact value in the UTC offsets table or from the timezones.now homepage.