The time in several places at once

Add the cities you care about and read them together. Each shows its current offset, whether daylight saving is in force, and when that next changes — the three facts a bare clock face leaves out.

A clock face without an offset is half an answer

Knowing it is four in the afternoon somewhere tells you nothing about whether that gap will still be the same next month. Every city here carries its offset and its next clock change, so you can schedule against it rather than just look at it.

The list is the database, not a shortlist

Cities are offered from the full IANA zone list your browser carries — 418 zones in this build — rather than a hand-picked dozen. Zones get renamed, created and merged by governments, and a frozen list quietly offers people places that no longer resolve.

Questions

Where do the time zones come from?

From the IANA time-zone database, through your own browser and our build runtime rather than a list we typed out. This build was made against tzdata 2025b, which names 418 zones. We show that version because a stale time-zone database is a wrong answer that looks completely right.

Why does the difference between two time zones change during the year?

Because countries change their clocks on different dates. The United States moves in March and November, the European Union in the last weekends of March and October, and the southern hemisphere moves the opposite way entirely. For a few weeks each year the usual gap is an hour out, which is when most mis-scheduled calls happen.

Why is Nepal not a whole number of hours?

Because time zones are political rather than geometric. Nepal is UTC+5:45, India UTC+5:30, and the Chatham Islands UTC+12:45. Any converter built on whole hours is wrong for entire countries, which is why nothing here rounds.