HesapHanem

Time Zone Meeting Planner

Enter both UTC offsets and your working hours to find the best meeting window.

How it is calculated

Both zones share the same working day, entered as a start and end hour on a 24-hour clock (decimals for half hours: 9.5 is 9:30). Each zone's window is moved to UTC with UTC time = local time − UTC offset. The tool then intersects zone A's window with zone B's, also trying B's window shifted by whole days so that pairs across the date line, such as −8 and +12, are handled. It reports the total overlap in hours, the time difference offset B − offset A, and the overlap window expressed in zone A's local time as decimal hours. If the overlap is split into two pieces, the hours add up but the window shows only the longer piece. Offsets must be between −14 and +14, the start must be 0 or later, the end no later than 24, and the end after the start. UTC offsets are fixed numbers, so the tool does not know about daylight saving.

Worked example

Zone A is New York in winter (UTC−5) and zone B is London (UTC+0), both working 9 to 17. In UTC, A works 14:00 to 22:00 (9 + 5 and 17 + 5) and B works 9:00 to 17:00. They overlap from 14:00 to 17:00, which is 3.0 h. The time difference is 0 − (−5) = 5.0 h. In New York's local time the window is 9.0 to 12.0, that is 9:00 to 12:00.

Try this example →

Common mistakes

  • Entering the offset with the wrong sign. New York in winter is −5, not 5; with +5 the same example shows a difference of -5.0 h and a window of 14.0 to 17.0 instead of 9.0 to 12.0.
  • Typing half-hour offsets as 5:30. Clock notation is rejected; use 5.5 for UTC+5:30, and write working hours the same way (9.5, not 9:30).
  • Using the standard offset all year. Daylight saving changes the offset for part of the year, so enter the offset that applies on the meeting date.
  • Reading the window as zone B's time. The window is given in zone A's local time; add the time difference to get B's time.
  • Giving an overnight shift (17 to 9) as the working day. The end must be later than the start, so an overnight window like 17 to 9 returns no result.

About this calculator

Finding a meeting time that works across time zones means comparing each location's working hours after converting them to a common reference — typically UTC. Given each participant's UTC offset and their shared working-hour window (say, 9:00–17:00 local time), the calculator shifts both ranges onto the same UTC timeline and finds the overlap, if any, between them.

Remote teams, distributed companies, and international project managers use this constantly to schedule calls without forcing one side into an inconvenient early morning or late evening slot. It's especially useful across large offset gaps — like teams split between the US West Coast and Europe or Asia — where the overlapping window can be narrow or nonexistent within standard business hours, making it clear when a compromise, an early or late call, is unavoidable.

Was this helpful?

You can pick up to 3 reactions.

Comments (1)

  • Editorial team

    The overlap window is printed in zone A's local time only. To get zone B's, add the time difference shown. With the default settings, New York at UTC minus 5 and Central Europe at UTC plus 1 share just 2.0 hours, from 9.0 to 11.0 in zone A, which is 15.0 to 17.0 in zone B. The tool assumes the same working hours on both sides; stretching one side early or late is the usual fix. What hours can your teams offer?

Popular calculators

Loan Calculator

Monthly payment, total interest and full amortization schedule.

Percentage Calculator

Percent change, percent of, and ratio calculations.

Discount Calculator

Calculate final price, savings, and discount amount.

BMI Calculator

Body mass index from height and weight (metric or imperial).

Age Calculator

Compute your exact age in years, months and days from a birth date.

Compound Interest Calculator

Calculate the final amount and interest earned with compounding.

All Calculators