Canada · calendar time observatoryPinned IANA 2026e · Oct 2026—Feb 2027

Calendar time, explained

Pinned reference & reproducible calendar cases

The reference is a snapshot of IANA tzdb 2026e, reviewed October 15, 2026. It supports eight locations during a five-month window; it is not a complete timezone database.

Expected display at 17:00 UTC, November 4

IANA locationOffsetWall time
America/Vancouver−07:0010:00
America/Edmonton−06:0011:00
America/Inuvik−06:0011:00
America/Winnipeg−05:0012:00
America/Los_Angeles−08:0009:00
America/Toronto−05:0012:00
America/Regina−06:0011:00
America/Whitehorse−07:0010:00

The supported UTC interval is October 1, 2026 inclusive through March 1, 2027 exclusive. Los Angeles falls back at November 1, 09:00 UTC; Toronto at 06:00 UTC. No offset transition occurs in the other six selected zones during this window.

Data comes from the official 2026e release. Its northamerica source was compiled with zic -b fat, read from those compiled files with Python ZoneInfo, and sampled hourly across the window. The JSON records the archive hash and transition boundaries. The browser probe reads the runtime separately with Intl.DateTimeFormat.

Download the pinned reference JSON · Release notes · Timezone data license

Five fictional files, five checks

  1. Old Vancouver rule: 09:00 on November 4 maps to 17:00Z in the file, versus 16:00Z in the reference. Expected difference: +60 minutes.
  2. Fixed UTC−07 rule: the same wall time maps to 16:00Z in both. This confirms that single stored start only.
  3. UTC, all-day and floating: three separate classifications. The UTC event displays 10:00 in Vancouver; the all-day event covers one date; floating time has no inferred zone.
  4. Series and exception: two components, with recurrence flags. The October start matches; the November exception differs. No series expansion is performed.
  5. Los Angeles fallback: 01:30 on November 1 has two reference candidates, 08:30Z and 09:30Z. The checker must not select one silently.

Download for inspection or load these directly in the checker. Do not import them into a production calendar. They use fictional identifiers and are designed to expose particular behaviors.

Evaluator boundaries

Files are capped at 256 KB and 200 event components. The parser accepts at most 20 embedded zones, each with up to six STANDARD/DAYLIGHT observances. Supported timezone rules are bounded yearly rules with a single month and ordinal weekday or month-day, limited transition dates and observance starts from 1900–2027. Unsupported definitions are flagged; they are not replaced with guessed rules.

Event recurrences, tasks, alarms, attachments and invitations are not executed. Calendar URLs are never fetched. The tool does not validate an entire ICS file against every requirement of the standard. It checks stored starts, relevant date types and the timezone mappings described above.

Recognized aliases are Canada/Pacific, Canada/Mountain, Canada/Central, Canada/Eastern, Canada/Saskatchewan, Canada/Yukon and US/Pacific. Other IDs receive an explicit unknown-zone result. The parser uses ical.js 2.2.1; its license is included.