Explore · time zones
Mexico City to AEST converter
Central Standard Time (Mexico) (Mexico City) → Australian Eastern Time (Sydney)
Quick answer
The difference changes with daylight saving time. Sydney is 17 hours ahead of Mexico City from Jan 1, 2026 to Apr 4, 2026 16:00 UTC (Sydney on AEDT · UTC+11); 16 hours ahead of Mexico City from Apr 4, 2026 16:00 UTC to Oct 3, 2026 16:00 UTC (Sydney on AEST · UTC+10); 17 hours ahead of Mexico City from Oct 3, 2026 16:00 UTC to Dec 31, 2026 (Sydney on AEDT · UTC+11).
- Jan 1, 2026 to Apr 4, 2026 16:00 UTCMexico City (CST, UTC−6) → Sydney (AEDT, UTC+11)Sydney is 17 hours ahead of Mexico City
- Apr 4, 2026 16:00 UTC to Oct 3, 2026 16:00 UTCMexico City (CST, UTC−6) → Sydney (AEST, UTC+10)Sydney is 16 hours ahead of Mexico City
- Oct 3, 2026 16:00 UTC to Dec 31, 2026Mexico City (CST, UTC−6) → Sydney (AEDT, UTC+11)Sydney is 17 hours ahead of Mexico City
9:00 AM CST (UTC−6) in Mexico City is 2:00 AM AEDT (UTC+11) in Sydney, the next day. Sydney is 17 h ahead of Mexico City.
| Format | Result | Copy |
|---|---|---|
| SydneyAEDT · UTC+11 · Thursday, January 15, 2026 · the next day | 2: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768402800 | |
| RFC 2822UTC | Wed, |
Conversions use Mexico City (America/Mexico_City) and Sydney (Australia/Sydney). Other cities reached through search aliases may have different historical rules.
Current time in Mexico City and Sydney
Hour by hour: Mexico City (CST, UTC−6) → Sydney (AEDT, UTC+11)
Both sides are inside 9:00–17:00 from 4:00 PM to 5:00 PM CST (UTC−6) in Mexico City (1 hour).
| Mexico City | Sydney | Day |
|---|---|---|
| 12:00 AM | 5:00 PM | same day |
| 1:00 AM | 6:00 PM | same day |
| 2:00 AM | 7:00 PM | same day |
| 3:00 AM | 8:00 PM | same day |
| 4:00 AM | 9:00 PM | same day |
| 5:00 AM | 10:00 PM | same day |
| 6:00 AM | 11:00 PM | same day |
| 7:00 AM | 12:00 AM | next day |
| 8:00 AM | 1:00 AM | next day |
| 9:00 AM | 2:00 AM | next day |
| 10:00 AM | 3:00 AM | next day |
| 11:00 AM | 4:00 AM | next day |
| 12:00 PM | 5:00 AM | next day |
| 1:00 PM | 6:00 AM | next day |
| 2:00 PM | 7:00 AM | next day |
| 3:00 PM | 8:00 AM | next day |
| 4:00 PM | 9:00 AM | next day |
| 5:00 PM | 10:00 AM | next day |
| 6:00 PM | 11:00 AM | next day |
| 7:00 PM | 12:00 PM | next day |
| 8:00 PM | 1:00 PM | next day |
| 9:00 PM | 2:00 PM | next day |
| 10:00 PM | 3:00 PM | next day |
| 11:00 PM | 4:00 PM | next day |
Hour by hour: Mexico City (CST, UTC−6) → Sydney (AEST, UTC+10)
There is no time when both Mexico City and Sydney are inside 9:00–17:00.
| Mexico City | Sydney | Day |
|---|---|---|
| 12:00 AM | 4:00 PM | same day |
| 1:00 AM | 5:00 PM | same day |
| 2:00 AM | 6:00 PM | same day |
| 3:00 AM | 7:00 PM | same day |
| 4:00 AM | 8:00 PM | same day |
| 5:00 AM | 9:00 PM | same day |
| 6:00 AM | 10:00 PM | same day |
| 7:00 AM | 11:00 PM | same day |
| 8:00 AM | 12:00 AM | next day |
| 9:00 AM | 1:00 AM | next day |
| 10:00 AM | 2:00 AM | next day |
| 11:00 AM | 3:00 AM | next day |
| 12:00 PM | 4:00 AM | next day |
| 1:00 PM | 5:00 AM | next day |
| 2:00 PM | 6:00 AM | next day |
| 3:00 PM | 7:00 AM | next day |
| 4:00 PM | 8:00 AM | next day |
| 5:00 PM | 9:00 AM | next day |
| 6:00 PM | 10:00 AM | next day |
| 7:00 PM | 11:00 AM | next day |
| 8:00 PM | 12:00 PM | next day |
| 9:00 PM | 1:00 PM | next day |
| 10:00 PM | 2:00 PM | next day |
| 11:00 PM | 3:00 PM | next day |
Worked examples
| When | Mexico City | Sydney | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 8:00 AM CST (UTC−6), January 14, 2026 | 1:00 AM AEDT (UTC+11), January 15, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 8:00 AM CST (UTC−6), July 15, 2026 | 12:00 AM AEST (UTC+10), July 16, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 6:00 PM CST (UTC−6), December 31, 2026 | 11:00 AM AEDT (UTC+11), January 1, 2027 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
Mexico City — Central Standard Time (Mexico)
- IANA identifier
- America/Mexico_City
- UTC offset
- CST · UTC−6
- Daylight saving
- Not observed
- On this clock today
- Mexico City, Guadalajara, Monterrey, most of Mexico, Calgary, Edmonton
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Mexico_City; a listed place's past or future rules may differ.
Most of Mexico abolished daylight saving time in October 2022; Mexico City stays on UTC−6 all year. Border municipalities that follow US daylight saving, Baja California and the states on UTC−7 are not on this clock. Alberta (Calgary, Edmonton) has used this UTC−6 clock all year since 1 November 2026; for earlier dates in Alberta use the Mountain Time page.
AEST — Australian Eastern Time
- IANA identifier
- Australia/Sydney
- Standard time
- AEST · UTC+10
- Daylight time
- AEDT · UTC+11
- On this clock today
- Sydney, Melbourne, Canberra, Hobart
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Australia/Sydney; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Apr 5, 2026, 2:00 AM local (2026-04-04 16:00 UTC): clocks go back to UTC+10 (AEST)
- Oct 4, 2026, 3:00 AM local (2026-10-03 16:00 UTC): clocks go forward to UTC+11 (AEDT)
- Apr 4, 2027, 2:00 AM local (2027-04-03 16:00 UTC): clocks go back to UTC+10 (AEST)
- Oct 3, 2027, 3:00 AM local (2027-10-02 16:00 UTC): clocks go forward to UTC+11 (AEDT)
AEST is UTC+10; AEDT (UTC+11) applies from the first Sunday of October to the first Sunday of April. Queensland (Brisbane) stays on AEST all year.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.