Most of the world rounds its clocks to the nearest whole hour from UTC. India doesn't: Indian Standard Time is exactly five and a half hours ahead. It isn't a rounding quirk or a historical accident that stuck — it's a deliberate choice, and this world clock renders it correctly wherever it shows up, including the "vs. you" column when you're comparing your own zone against it.
Open Mumbai and New Delhi on the world clock
India Standard Time is anchored to 82.5°E — the meridian passing near Mirzapur, close to the country's geographic centre. Solar noon on that line falls almost exactly 5 hours 30 minutes ahead of solar noon at Greenwich. Rounding to a flat UTC+5 or UTC+6 would have made the clock read noticeably early or late against the sun for whichever coast was rounded away from; UTC+5:30 was chosen to split that difference rather than accept it on one side.
India stretches from about 68°E to 97°E — roughly two hours of solar time from its western border to its eastern one. Before 1906 the country ran two zones, Bombay Time and Calcutta Time; they were merged into one Indian Standard Time that year, and the country has kept a single zone since independence for the sake of one national timetable — one clock for trains, broadcasting and government offices, rather than a traveller crossing an internal time boundary.
The tradeoff is real and it's visible on this tool's own city list, which carries both ends of the country. Mumbai, in the west, and New Delhi are close enough in longitude that the difference barely registers — but the far northeast, near the Myanmar border, sees the sun rise nearly two hours before it does in the west. A single national clock means the northeast starts its working day in bright daylight while clocks nationwide still read the same 5:30 offset.
| City | Time zone | UTC offset |
|---|---|---|
| Mumbai | Asia/Kolkata | UTC+5:30 |
| New Delhi | Asia/Kolkata | UTC+5:30 |
Both cities share the same IANA zone, Asia/Kolkata, and this world clock reads it straight from your browser's own time zone database — the same source used for every city on the list — so the half-hour offset, and the "vs. you" comparison against it, are exact rather than approximated.
Half-hour and other fractional offsets show up wherever a government has favoured tracking the sun over rounding to a clean number:
| Place | Offset |
|---|---|
| Iran | UTC+3:30 |
| Afghanistan | UTC+4:30 |
| India, Sri Lanka | UTC+5:30 |
| Myanmar | UTC+6:30 |
| Nepal | UTC+5:45 |
| Newfoundland, Canada | UTC-3:30 |
Nepal's UTC+5:45 is one of only two 45-minute offsets used anywhere in the world. None of these are mistakes to round away — a tool that assumes every zone sits on a whole hour will misreport the local time in any of them.
India Standard Time is fixed to 82.5°E longitude, roughly the meridian running through Mirzapur, near the geographic middle of the country. Solar noon there falls almost exactly 5 hours 30 minutes ahead of solar noon at Greenwich, so the government set the clock to UTC+5:30 rather than round to the nearest whole hour, which would have pushed one coast's solar time further from the clock than the other's.
India used two time zones, Bombay Time and Calcutta Time, until they were unified into a single Indian Standard Time in 1906, and the country has kept one zone since independence for administrative simplicity — one national timetable for trains, broadcasting and government offices. The tradeoff is real: solar noon in the far east (near the Myanmar border) arrives roughly two hours earlier than solar noon in the far west (near the Pakistan border), so a single clock reads noon well after sunrise in the east and well before it in the west.
No. Iran and Afghanistan use UTC+3:30 and UTC+4:30. Sri Lanka and Myanmar use UTC+5:30 and UTC+6:30. Nepal uses UTC+5:45, one of only two 45-minute offsets in the world. Newfoundland, Canada runs UTC-3:30. None of these are errors — each was chosen so the local clock tracks solar time more closely than the nearest whole-hour zone would.