London and New York in March
On March 16, 2026, 14:00 in Europe/London is 10:00 in America/New_York. On March 30, the same London clock time is 09:00 in New York. The countries change clocks on different dates.
Plan a meeting across cities using the actual calendar date. Enter the source date and time, add participant time zones, and compare local start and end times. Preferred local hours help you find a window that fits the whole meeting.
Preferred windows apply every day, including weekends. An end before the start means an overnight window. End times are exclusive; the whole meeting must fit.
| Person / zone | Start → end | Preferred hours |
|---|---|---|
| London Europe/London | Fri, Oct 23, 2026, 15:00 GMT+1 → Fri, Oct 23, 2026, 16:00 GMT+1 | ✓ Fits |
| New York America/New_York | Fri, Oct 23, 2026, 10:00 GMT-4 → Fri, Oct 23, 2026, 11:00 GMT-4 | ✓ Fits |
5 start times fit everyone on this date in Europe/London. Checked every 30 minutes; meeting length is 60 minutes.
Conversions use your browser’s time-zone data. Rules can change; keep your browser and operating system current. Meetings are not added to any calendar.
Time zones come from the browser’s Intl implementation. No external calendar or availability data is used.
Choose the calendar date, 24-hour start time, source IANA time zone, and meeting length. The date belongs to the source zone.
Add up to eight participants. Set each person’s IANA time zone and preferred start and end times. Use a location such as America/New_York rather than an abbreviation such as EST.
Review local dates and UTC offsets. If the source time occurs twice during a clock change, select an occurrence explicitly.
Choose one of the overlapping start times, if any, and copy the meeting summary. Each suggested start is tested against everyone’s full preferred window.
On March 16, 2026, 14:00 in Europe/London is 10:00 in America/New_York. On March 30, the same London clock time is 09:00 in New York. The countries change clocks on different dates.
November 1, 2026 at 01:30 in America/New_York happens twice: once at UTC−04 and once at UTC−05. The planner asks you to choose which instant you mean.
A late-afternoon meeting in America/Los_Angeles may fall on the following calendar day in Asia/Tokyo. Both local dates appear in the conversion table.
IANA location identifiers represent time-zone histories and rules. Conversions use the browser’s Intl time-zone data for the selected date rather than a fixed city offset. Governments can change these rules, so browser and operating-system updates matter, especially for future events.
When clocks move forward, some local times do not exist. The planner rejects those inputs. When clocks move backward, a clock time can refer to two instants; selecting the displayed offset removes that ambiguity. A meeting length is elapsed minutes, so its local start and end clock readings can appear unusual across a transition.
Suggested start times are spaced every 30 minutes on the chosen date in the source zone. Each elapsed minute of the meeting must fall in every participant’s preferred window. The ending boundary is exclusive. An end earlier than the start defines an overnight window. Preferences apply every day; the planner does not infer weekends, holidays, availability, or calendar conflicts.
A location identifier selects date-aware rules. Short abbreviations can be ambiguous and can describe a fixed standard offset that is wrong during daylight saving.
Try a shorter meeting, wider preferred hours, another source date, or fewer participants. Suggestions use 30-minute start intervals, so a very narrow valid window between those intervals may not appear.
No. Local dates can differ across zones, particularly near the international date line. The conversion table includes the local date for both start and end.
Yes. A preferred window from 22:00 to 06:00 covers late evening and early morning. Equal start and end times are rejected because they could mean either zero hours or all day.
No. Copy the summary into your invitation, then confirm availability with participants. This page does not read or write calendars.