Find overlapping meeting hours across time zones
Berlin (UTC+2) and New York (UTC−5), both working 9 to 17, overlap only from 14:00 to 15:00 UTC: 16:00 in Berlin, 9:00 in New York. Add each person's offset and office hours to see every shared slot. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Scheduling a call across cities is hard when each person only shares a fixed UTC offset and a local working day. A timezone meeting finder that only converts one clock into another still leaves you to hunt for the intersection by hand. This overlapping meeting hours tool accepts two or more participants, each with a fixed offset from Coordinated Universal Time and a same-day local window such as nine to seventeen, maps every window into UTC at one-minute resolution, and returns the intervals where every participant is simultaneously available. Results include the UTC span plus each participant’s local start and end so you can paste times into a calendar invite without mental arithmetic.
What overlapping meeting hours means with fixed UTC offsets
A fixed UTC offset is a constant number of hours from Coordinated Universal Time: plus two for a winter schedule in much of Central Europe, minus five for Eastern Standard Time, plus five point five for India Standard Time, or plus fourteen for the Line Islands. Unlike a named zone such as America/New_York, a fixed offset does not spring forward or fall back inside this calculator.
The engine converts every local minute of that window into a minute of the UTC day, allowing the mapped interval to wrap past midnight UTC when the offset is large. Availability is stored as a circular mask of one thousand four hundred forty minutes. Contiguous runs of candidate minutes become the overlapping windows reported in the response.
That model answers the search intent behind find overlapping meeting hours timezones: not “what time is it there,” but “when can we all talk while everyone is still inside their published office hours.” Daylight-saving transitions and city-name resolution are deliberately out of scope; supply the fixed offsets that already apply for the date you care about, the same way tickets and status pages print UTC± labels.
Practical tips, limits, and when to use a different tool
Prefer whole or fractional hours that match published civil offsets: five point five for India, five point seven five for Nepal, nine point five for parts of Australia, rather than inventing a second field for offset minutes. Keep every working window on a single local calendar day with end after start; overnight shifts that cross local midnight are not modeled as one row—split them or adjust the day you are planning.
When east and west coast office hours barely touch, expect a short window near one side’s open or close; when Asia and the Americas both use nine-to-five local, you may get no overlap and should either extend windows or pick a different day with different constraints. Pair this capability with a fixed-offset converter when you only need to map one clock, and with a full IANA zone tool when you only have city names or must honor daylight saving automatically.
Cap the team list at forty participants to keep minute-mask work bounded for edge workers.
What you can do with it
Remote team standups across continents
Engineering managers paste each site’s fixed UTC offset and local core hours to list the single daily slot that works for all offices before sending a calendar invite.
Sales calls with customers on published UTC± labels
Account teams that already know both sides as fixed offsets find mutual working hours without opening a full timezone database or guessing daylight-saving rules.
FAQ
What happens if there is no overlap?
Empty intersection is never returned as a successful empty list, and failed validation is not billed.
Does this handle daylight saving time or city names?
No. There is no IANA database and no Date usage. Supply the fixed offsets that already apply for the date you are planning.
How do I enter India or Nepal, which are not on whole hours?
Type the offset as a decimal hour: 5.5 for India Standard Time and 5.75 for Nepal. Parts of Australia use 9.5. You do not need to enter the minutes separately.
Can I plan around a night shift that crosses midnight?
Not as a single entry. Each working window has to start and end on the same local day, with the end after the start. Split an overnight shift into two entries, or plan for a different day.
How many people or cities can I compare at once?
From two up to forty participants in one search. Each brings their own offset and working hours, and a minute only counts as a meeting minute when every participant is available at that moment.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/travel/time-zone-meeting-finder \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"zones":[{"offset":2,"start_hour":9,"end_hour":17,"label":"Berlin"},{"offset":-5,"start_hour":9,"end_hour":17,"label":"New York"}]}'const res = await fetch("https://api.kit.forhosting.com/travel/time-zone-meeting-finder", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"zones": [
{
"offset": 2,
"start_hour": 9,
"end_hour": 17,
"label": "Berlin"
},
{
"offset": -5,
"start_hour": 9,
"end_hour": 17,
"label": "New York"
}
]
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/travel/time-zone-meeting-finder",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"zones": [
{
"offset": 2,
"start_hour": 9,
"end_hour": 17,
"label": "Berlin"
},
{
"offset": -5,
"start_hour": 9,
"end_hour": 17,
"label": "New York"
}
]
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/travel/time-zone-meeting-finder", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"zones":[{"offset":2,"start_hour":9,"end_hour":17,"label":"Berlin"},{"offset":-5,"start_hour":9,"end_hour":17,"label":"New York"}]}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"zones":[{"offset":2,"start_hour":9,"end_hour":17,"label":"Berlin"},{"offset":-5,"start_hour":9,"end_hour":17,"label":"New York"}]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/travel/time-zone-meeting-finder", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"zones": [
{
"offset": 2,
"start_hour": 9,
"end_hour": 17,
"label": "Berlin"
},
{
"offset": -5,
"start_hour": 9,
"end_hour": 17,
"label": "New York"
}
]
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "travel.time_zone_meeting_finder",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
When the windows never meet, the task fails with invalid_input instead of a hollow empty list, matching how planners treat “no slot this day” as a hard outcome.
What overlapping meeting hours means with fixed UTC offsets
Each participant also declares a same-calendar-day local working window as start_hour and end_hour on a twenty-four-hour clock, with end strictly greater than start. Intersection is a bitwise AND across all participants: a UTC minute is a candidate meeting minute only if every mask marks it available.
Input contract, response shape, and error behaviour
Optional label is a short string for the city, team, or person. POST a JSON body with required field zones: an array of at least two and at most forty objects. Each object requires finite numbers offset (within minus fourteen through plus fourteen inclusive), start_hour and end_hour (each from zero through twenty-four, with start strictly less than end and start less than twenty-four). Aliases participants, people, locations, and team are accepted for the array. On success the body includes zone_count; zones echoing each row with offset_label, local clocks, and duration_hours; has_overlap true; overlap_minutes and overlap_hours for the total intersected length; window_count; windows as an ordered list of objects with start_utc, end_utc, duration fields, and local_times mapping the same UTC run into each participant’s local clock; plus message and steps for display and debugging. Failed validation—missing zones, fewer than two rows, non-finite numbers, offsets outside ±14, start not less than end, empty or oversized labels—returns invalid_input and is never billed. Pricing is a flat $0.002 per successful call with unit item.
Practical tips, limits, and when to use a different tool
Use deliberate no-overlap examples in tests so automation asserts invalid_input rather than inventing a slot. Round-trip checks are straightforward: recompute one known pair by hand—Berlin UTC+2 nine-to-seventeen against New York UTC−5 nine-to-seventeen yields a one-hour UTC window fourteen to fifteen, which is sixteen-to-seventeen in Berlin and nine-to-ten in New York—and confirm the API matches. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scheduling scripts cheap when learners deliberately send non-overlapping windows.
Integration use cases
Automation tests for multi-zone schedulers
Services that store fixed offsets generate golden overlap windows and deliberate no-overlap invalid_input cases for continuous integration.
Technical questions
How do I find overlapping meeting hours across time zones?
Send at least two zones, each with a fixed UTC offset and local start_hour/end_hour. The API returns UTC windows and each participant’s local times for every minute when everyone is available.
How many participants can I include?
Between 2 and 40 zone rows per request. Each row needs offset, start_hour, and end_hour; label is optional.
What does the overlapping meeting hours finder cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.