Time zones look like they should be simple geography — divide the globe into 24 slices — but political decisions, daylight saving, and inconsistent transition dates make real-world time zone math genuinely tricky.
Why Some Offsets Aren't Whole Hours
Time zone boundaries are political choices, not purely geographic ones. India (UTC+5:30) and Nepal (UTC+5:45) are well-known examples of countries that chose an offset better centered on their territory relative to solar noon, or reflecting a historical preference, rather than sticking to the whole-hour grid most zones follow.
Daylight Saving Time and Scheduling
Not every country observes daylight saving time, and among those that do, the transition dates aren't synchronized globally. This means the offset between two specific cities can genuinely change twice a year, and can shift on different calendar dates in each location — a meeting time correct in early March can be off by an hour in early April if only one side has adjusted its clocks so far.
Why UTC Is the Universal Reference
UTC (Coordinated Universal Time) never observes daylight saving and isn't tied to any single country's political decisions, which gives it a stable, unchanging reference point that every other time zone can define itself relative to. Using any one country's local time as the reference instead would drag that country's own daylight saving complications into every other calculation built on top of it.
Finding an Overlapping Meeting Time
Convert each location's normal working hours into a single common reference (UTC works well for this), then look for the window where all locations fall within a reasonable working range. Between zones with a large offset, that overlap can be small or nonexistent — which is exactly why globally distributed teams often end up rotating who takes an inconvenient meeting time.
Converting Right Now
See the same moment across 15+ major world cities, watch a live-updating clock for each zone, and find overlapping business-hour meeting times with our free Time Zone Converter.
FAQ
Why do some time zones have a half-hour or 45-minute offset instead of a whole hour? Time zone boundaries are political decisions, not purely geographic ones, and some countries — India (UTC+5:30) and Nepal (UTC+5:45) are well-known examples — chose an offset that better centers their territory relative to solar noon, or that matches a historical or symbolic preference, rather than sticking to the whole-hour grid most zones use.
Why does daylight saving time make scheduling across time zones so error-prone? Not every country or region observes daylight saving time, and among those that do, the start and end dates aren't synchronized globally. This means the offset between two specific cities can actually change twice a year, and can shift on different calendar dates in each location — a meeting time that's correct in March can be off by an hour in April if only one side has changed its clocks yet.
Why is UTC used as the universal reference instead of any single country's local time? UTC (Coordinated Universal Time) never observes daylight saving and isn't tied to any particular country's political decisions, giving it a single, stable reference point that every other time zone can define itself relative to. Using any one country's local time as the reference would import that country's own daylight saving rules and complications into every other calculation.
How do you find a meeting time that overlaps across several time zones? Convert each location's normal working hours into a single common reference (like UTC), then look for the overlapping window where all of them fall within a reasonable working range. Between time zones with a large offset, that overlap window can be small or nonexistent, which is why teams spread across very different zones often have to rotate who takes an inconvenient meeting time.