Why some places are 45 minutes out
Whole-hour offsets are a convention, not a rule. Several hundred million people live somewhere that is thirty or forty-five minutes off the hour — and code that rounds is wrong for all of them.
They are not exotic
The assumption that time zones come in whole hours is one of the most widespread wrong beliefs in software. Asked at a fixed instant — 15 January 2026, 12:00 UTC — the platform’s own zone data reports:
Asia/Kolkata— +05:30Asia/Kathmandu— +05:45Australia/Eucla— +08:45Pacific/Chatham— +13:45
India alone puts well over a billion people on a half-hour offset. This is not an edge case tucked away in a corner of the map; it is a normal way for a country to keep time, and the “standard” whole hour is just the option most places happened to choose.
Why they exist
Offsets are a political settlement, not a geometric fact. A country whose territory sits awkwardly between two whole-hour meridians has a genuine choice: split into two zones and accept the internal friction, pick one hour and let one end of the country live with the sun in the wrong place, or split the difference. Plenty of places took the third option, and a smaller number went to the quarter hour.
Once chosen, the offset tends to persist, because changing it is disruptive in exactly the way that makes governments reluctant. So the half hours are not transitional oddities working their way toward tidiness. They are stable, and they have been stable for a long time.
What breaks
The damage from rounding is that the result stays plausible. An answer wrong by thirty minutes does not look like a bug; it looks like a meeting time. Nobody double-checks it, which is precisely why it survives to production.
- Integer-hour data types. Any field that stores an offset as a whole number of hours cannot represent Kathmandu at all. The value gets rounded on the way in, and the information is gone.
- Dropdowns built from a list of hours. A picker offering UTC−12 through UTC+14 in single steps silently excludes several hundred million people from choosing their own time zone correctly.
- Reasoning in “hours difference”. “They are 4 hours ahead” is a habit that quietly rounds. Between two quarter-hour zones the gap can be a number of hours plus thirty or forty-five minutes, and the mental shortcut has nowhere to put the remainder.
And they combine with daylight saving
A quarter-hour offset is not necessarily fixed. Pacific/Chatham reports
+13:45 at 15 January 2026 12:00 UTC and +12:45 at 15 July 2026
12:00 UTC — an odd offset that also shifts seasonally, in the southern-hemisphere direction that
inverts the usual northern intuition.
So a zone can be non-integer and variable at once, which defeats both shortcuts simultaneously: you cannot round it, and you cannot cache it. The only correct approach is the one described in a time zone is not an offset — keep the zone name, and ask for the offset at the instant you actually care about.
How the tools here handle it
Every zone on this site comes from a named IANA zone with its offset resolved at the relevant instant, so quarter-hour zones behave like any other. The time zone converter and the meeting planner both show them without special-casing, and the world clock will hold them alongside whole-hour cities. The place data behind the pickers, and what we changed in it, is itemised on where our data comes from.