Time Zones Without Hour Offsets

The textbook model of time zones — 24 wedges, each 15° wide, each one hour offset from the next — does not match reality. About a dozen deviations from the model are in current use, and the /learn/how-many-time-zones support counts them as part of the ~38–40 distinct UTC offsets observed in 2026. This article covers each non-hour zone in detail: where it is, what offset it uses, why the country chose that offset, and what software needs to know to handle it correctly.

Half-hour offsets

UTC+5:30 — India and Sri Lanka

The most-populated non-hour zone: about 1.4 billion people across India, plus another 22 million in Sri Lanka. Adopted by India on 1 September 1947 (shortly after independence on 15 August 1947) as the single national time zone for the country.

The choice was a compromise. India spans about 28° of longitude, from approximately 68°E (Gujarat) to 97°E (Arunachal Pradesh). The two historical commercial capitals — Bombay (now Mumbai) at ~73°E and Calcutta (now Kolkata) at ~88°E — used local mean times of about UTC+4:51 and UTC+5:54 respectively. The independent Indian government chose a single nationwide time zone anchored on the 82.5°E meridian (which runs near Allahabad / Prayagraj), giving the offset of +5:30. The choice is slightly closer to Calcutta than to Bombay; eastern India sees solar noon at about 11:30 IST while western India sees it at about 12:30 IST.

Per the National Physical Laboratory of India, Indian Standard Time is now broadcast by atomic clocks and synchronised to UTC through the Bureau International de l'Heure mechanism. The +5:30 offset has remained unchanged since 1947.

Sri Lanka adopted +5:30 to match India. The country briefly switched to UTC+6:00 from 1996 to 2006 as a power-conservation measure (extending daylight evening hours), then reverted to UTC+5:30 to re-align with India and reduce border confusion.

UTC+3:30 — Iran

Adopted in 1947, anchored on the 52.5°E meridian (which runs near Tehran at 51.4°E). Iran briefly observed DST until 2022, when the government abolished it; the country now stays on UTC+3:30 year-round. About 90 million people.

UTC+4:30 — Afghanistan

Adopted in 1945, anchored on the 67.5°E meridian (which runs near Herat). About 40 million people. Afghanistan does not observe DST.

UTC+6:30 — Myanmar and Cocos Islands

Myanmar (formerly Burma) adopted UTC+6:30 in 1937 anchored on the 97.5°E meridian (near Yangon). The country briefly used UTC+6:00 from 1942 to 1945 during Japanese occupation, then returned to +6:30. About 55 million people.

The Australian Cocos (Keeling) Islands — a small island group in the Indian Ocean about 2,750 km northwest of Perth — also use UTC+6:30, matching their longitude. Population about 600.

UTC−3:30 — Newfoundland and Labrador

The most westerly of the non-hour zones, used by the Canadian province of Newfoundland and Labrador since 1935 (with various predecessor offsets including UTC−3:30:30 in the 1880s). Anchored on the 52.5°W meridian, the offset gives St. John's a civil noon about 30 minutes before solar noon — close to the true solar time of about UTC−3:32 at that location. About 520,000 people.

Newfoundland is the only North American jurisdiction with a non-hour offset; the rest of Canada uses standard hour offsets. The province also observes DST, becoming UTC−2:30 in summer.

UTC+9:30 and UTC+10:30 — Australian Central

The Australian Northern Territory and South Australia use UTC+9:30 year-round (Northern Territory does not observe DST; South Australia does and becomes UTC+10:30 in southern summer). Anchored on the 142.5°E meridian. About 2 million people.

The offset reflects the choice in 1899 when the Australian colonies each adopted standard time: Western Australia (UTC+8), Central Australia (UTC+9:30), Eastern Australia (UTC+10). The Central zone covers about 25° of longitude, more than one hour's span, but the colonies chose a half-hour offset as a compromise between matching solar time and aligning with the eastern states.

UTC+10:30 — Lord Howe Island (with half-hour DST!)

A small Australian island in the Tasman Sea, about 600 km off the New South Wales coast. Lord Howe Island is the only place on Earth with a half-hour DST shift: it uses UTC+10:30 in winter and UTC+11:00 in summer, a 30-minute shift rather than the usual 60-minute one. The unusual arrangement was chosen because the mainland New South Wales DST shift would have given Lord Howe an unreasonable solar-time deviation; the half-hour compromise keeps the island close to true solar time year-round. Population about 400.

UTC−9:30 — Marquesas Islands

The Marquesas archipelago in French Polynesia uses UTC−9:30, a half-hour offset from the standard French Polynesian time of UTC−10 used by Tahiti and the Society Islands. Anchored on the 142.5°W meridian to match the archipelago's longitude. About 9,000 people.

Quarter-hour offsets

The quarter-hour offsets are rarer than the half-hour ones and serve small populations.

UTC+5:45 — Nepal

Adopted in 1986, anchored on the 86.25°E meridian (near Kathmandu at 85.3°E). About 30 million people.

The choice has two motivations. First, identity: Nepal's political relationship with India has often been tense, and adopting an offset 15 minutes different from Indian Standard Time was an explicit assertion of distinct national identity. Second, accuracy: Kathmandu's true solar time is about UTC+5:41, closer to +5:45 than to +5:30. The choice is the only quarter-hour offset in a major national capital.

UTC+12:45 / +13:45 — Chatham Islands

A small island group about 800 km east of New Zealand's South Island. Population about 600. The Chathams use UTC+12:45 in winter and UTC+13:45 in summer, a 60-minute DST shift like New Zealand mainland but offset by 45 minutes from NZST/NZDT.

The 45-minute offset reflects the Chathams' longitude (approximately 176.5°W, equivalent to 183.5°E or about 3.5° east of New Zealand's 172.5°E reference meridian). The offset gives the islands civil time close to their solar time without aligning exactly with NZ mainland time.

UTC+8:45 — Eucla, Western Australia

The most curious of the quarter-hour zones. Eucla is a roadhouse settlement of about 50 people on the South Australia–Western Australia border. Western Australia is on UTC+8; South Australia is on UTC+9:30; the residents of Eucla, between the two, observe an informal UTC+8:45 — splitting the difference between the two official zones.

The offset has no legal status. It is observed by the few businesses and residents at Eucla and by truck drivers passing through; Australian government clocks at the location use Western Australia time. The informal practice has persisted long enough to be documented in the IANA tz database under Australia/Eucla.

Historical non-hour offsets

Several countries have used non-hour offsets in the past and abandoned them, or vice versa. The history is captured in the IANA tz database:

• Venezuela used UTC−4 from 1965 to 2007, switched to UTC−4:30 under the Chávez government (citing solar-time accuracy and schoolchildren's morning daylight), then switched back to UTC−4 in May 2016 under the Maduro government as an energy-saving measure. The 2007–2016 period produced an unusual half-hour zone for an entire country of ~28 million people that no longer exists.
• North Korea switched from UTC+9 to UTC+8:30 in August 2015 (to symbolically distance itself from Japan-imposed time during the 1910–1945 occupation), then switched back to UTC+9 in May 2018 as part of inter-Korean reconciliation talks. The brief 8:30 period was the country's most recent non-hour episode.
• Australian Eastern Standard Time used UTC+10:00 from 1895, with Lord Howe Island and Norfolk Island variously deviating. Norfolk Island used UTC+11:30 until 2015, then switched to UTC+11:00 to match mainland Australia.
• Indian princely states before 1947 unification used a variety of offsets including UTC+5:21 (Bombay Mean Time), UTC+5:53 (Calcutta Mean Time), UTC+4:51 (Madras Mean Time), and several other regional variants. Indian Standard Time at +5:30 replaced all of these.
• Singapore and Malaysia used UTC+7:20 from 1933 to 1942, then UTC+7:30 from 1942 to 1981, before finally adopting UTC+8 in 1981 to align with China. The history is preserved in Asia/Singapore and Asia/Kuala_Lumpur tz database entries.

The IANA database's richness in handling these histories is exactly why software that needs to handle past timestamps correctly must use the database rather than computing UTC offsets by hand.

Software handling

Modern time-zone libraries handle non-hour offsets correctly because they rely on the IANA tz database:

• Python: zoneinfo (standard library, since 3.9); previously pytz.
• Java: java.time.ZoneId; previously Joda-Time.
• JavaScript / Node.js: Intl.DateTimeFormat and the Temporal API (when stable).
• C++: std::chrono::time_zone (since C++20).
• .NET: TimeZoneInfo on .NET Core 3.0+; older versions on Windows have idiosyncrasies but generally work.
• PostgreSQL, MySQL, Oracle: built-in support via the database's integrated tz tables.

Legacy systems are where problems show up:

• POSIX TZ strings (the older TZ=America/New_York mechanism) correctly handle non-hour offsets only when implemented against the tz database. The older simple form TZ=GMT+5:30 does work in POSIX but the sign convention is reversed (POSIX GMT+5:30 is actually UTC−5:30).
• Spreadsheet date arithmetic can lose 30-minute precision when formats round; this is a common source of off-by-30-minute bugs in financial reporting that crosses Indian or Iranian time zones.
• Old hardware clocks in some embedded systems only store whole-hour offsets; this is rare in modern hardware but appears in legacy industrial equipment.
• NTP (Network Time Protocol) provides UTC directly; time-zone application happens at the OS or application layer, which means non-hour offsets are handled by the application's tz library rather than by NTP itself.

The general guidance: always use tz-database-backed library code, never compute UTC offsets by hand. The IANA database is updated multiple times per year as countries adjust their offsets, DST rules, or political boundaries; manual computation is brittle and ages poorly. The /learn/iana-time-zone-database support covers the database in depth.

ISO 8601 representation

ISO 8601 (covered in the /learn/iso-8601-date-time-format support) represents non-hour offsets unambiguously:

2026-05-27T12:00:00+05:30    Indian time
2026-05-27T12:00:00+05:45    Nepal time
2026-05-27T12:00:00+12:45    Chatham time (winter)
2026-05-27T12:00:00-03:30    Newfoundland time
2026-05-27T12:00:00+14:00    Kiribati Line Islands time

The colon-separated minute portion makes the offset explicit. Any ISO-8601-compliant parser handles these correctly. The much older RFC 822 mail-header format (still used in email Date headers, with RFC 5322 updates) uses a different convention — +0530 without the colon — but again with explicit minutes. Avoid older partial formats that omit the minute portion; those break on non-hour offsets.

Sources

• IANA tz database — the authoritative reference for every zone covered here.
• BIPM UTC — UTC definition.
• NIST glossary — time-zone references.
• National Physical Laboratory of India — Indian Standard Time history and broadcast.
• Australian Bureau of Meteorology — Australian time-zone information.
• New Zealand DIA — Chatham Islands time history.

For closely related material, see /learn/how-many-time-zones for the broader count of distinct offsets, the /learn/iana-time-zone-database support for the authoritative software reference, and the /learn/iso-8601-date-time-format support for the canonical timestamp representation.