Live findings
Research suggests:  clicking things is, on balance, good for you. Sample size: everyone.
Research suggests:  the 3pm slump responds best to one (1) game of Snake.
Research suggests:  reaction time peaks exactly 11 minutes before a meeting you forgot about.
Research suggests:  productivity is, technically, a social construct.
Research suggests:  "just one more game" has never once been one more game.
Research suggests:  looking busy accounts for roughly 90% of looking employed.
Research suggests:  Alt-Tab is the most-used keyboard shortcut in this building.
Research suggests:  a watched progress bar never loads. A played game always does.
Research suggests:  studies confirm: the boss always walks in during your high score.
n = ∞

JustResearching / Tools / Time & Dates

Timezone Overlap Finder

Add locations and see which hours of the working day overlap. For scheduling meetings without making someone miserable.

London
New York
12am
3am
6am
9am
12pm
3pm
6pm
9pm
London12:06 PM
New York7:06 AM
Overlap3h
9am - 5pm working hours
Overlap window
Outside working hours
Current hour (UTC)

3 overlapping hours: 1pm - 4pm UTC.

This tool shows the overlapping 9-to-5 working hours between up to five locations, so you can find a meeting time that does not require anyone to join at 6am.

Remote teams routinely struggle with timezone scheduling because the mental arithmetic of converting between zones is surprisingly easy to get wrong. This tool shows all locations side by side as a 24-hour grid, with working hours highlighted and the true overlap clearly marked.

How we work it out

Working hours are assumed to be 9am to 5pm local time for each location. The grid runs across 24 UTC hours, and each location's working hours are mapped onto it using the current timezone offset including daylight saving time. The overlap row shows only the hours where every selected location is within working hours simultaneously.

Questions

Does this account for daylight saving time?

Yes. Timezone offsets are calculated using the browser's Intl API, which uses the current date and therefore reflects the correct offset including any daylight saving adjustment in effect today.

What if there is no overlap at all?

That is genuinely common with teams spanning more than 10 or 11 hours of difference, such as US West Coast and India. In that case, someone has to flex outside 9-5. Rotating who takes the early or late call is the usual approach.

Can I change the working hours assumption?

Not currently. The tool uses 9am to 5pm as the standard working window. If your team works different hours, use the grid as a reference and shift mentally by the difference.

How do I find overlapping working hours between two cities?

Enter both cities using the location selector and the tool maps each city's 9am to 5pm window onto a shared 24-hour UTC grid. The overlap row shows the hours where both locations are simultaneously within working hours. Works for any city pair: Seattle and Barcelona, London and Bangalore, New York and Amsterdam, or any other cross-timezone combination.