An identical display can still be a distinct location
Hong Kong uses Asia/Hong_Kong, while Shanghai uses Asia/Shanghai. Both show UTC+08:00 in the displayed 2026 examples. Keep the intended city in the plan and let its named rules determine later dates; a current match alone is not a reason to replace the identifier.
A dated view of the local clock
| UTC date | UTC offset | Abbreviation | Local date and time |
|---|---|---|---|
| 2026-01-15 | UTC+08:00 | HKT | Thu, 15 Jan 2026 · 21:00 |
| 2026-07-15 | UTC+08:00 | HKT | Wed, 15 Jul 2026 · 21:00 |
| 2026-10-27 | UTC+08:00 | HKT | Tue, 27 Oct 2026 · 21:00 |
| 2026-11-03 | UTC+08:00 | HKT | Tue, 3 Nov 2026 · 21:00 |
Try a Europe-to-Asia handover before it gets too late
At 16:00 Hong Kong on 27 October, Amsterdam reads 09:00. With illustrative working hours ending at 17:00 in Hong Kong, that leaves one hour for the complete discussion. A 90-minute meeting requires an explicit change to the hours or duration.
Build a plan for this city
Select Hong Kong, add the other participants, and enter the actual meeting date. The planner uses Asia/Hong_Kong; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.