Explore · time zones
São Paulo to ACST converter
Brasília Time (São Paulo) → Australian Central Time (Adelaide)
Quick answer
The difference changes with daylight saving time. Adelaide is 13 hours 30 minutes ahead of São Paulo from Jan 1, 2026 to Apr 4, 2026 16:30 UTC (Adelaide on ACDT · UTC+10:30); 12 hours 30 minutes ahead of São Paulo from Apr 4, 2026 16:30 UTC to Oct 3, 2026 16:30 UTC (Adelaide on ACST · UTC+9:30); 13 hours 30 minutes ahead of São Paulo from Oct 3, 2026 16:30 UTC to Dec 31, 2026 (Adelaide on ACDT · UTC+10:30).
- Jan 1, 2026 to Apr 4, 2026 16:30 UTCSão Paulo (UTC−3) → Adelaide (ACDT, UTC+10:30)Adelaide is 13 hours 30 minutes ahead of São Paulo
- Apr 4, 2026 16:30 UTC to Oct 3, 2026 16:30 UTCSão Paulo (UTC−3) → Adelaide (ACST, UTC+9:30)Adelaide is 12 hours 30 minutes ahead of São Paulo
- Oct 3, 2026 16:30 UTC to Dec 31, 2026São Paulo (UTC−3) → Adelaide (ACDT, UTC+10:30)Adelaide is 13 hours 30 minutes ahead of São Paulo
9:00 AM UTC−3 in São Paulo is 10:30 PM ACDT (UTC+10:30) in Adelaide, the same day. Adelaide is 13 h 30 min ahead of São Paulo.
| Format | Result | Copy |
|---|---|---|
| AdelaideACDT · UTC+10:30 · Wednesday, January 14, 2026 · the same day | 10: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768392000 | |
| RFC 2822UTC | Wed, |
Conversions use São Paulo (America/Sao_Paulo) and Adelaide (Australia/Adelaide). Other cities reached through search aliases may have different historical rules.
Current time in São Paulo and Adelaide
Hour by hour: São Paulo (UTC−3) → Adelaide (ACDT, UTC+10:30)
There is no time when both São Paulo and Adelaide are inside 9:00–17:00.
| São Paulo | Adelaide | Day |
|---|---|---|
| 12:00 AM | 1:30 PM | same day |
| 1:00 AM | 2:30 PM | same day |
| 2:00 AM | 3:30 PM | same day |
| 3:00 AM | 4:30 PM | same day |
| 4:00 AM | 5:30 PM | same day |
| 5:00 AM | 6:30 PM | same day |
| 6:00 AM | 7:30 PM | same day |
| 7:00 AM | 8:30 PM | same day |
| 8:00 AM | 9:30 PM | same day |
| 9:00 AM | 10:30 PM | same day |
| 10:00 AM | 11:30 PM | same day |
| 11:00 AM | 12:30 AM | next day |
| 12:00 PM | 1:30 AM | next day |
| 1:00 PM | 2:30 AM | next day |
| 2:00 PM | 3:30 AM | next day |
| 3:00 PM | 4:30 AM | next day |
| 4:00 PM | 5:30 AM | next day |
| 5:00 PM | 6:30 AM | next day |
| 6:00 PM | 7:30 AM | next day |
| 7:00 PM | 8:30 AM | next day |
| 8:00 PM | 9:30 AM | next day |
| 9:00 PM | 10:30 AM | next day |
| 10:00 PM | 11:30 AM | next day |
| 11:00 PM | 12:30 PM | next day |
Hour by hour: São Paulo (UTC−3) → Adelaide (ACST, UTC+9:30)
There is no time when both São Paulo and Adelaide are inside 9:00–17:00.
| São Paulo | Adelaide | Day |
|---|---|---|
| 12:00 AM | 12:30 PM | same day |
| 1:00 AM | 1:30 PM | same day |
| 2:00 AM | 2:30 PM | same day |
| 3:00 AM | 3:30 PM | same day |
| 4:00 AM | 4:30 PM | same day |
| 5:00 AM | 5:30 PM | same day |
| 6:00 AM | 6:30 PM | same day |
| 7:00 AM | 7:30 PM | same day |
| 8:00 AM | 8:30 PM | same day |
| 9:00 AM | 9:30 PM | same day |
| 10:00 AM | 10:30 PM | same day |
| 11:00 AM | 11:30 PM | same day |
| 12:00 PM | 12:30 AM | next day |
| 1:00 PM | 1:30 AM | next day |
| 2:00 PM | 2:30 AM | next day |
| 3:00 PM | 3:30 AM | next day |
| 4:00 PM | 4:30 AM | next day |
| 5:00 PM | 5:30 AM | next day |
| 6:00 PM | 6:30 AM | next day |
| 7:00 PM | 7:30 AM | next day |
| 8:00 PM | 8:30 AM | next day |
| 9:00 PM | 9:30 AM | next day |
| 10:00 PM | 10:30 AM | next day |
| 11:00 PM | 11:30 AM | next day |
Worked examples
| When | São Paulo | Adelaide | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 11:00 AM UTC−3, January 14, 2026 | 12:30 AM ACDT (UTC+10:30), January 15, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 11:00 AM UTC−3, July 15, 2026 | 11:30 PM ACST (UTC+9:30), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 9:00 PM UTC−3, December 31, 2026 | 10:30 AM ACDT (UTC+10:30), 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.
São Paulo — Brasília Time
- IANA identifier
- America/Sao_Paulo
- UTC offset
- UTC−3
- Daylight saving
- Not observed
- On this clock today
- São Paulo, Rio de Janeiro, Brasília
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Sao_Paulo; a listed place's past or future rules may differ.
Brazil has not observed daylight saving time since 2019.
ACST — Australian Central Time
- IANA identifier
- Australia/Adelaide
- Standard time
- ACST · UTC+9:30
- Daylight time
- ACDT · UTC+10:30
- On this clock today
- Adelaide, South Australia
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Australia/Adelaide; 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:30 UTC): clocks go back to UTC+9:30 (ACST)
- Oct 4, 2026, 3:00 AM local (2026-10-03 16:30 UTC): clocks go forward to UTC+10:30 (ACDT)
- Apr 4, 2027, 2:00 AM local (2027-04-03 16:30 UTC): clocks go back to UTC+9:30 (ACST)
- Oct 3, 2027, 3:00 AM local (2027-10-02 16:30 UTC): clocks go forward to UTC+10:30 (ACDT)
UTC+9:30 in winter and UTC+10:30 in summer. Darwin (Northern Territory) uses ACST without daylight saving.
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.