Asia/Seoul · GMT+09:00
20:06:59
2026년 10월 18일 (일)
24h
Seconds
Seoul
Tennessee
Budapest
San Francisco
New York
London
UTC
public
Add a time zone above to start comparing.
Track the current time in several cities at once and find a meeting slot that is not the middle of the night for someone. Built for distributed teams that keep getting this wrong.
A world clock answers the easy half of a scheduling problem. The hard half is that "3pm" is a different instant for everyone reading it, and the difference is not fixed: the United States moves its clocks on a different date from Europe, most of Asia does not move them at all, and the southern hemisphere moves in the opposite direction. A gap that works for Seoul, Berlin and Chicago in January can be an hour wrong for one of them in March.
The times here come from your browser’s own IANA time zone database, so each city carries its real rules rather than a stored offset — including the years when a country changed its mind. The meeting planner shades each city’s working hours across a 24-hour strip, so the columns where every row is inside working time are the slots that are genuinely fair rather than merely convenient for whoever proposed them.
Half-hour and quarter-hour offsets are the detail that breaks homemade conversions. India is UTC+05:30, Nepal is UTC+05:45, parts of Australia are UTC+09:30, and Iran and Afghanistan sit on half-hours as well. Code that stores an offset as a whole number of hours is wrong for all of them, and a mental conversion that rounds to the nearest hour schedules a meeting thirty minutes off. The offsets here come from the browser time zone database, so a half-hour zone is simply a half-hour zone rather than a special case somebody had to remember.
A time zone is a set of rules, not a number, and the rules change more often than most people expect. Governments move daylight-saving dates, adopt or abandon the practice, and occasionally change their standard offset outright — several have done so in the last decade. This is why storing a fixed offset with a future appointment is a bug in waiting: a meeting saved as UTC+02:00 for next October is wrong if the country has moved its clocks by then, while one saved with its zone name is re-evaluated against the current rules whenever it is read.
The meeting planner exists because the arithmetic is the easy part. Finding an hour that is inside working time for Seoul, Berlin and Chicago at once is a search across three shifting windows, and the honest answer is often that no such hour exists — at which point the question becomes whose morning or evening gets used, which is a decision rather than a calculation. Shading each city working hours across a 24-hour strip makes that visible, so the choice is made deliberately instead of falling on whoever was least awake to object.
Time zone abbreviations are ambiguous and should not be used to record anything. CST is Central Standard Time in North America, China Standard Time and Cuba Standard Time — three different offsets sharing three letters. IST covers India, Ireland and Israel. Even KST is unambiguous only by convention rather than by any registry. A meeting written as "3pm CST" is genuinely undefined, and the fix is to write the offset or the zone name instead. The cities here are labelled with their IANA zone, which is the only identifier that means exactly one thing.
Yes. Times come from your browser’s time zone database, so DST rules per region are applied automatically.
Your selection is kept in your browser, so it is still there when you come back.
Either their device clock is wrong, or their region changed its offset recently and one machine has an outdated time zone database. Compare against UTC to see which.