Time difference between Taipei and Mount Barker
Mount Barker is 1 hours 30 minutes ahead of Taipei.
Local time in both cities
Taipei · China
06:23
ChinaMount Barker · Australia
07:53
AustraliaMount Barker is 1 hours 30 minutes ahead of Taipei.
same day
Time zones
| Taipei | Asia/Taipei · UTC+08:00 |
|---|---|
| Mount Barker | Australia/Adelaide · UTC+09:30 |
Taipei does not observe daylight saving and stays on UTC+08:00 all year.
Mount Barker is currently on standard time (UTC+09:30). Next change: 2026-10-04 03:00.
Hour-by-hour conversion
Calculated for 2026-09-22 local time in Taipei. The two places start and end daylight saving on different dates, so another day can give a different result.
| Taipei (source) | Mount Barker (target) |
|---|---|
| 00:00 | 01:30 |
| 01:00 | 02:30 |
| 02:00 | 03:30 |
| 03:00 | 04:30 |
| 04:00 | 05:30 |
| 05:00 | 06:30 |
| 06:00 | 07:30 |
| 07:00 | 08:30 |
| 08:00 | 09:30 |
| 09:00 | 10:30 |
| 10:00 | 11:30 |
| 11:00 | 12:30 |
| 12:00 | 13:30 |
| 13:00 | 14:30 |
| 14:00 | 15:30 |
| 15:00 | 16:30 |
| 16:00 | 17:30 |
| 17:00 | 18:30 |
| 18:00 | 19:30 |
| 19:00 | 20:30 |
| 20:00 | 21:30 |
| 21:00 | 22:30 |
| 22:00 | 23:30 |
| 23:00 | 00:30 next day |
Other common differences from Taipei
FAQ
- How many hours apart are Taipei and Mount Barker right now?
- The answer at the top of the page is calculated for the current moment and states which side is ahead. The gap changes during the year, because the two places usually start and end daylight saving on different dates.
- Is this difference the same all year?
- Not necessarily. Taipei uses Asia/Taipei and Mount Barker uses Australia/Adelaide; if either observes daylight saving, the gap shifts during the year. Use “Convert a specific date and time” below to calculate it for a given day.
- How do I read the conversion table?
- The left column lists each whole hour in Taipei; the right column is the local time in Mount Barker at that same instant, with date rollovers marked. On the day clocks jump forward, some hours do not exist locally — the table says so instead of showing a plausible but wrong value.