Use the Melbourne row even when Sydney matches
Melbourne and Sydney share the offsets in all four displayed 2026 samples, while retaining different IANA identifiers. If a plan is for a Melbourne participant, choose Australia/Melbourne. Separate availability can still matter when a Sydney participant joins, even though their clock values match.
A dated view of the local clock
| UTC date | UTC offset | Abbreviation | Local date and time |
|---|---|---|---|
| 2026-01-15 | UTC+11:00 | AEDT | Fri, 16 Jan 2026 · 00:00 |
| 2026-07-15 | UTC+10:00 | AEST | Wed, 15 Jul 2026 · 23:00 |
| 2026-10-27 | UTC+11:00 | AEDT | Wed, 28 Oct 2026 · 00:00 |
| 2026-11-03 | UTC+11:00 | AEDT | Wed, 4 Nov 2026 · 00:00 |
A Singapore meeting moves around the Australian change
At 09:00 Singapore in the July sample, Melbourne reads 11:00. On 27 October 2026 it reads 12:00. If the Melbourne team needs an unchanged local start, anchor the recurrence there and check the resulting Singapore time rather than trying to keep both clocks fixed across a change.
Build a plan for this city
Select Melbourne, add the other participants, and enter the actual meeting date. The planner uses Australia/Melbourne; 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.