---
title: "AEST vs AEDT: what's the difference?"
url: https://meet.barq.dev/glossary/aest-vs-aedt
updated: 2026-11-17
author: "Hammad Ali"
---

# AEST vs AEDT: what's the difference?

> **Short answer:** AEST is Australian Eastern Standard Time at UTC+10:00; AEDT is Australian Eastern Daylight Time at UTC+11:00, one hour ahead of AEST. Sydney's 09:00 on 15 January 2026 is 22:00 UTC on the previous date, while its 09:00 on 15 July is 23:00 UTC on the previous date.


## Why does AEST vs AEDT depend on the Australian city?

The AEST vs AEDT distinction needs a location because Sydney and Brisbane don't have matching offsets on every date. Choose the city first. In the computed January example, Sydney is one hour ahead of Brisbane, but the two cities share an offset in the July example.


| City and named zone | 15 January 2026 | 15 July 2026 |
| --- | --- | --- |
| Sydney, Australia/Sydney | UTC+11:00 | UTC+10:00 |
| Brisbane, Australia/Brisbane | UTC+10:00 | UTC+10:00 |

Method: calculated with Luxon for 09:00 local on each date. Zone rules come from the [IANA time-zone database](https://www.iana.org/time-zones), maintained through its [release history](https://data.iana.org/time-zones/tzdb/NEWS), as of 17 November 2026.


These dated results explain why writing only "Australian eastern time" leaves a scheduling question unanswered. The [meeting abbreviation reference](https://meet.barq.dev/glossary/time-zone-abbreviations) explains how the named zone supplies the missing location.


## How does Australia's summer timing affect overseas calls?

Sydney's January example uses the daylight offset, while its July example uses the standard offset, reversing the seasonal pattern that a northern-hemisphere colleague may expect. Don't copy their winter assumption. Calculate each participant's zone on the appointment date before agreeing a standing local hour.


For Australian locations that observe the checked clock changes, daylight time ends on 5 April 2026 and starts on 4 October 2026. Sources: timeanddate's [first-half 2026 changes](https://www.timeanddate.com/time/dst/2026a.html) and [second-half 2026 changes](https://www.timeanddate.com/time/dst/2026b.html), as of 17 November 2026.


That qualification matters because the transition table isn't permission to apply one seasonal rule to every Australian location. The [daylight-saving definition](https://meet.barq.dev/glossary/daylight-saving-time) describes the difference between a named zone's rules and a fixed UTC offset.


## Which date belongs on an AEDT conversion?

Use the date in the destination zone after conversion, even when it is the day before the host's appointment. Midnight changes the date. A thirty-minute Sydney call at 09:00 on 15 January 2026 runs from 22:00 to 22:30 UTC on 14 January.


Calculate the July version independently: 09:00 to 09:30 in Sydney on 15 July corresponds to 23:00 to 23:30 UTC on 14 July. Both results use Luxon with Australia/Sydney, not a guessed twelve-hour reversal.


The [scheduling glossary's time entries](https://meet.barq.dev/glossary/scheduling-glossary) connect the date, offset and local-clock concepts. Include the duration in your proposal so the recipient can check the full interval instead of only its start. The [Central European seasonal-time definition](https://meet.barq.dev/glossary/cet-vs-cest) explains why a fixed CET start and a city's local-clock start can differ in summer.


## How do AEST and AEDT appear in Barq Meet?

Barq Meet interprets an availability schedule using its named zone, so an Australia/Sydney schedule follows Sydney's dated rules when appointments are offered. We let the guest choose their display zone. A Brisbane guest can therefore read the proposed time on their own clock.


We provide multiple schedules for offers that need different hours. We send a calendar invitation with the confirmation, carrying the selected appointment beyond the booking page and into the guest's calendar.


Inspect the whole date. Calendar integration uses Google Calendar; an Australian host working only from Outlook needs a different calendar connection before conflict checking can cover their existing appointments.


Review [account details for time-zone bookings](https://meet.barq.dev/pricing), then [create a link using your Australian schedule zone](https://meet.barq.dev/app/sign-in).

## Frequently asked questions

### Is Sydney one hour ahead of Brisbane all year?

No. The worked examples put both cities at UTC+10:00 in July 2026, while Sydney is at UTC+11:00 and Brisbane at UTC+10:00 in January. A city pair needs a meeting date before you can state its gap. Check the proposed appointment's date before applying either city's seasonal abbreviation.

### Why does my Australian morning meeting appear yesterday in UTC?

Because subtracting a positive offset can cross midnight. In the January Sydney example, 09:00 local minus eleven hours is 22:00 UTC on the preceding date. Keep that date change when copying the meeting into another system. Include the previous UTC date in the invitation so someone reading the converted hour doesn't arrive a full day late.

### Can I use AEDT for every Australian guest?

No. Name the guest's city or chosen zone before converting an appointment. The Sydney and Brisbane examples already produce different January offsets, so a single eastern-time abbreviation can't describe every Australian participant's intended local time. Ask for the guest's city before converting, since a national label alone won't identify the seasonal rules their location follows.

## Related pages

- [Time zone abbreviations list for scheduling](https://meet.barq.dev/glossary/time-zone-abbreviations)
- [What is daylight saving time (for schedulers)?](https://meet.barq.dev/glossary/daylight-saving-time)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [CET vs CEST: what's the difference?](https://meet.barq.dev/glossary/cet-vs-cest)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
