World Clock — Current Time Worldwide

How to schedule across time zones without the guesswork

Most missed meetings are not a calendar problem, they are a math problem. Pick one reference city and convert everything to it before you send an invite. If your team spans New York and London, that gap is five hours for most of the year but only four for two weeks in March and one week in late October, because the United States and the United Kingdom change their clocks on different dates. The clocks above already account for that, so read them rather than adding hours in your head.

The overlap window trick

For a distributed team, write down each person's working hours in their own local time, then find the block where every row overlaps. New York and London usually share 9:00 to 12:00 New York time. New York and Tokyo barely overlap at all, so the fair answer is to rotate who takes the awkward call rather than always making the same region stay late. Sydney and Los Angeles are effectively a full day apart, which is why asynchronous handoffs beat live meetings on that pairing.

Write times so nobody has to interpret them

Always include the zone abbreviation and the date: "Tuesday 14:00 GMT" is unambiguous, while "2pm" is not. Using 24-hour notation removes the AM and PM mistake entirely, which is exactly why hospitals, airlines and the military use it. If your team is new to it, the military time chart converts every hour in one glance, and what are time zones explains why the grid exists in the first place.

Once the call starts, keep it on schedule with the countdown timer for each agenda item, or the multi timer when several breakout groups are running at the same time.