A distinct rule behind a familiar UTC+08:00 display
Asia/Singapore has UTC+08:00 on the displayed dates. Asia/Shanghai and Asia/Hong_Kong share those sampled offsets, yet remain separate identifiers. Matching output for a few dates is not a reason to rewrite a saved participant’s zone.
Offsets in the bundled rules
| Date | UTC offset | Display abbreviation |
|---|---|---|
| 2026-01-15 | UTC+08:00 | +08 |
| 2026-07-15 | UTC+08:00 | +08 |
| 2026-10-27 | UTC+08:00 | +08 |
| 2026-11-03 | UTC+08:00 | +08 |
Resolve the wall time before exporting
21:00 in this zone on 27 October 2026 is 13:00 UTC and midnight on 28 October in Australia/Sydney. Even an offset-stable source zone can produce a date change at the destination.
Use this identifier in a plan
Find Asia/Singapore in the zone directory or choose Singapore from the city directory. Add the other meeting locations, enter their availability, and check the complete duration. The supported planning years are 2026–2035; future political rule changes may require a new data version.
A calendar export uses the resolved UTC start and end times. The zone remains part of the planning context, while the exported instant stays unambiguous when another calendar displays it in its own time zone.