TimezoneCalculator

Recurring meeting preview

A 09:00 New York standup is 14:00 in London most of the year — and 13:00 for a few weeks. Every occurrence is listed so nothing surprises anyone.

Series

Loading local copy…

What stays fixed?

12 occurrences

Exported as a finite list of 12 separate events, not an endless RRULE, so every occurrence is exactly what you see here.

#America/New_YorkEurope/LondonAsia/KolkataNotesExclude
1Mon 23 Feb 09:00 UTC-05:00Mon 23 Feb 14:00Mon 23 Feb 19:30
2Mon 2 Mar 09:00 UTC-05:00Mon 2 Mar 14:00Mon 2 Mar 19:30
3Mon 9 Mar 09:00 UTC-04:00Mon 9 Mar 13:00 (moved)Mon 9 Mar 18:30 (moved)
4Mon 16 Mar 09:00 UTC-04:00Mon 16 Mar 13:00 (moved)Mon 16 Mar 18:30 (moved)
5Mon 23 Mar 09:00 UTC-04:00Mon 23 Mar 13:00 (moved)Mon 23 Mar 18:30 (moved)
6Mon 30 Mar 09:00 UTC-04:00Mon 30 Mar 14:00Mon 30 Mar 18:30 (moved)
7Mon 6 Apr 09:00 UTC-04:00Mon 6 Apr 14:00Mon 6 Apr 18:30 (moved)
8Mon 13 Apr 09:00 UTC-04:00Mon 13 Apr 14:00Mon 13 Apr 18:30 (moved)
9Mon 20 Apr 09:00 UTC-04:00Mon 20 Apr 14:00Mon 20 Apr 18:30 (moved)
10Mon 27 Apr 09:00 UTC-04:00Mon 27 Apr 14:00Mon 27 Apr 18:30 (moved)
11Mon 4 May 09:00 UTC-04:00Mon 4 May 14:00Mon 4 May 18:30 (moved)
12Mon 11 May 09:00 UTC-04:00Mon 11 May 14:00Mon 11 May 18:30 (moved)

Check against future rule changes

Save the accepted occurrences, then compare later (for example after a browser or OS update changes tz data). Differences are listed for review; nothing is rescheduled automatically.

Check a calendar file

Reads a supported .ics subset on this device: lists events and reports floating times and properties it does not interpret (RRULE, EXDATE, alarms and others). Nothing is fetched or executed.

Wall time or instant?

A recurring meeting has to be anchored to something. Anchored to local clock time, it stays at 09:00 in the organiser’s zone and moves for everyone whose clocks change on different dates. Anchored to an instant, it repeats every 7 × 24 elapsed hours and stays put in UTC, so the organiser’s own clock time shifts by an hour after a DST change. Pick one deliberately; the table marks occurrences whose local time moved.

Exceptions

If an occurrence falls in a skipped hour you can skip it, shift it forward, or shift and flag it. Repeated hours use the first or second occurrence. You can also exclude individual dates; excluded dates are kept as exceptions and restored with one click.

Export and rule changes

The .ics export writes each occurrence as its own event with a stated horizon instead of an open-ended rule, so calendar apps cannot reinterpret it. Save a snapshot of accepted occurrences; after a browser or OS update you can recompute and see exactly which occurrences would move before changing anything.

Questions

Why not export an RRULE?

Calendar apps expand recurrence rules with their own time zone data and exception handling. A finite list of events is exactly what you previewed. Update it by exporting again.

How many occurrences can I preview?

Up to 520, about ten years of weekly meetings.