Knowing the time is not the same as knowing whether to call
A row of digital clocks tells you it is 03:40 in Singapore. What you wanted to know was whether anyone is awake, and the number makes you do that conversion yourself every time.
The band puts the hour in context. Night hours are filled dark and their text inverts; the working day is bright; early morning and evening sit between. You read whether someone is available before you have read the number.
A red rule marks the present moment across every row at once, so "now" is a single vertical line rather than something you assemble from several separate readings.
Offsets come from your browser
The times are computed with the IANA time zone database that your browser already carries. That means daylight saving is handled correctly without this site tracking it, including for the places that have changed their rules recently.
One caveat worth stating: British Columbia moved to permanent −07:00 in March 2026 and Alberta to permanent −06:00 that June, and the time zone database currently models both with a placeholder date to work around a limitation elsewhere in the tooling. A browser lookup for those two provinces can therefore be wrong at the moment. Everywhere else in the list is unaffected.
It keeps running
The clock refreshes itself, so a tab left open on a second monitor stays right. Nothing is transmitted and nothing is stored — the page does not know which cities you added and could not tell anyone if it did.
Things people ask
Does it handle daylight saving?
Yes, automatically, because the offsets are computed from your browser's own copy of the IANA time zone database rather than a table stored here.
Why show day and night?
Because it is what the question is usually really about. The number alone makes you do the "is that a reasonable hour" conversion yourself.
Is my list of cities saved?
No. Nothing is stored and nothing is sent anywhere.