Half-Hour and 45-Minute Time Zones Explained
Almost every time zone is a whole number of hours from UTC, like UTC+1 or UTC-5. A handful of places sit 30 or 45 minutes off instead, and India, at UTC+05:30, is the one most people run into. That odd half hour is behind plenty of meetings that start 30 minutes late. Here's where these offsets come from, who uses them, and how to convert them without slipping.
Where the extra half hour comes from
Time zones started out tied to the sun. The Earth turns 15 degrees of longitude every hour, so a country picks a reference line (a "meridian") and sets its clocks to the time there. Pick a line that's a multiple of 15 degrees and you get a whole-hour offset; pick one halfway between and you get a half hour.
- India uses about 82.5 degrees east. Divide by 15 and you get 5.5 hours, which is UTC+05:30. That one zone covers a country about 2,900 km wide, so the sun comes up much earlier in the north-east than in the west.
- Iran (about 52.5 degrees east) comes out at 3.5 hours and Afghanistan (about 67.5 degrees east) at 4.5, while Myanmar, at about 97.5 degrees east, lands on 6.5.
- Nepal is the 45-minute case. At UTC+05:45 it runs 15 minutes ahead of India, which keeps Kathmandu's clock closer to its own sun.
Politics played a part too. Some countries simply wanted their own time rather than a neighbour's, and once millions of people, timetables and computer systems run on it, changing it is a huge job.
Who uses a 30 or 45-minute offset
These offsets are worked out live from the time zone database, so if a country changes its rules, the table follows.
| Place | Standard offset | Offset in July | Uses daylight saving? |
|---|---|---|---|
| India | UTC+05:30 | UTC+05:30 | No |
| Sri Lanka | UTC+05:30 | UTC+05:30 | No |
| Nepal | UTC+05:45 | UTC+05:45 | No |
| Afghanistan | UTC+04:30 | UTC+04:30 | No |
| Iran | UTC+03:30 | UTC+03:30 | No (stopped in 2022) |
| Myanmar | UTC+06:30 | UTC+06:30 | No |
| Newfoundland, Canada | UTC-03:30 | UTC-02:30 | Yes |
| South Australia (Adelaide) | UTC+09:30 | UTC+09:30 | Yes |
| Northern Territory, Australia (Darwin) | UTC+09:30 | UTC+09:30 | No |
| Lord Howe Island, Australia | UTC+10:30 | UTC+10:30 | Yes (a 30-minute change) |
| Chatham Islands, New Zealand | UTC+12:45 | UTC+12:45 | Yes |
| Marquesas Islands, French Polynesia | UTC-09:30 | UTC-09:30 | No |
"Standard offset" means the offset without daylight saving, so for Australia and New Zealand it's the July (winter) figure and both columns match. Lord Howe Island is the strange one: its daylight saving shift is only 30 minutes, not a full hour. And a small stretch of Western Australia around Eucla unofficially keeps UTC+08:45.
Why people get these wrong
Mostly it's rounding. Someone remembers "India is UTC+5" and ends up half an hour out, so a 9:00 AM London meeting in January gets written down as 2:00 PM in India when it's really 2:30 PM. Older software doesn't help either; some forms, calendars and spreadsheets only offer whole-hour choices, and people pick whichever is closest.
Daylight saving adds a second layer. The gap between India and a place that changes its clocks moves by an hour twice a year, so the half hour stays put while the hour in front of it shifts.
Converting them properly
- Write the full offset, such as "UTC+05:30", or better still, name the city.
- Move the hours and the minutes together. From UTC, that means adding 5 hours and 30 minutes to get India time.
- Check the date, since the answer can land on the day before or after.
- For anything that matters, let a tool do it. The Time Zone Converter handles half-hour and 45-minute zones for any date, and the Meeting Planner puts the result on a timeline.
One moment, five clocks
Say it's 12:00 noon UTC. London in summer (UTC+01:00) reads 1:00 PM, India (UTC+05:30) reads 5:30 PM, and Nepal (UTC+05:45) reads 5:45 PM, a quarter of an hour ahead of India. Adelaide in January (UTC+10:30) is already at 10:30 PM. India's live time is on the IST time now page, and the time zone FAQ covers more questions about offsets.