Why Some Time Zones Are Offset by 30 or 45 Minutes Instead of a Full Hour

Quick: is India ahead of or behind Pakistan? Trick question in one sense — they’re both roughly in the same longitude band — but India runs on UTC+5:30 while Pakistan runs on UTC+5:00, a 30-minute gap that trips up scheduling tools built around the assumption that every time zone sits on a whole-hour boundary. Whole-hour offsets are the majority, but they’re not universal, and the exceptions have real, specific histories.

Time zones are political, not just geographic

The starting assumption behind time zones — that the world is divided into 24 neat, hour-wide longitudinal slices — was always a simplification. In practice, every country chooses its own civil time, and countries choose based on politics, trade convenience, and national identity as much as pure longitude. A handful of countries have deliberately chosen an offset that isn’t a whole hour, usually to sit at a compromise point between neighboring zones, or to make a symbolic statement of independence from a larger neighbor’s time standard.

India: UTC+5:30

India uses a single time zone nationwide — Indian Standard Time, UTC+5:30 — despite the country spanning a longitude range that would geographically justify two zones. The half-hour offset dates to 1906, when it was set as roughly the midpoint of the country’s longitudinal span, referenced against a meridian passing near Mirzapur, close to the geographic center of the country at the time. India has kept a single unified time zone since independence, partly for administrative simplicity across such a large country, even though it means the sun rises and sets at noticeably different clock times in the far east (near the Myanmar border) versus the far west (near the Pakistan border).

Nepal: UTC+5:45

Nepal’s offset is one of the most distinctive in the world: UTC+5:45, a 45-minute offset that puts it a quarter-hour ahead of neighboring India’s UTC+5:30 — meaning the time difference between two neighboring countries whose capitals sit roughly on the same longitude is a mere fifteen minutes, small enough that it’s easy to forget it exists at all until a meeting starts a quarter-hour off from what someone expected. Nepal adopted this specific offset in 1986, calculated from the longitude of a peak in the Gaurishankar mountain range near Kathmandu. The distinct 15-minute gap from India’s time is widely understood as, at least in part, a deliberate assertion of Nepal’s separate national identity and sovereignty, distinguishing its clock from its much larger neighbor’s.

Iran: UTC+3:30

Iran uses a half-hour offset, UTC+3:30 (Iran Standard Time), also chosen to fall at what was historically calculated as the country’s mean solar longitude rather than rounding to the nearest whole-hour zone shared with neighbors like Iraq (UTC+3) or Pakistan (UTC+5).

Newfoundland: UTC-3:30

Canada is mostly divided into whole-hour zones, but the province of Newfoundland and Labrador (specifically the island of Newfoundland; Labrador itself mostly follows Atlantic time) uses Newfoundland Standard Time, UTC-3:30 — a half hour ahead of the neighboring Atlantic zone (UTC-4) used in the rest of Atlantic Canada. This predates Canadian confederation: Newfoundland was a separate British colony and later dominion until 1949, and it set its own time standard independently, choosing an offset that split the difference between Atlantic Canada’s time and the island’s true solar longitude. After joining Canada, Newfoundland kept its distinctive half-hour offset rather than adopting a neighboring whole-hour zone.

Parts of Australia: UTC+9:30 and UTC+8:45

Central Australia — South Australia and the Northern Territory — uses Australian Central Standard Time, UTC+9:30, splitting the difference between Australian Eastern time (UTC+10) and Australian Western time (UTC+8). This half-hour zone has a similar logic to India’s and Iran’s: a compromise offset chosen for a region whose longitude sits between two more populous zones.

More unusually, a small area of Western Australia around the town of Eucla, near the border with South Australia, unofficially observes an even odder offset — UTC+8:45 — as a local convention that splits the difference between Western Australia’s official UTC+8 and neighboring South Australia’s UTC+9:30. Unlike India’s or Nepal’s offsets, this one isn’t a matter of national law; it’s an informal local practice that has persisted because it’s convenient for a community near the state border, though it isn’t universally observed or legally standardized the way the other examples in this article are.

Myanmar: UTC+6:30

Myanmar (Burma) uses Myanmar Standard Time, UTC+6:30, a half-hour offset that sits between Bangladesh’s UTC+6 and Thailand’s UTC+7. As with several of the other half-hour zones on this list, the offset predates modern borders and has simply persisted through subsequent changes of government, rather than being aligned to either neighbor’s whole-hour standard.

The most extreme case: the Chatham Islands

If Nepal’s 45-minute offset seems unusual, New Zealand’s Chatham Islands go a step further. This small island group, part of New Zealand but roughly 800 kilometers east of the mainland, observes its own time zone: UTC+12:45 standard time, moving to UTC+13:45 during New Zealand’s daylight saving period. That combination — a 45-minute base offset that also observes DST — makes the Chatham Islands one of only a handful of places in the world where the time difference to a neighboring, closely related region (mainland New Zealand, at UTC+12/+13) is a mere 45 minutes rather than a round number, and it’s the most extreme quarter-hour offset in regular civil use anywhere.

How to keep these straight when you’re planning across them

None of these offsets are something most people need to memorize — the point of knowing they exist is simply to avoid the specific mistake of assuming a country’s offset must be a round number of hours from UTC. That assumption is safe for the majority of the world’s roughly 40 distinct time zone offsets in current use, but wrong for a meaningful handful of them, and the countries involved — India and Nepal in particular — are populous enough that the mistake comes up often for anyone doing business across South Asia. If you’re building a scheduling spreadsheet or a manual calculation by hand, it’s worth explicitly double-checking any city in India, Nepal, Iran, Newfoundland, central Australia, or the Chatham Islands against an authoritative source rather than rounding to the nearest hour out of habit.

Why this matters beyond trivia

These offsets are a good stress test for any time zone tool or piece of scheduling software: a system that assumes every offset is a whole number of hours will silently miscalculate the time in India, Nepal, Iran, or Newfoundland. This is one of several reasons relying on the full IANA time zone identifier (such as Asia/Kolkata or Asia/Kathmandu) rather than a hand-typed offset is the safer approach — the identifier encodes the exact offset, including any fractional-hour component, without requiring the person building the tool to remember which countries are exceptions. See our explainer on the IANA time zone database for more on how that identifier system works. If you want to see one of these offsets in action, our time zone converter will show you India or Nepal’s current local time alongside any other city, half-hour and quarter-hour offsets computed automatically, with no extra step required on your part to account for the unusual fraction of an hour involved, whether that’s a clean half hour, a Nepal-style 45 minutes, or the Chatham Islands’ unusual combination of the two.