Weekly meetings across daylight saving time changes

Keep a fixed local time in one city and compare the next four or eight sessions in every participant’s city.

HoraNexo · Reviewed 20 October 2026

City that keeps its local time

Second city

Third city (optional)

Fourth city (optional)

First session · date at origin

Fixed time at origin

Weekly sessions

Duration of each appointment

Each session is seven calendar days later at the same local time in the first city. All sessions must be in 2026. This does not read or change an existing calendar.

Example: Madrid keeps 16:00 while Mexico City moves from 08:00 to 09:00 after 25 October.

Origin date	Madrid	Mexico City	New York
23 October 2026	16:00 · UTC+02:00	08:00 · UTC−06:00	10:00 · UTC−04:00
30 October 2026	16:00 · UTC+01:00	09:00 · UTC−06:00	11:00 · UTC−04:00
6 November 2026	16:00 · UTC+01:00	09:00 · UTC−06:00	10:00 · UTC−05:00
13 November 2026	16:00 · UTC+01:00	09:00 · UTC−06:00	10:00 · UTC−05:00

Highlighted cells change local time or day relative to the origin compared with the first session. Enable JavaScript to adjust dates and download appointments.

One weekly meeting can shift twice

At 16:00 Madrid time on Friday 23 October 2026, Mexico City sees 08:00 and New York sees 10:00. On 30 October, after the European change, they see 09:00 and 11:00. On 6 November, after New York changes its clocks, Mexico City still sees 09:00 while New York returns to 10:00.

Choose which city keeps its time

Put Madrid first if the meeting must always start at 16:00 there. Put New York first if the rule is a fixed New York clock time. Those rules create different instants around daylight saving transitions. This tool creates a proposal; it does not inspect the rule inside an existing invitation.

What the calendar file contains

The ICS download contains four or eight independent events in UTC with the selected duration. It does not create an infinite recurrence, update previous invitations or send messages. Review the import preview before adding it alongside an existing series to avoid duplicate appointments.

Missing and repeated hours

If any weekly session falls in a local hour skipped by a forward clock change, the whole export is blocked until you choose a valid schedule. If the origin hour occurs twice, choose its first or second occurrence. Sessions outside 2026 are also flagged instead of being silently omitted.

For one known start time, use the date-based converter. Find availability with the meeting planner, check a series with the weekly meeting checker, or read our method and sources.

Read the Madrid–New York comparison for the week between the two transitions. Calendar files use iCalendar, RFC 5545.