World Clock
What time is it for everyone else
Track any number of cities, see who is inside working hours, and read every offset straight from the browser’s own time-zone data.
World Clock
Runs in your browser · nothing uploaded-
London
12:06
Thu 29 Oct · UTC
same time working hours
-
Berlin
13:06
Thu 29 Oct · UTC+1
1h ahead working hours
-
New York
08:06
Thu 29 Oct · UTC−4
4h behind
-
Los Angeles
05:06
Thu 29 Oct · UTC−7
7h behind night
-
Kolkata
17:36
Thu 29 Oct · UTC+5:30
5h30m ahead
-
Tokyo
21:06
Thu 29 Oct · UTC+9
9h ahead night
-
Sydney
23:06
Thu 29 Oct · UTC+11
11h ahead night
7 cities · 2 currently in working hours · offsets read from this browser’s time-zone data
01 — How to use World Clock
02 — Getting good results
03 — Questions
No. Time zone data ships inside your browser, so every calculation happens locally. Nothing about which cities you track leaves the tab, and none of it is stored between visits.
From your browser, which exposes the IANA time zone database it already carries for its own date handling. That means the list is as current as your browser is, and includes every zone it supports rather than a subset someone curated.
Almost always daylight saving. Check the date as well as the time — the offset shown is the one in force at this moment, which may not be the one that zone uses for most of the year.
09:00 to 17:00, Monday to Friday, in each city's own local time. It is a rough convention rather than a claim about any particular workplace, and weekends are excluded entirely.
04 — More about World Clock
Why time zones resist simple arithmetic
A time zone is not an offset. It is a set of rules describing which offset applies on which dates, and those rules change: governments move daylight saving boundaries, adopt or abandon the practice, and occasionally shift zone entirely. The IANA time zone database exists to track this, is updated several times a year, and ships with every operating system and browser. Software that stores "UTC+1" against a city has captured a single moment of a moving target; software that asks the platform what the offset is at a specific instant gets an answer that accounts for whatever rules were in force. This tool does the latter, which is why it handles daylight saving, half-hour offsets and historical changes without having any knowledge of them itself.
The transitions are where the bugs live
Twice a year, most daylight-saving zones produce a local time that either does not exist or happens twice. When clocks spring forward, the hour between 01:00 and 02:00 is skipped entirely — a meeting scheduled at 01:30 that day has no corresponding instant. When they fall back, that hour repeats, so 01:30 is ambiguous and refers to two different moments an hour apart. Any calculation that converts a local time into an instant has to decide what to do about both cases. Reading in the other direction, as this tool does — taking a known instant and asking what each zone displays — avoids the problem entirely, because an instant is unambiguous by definition and every zone has exactly one answer for it.
Coordinating across zones
The practical difficulty in scheduling across regions is rarely the arithmetic; it is that the useful overlap between two working days can be very small, and that it moves. London and Sydney have almost none, and what little exists shifts by two hours across the year as the two hemispheres change clocks on opposite schedules. Seeing the whole board at once, with the local date alongside the local time, makes the shape of that constraint visible: which cities are awake now, which are already into tomorrow, and where the hours that work for everyone actually fall.
61 more tools
where this came from.
Same shell, same shortcuts, same promise: nothing leaves your browser.