Time difference between Shanghai and Salisbury North
Salisbury North is 1 hours 30 minutes ahead of Shanghai.
Local time in both cities
Shanghai · China
23:15
Salisbury North · Australia
00:45
Salisbury North is 1 hours 30 minutes ahead of Shanghai.
already the next day
Time zones
| Shanghai | Asia/Shanghai · UTC+08:00 |
|---|---|
| Salisbury North | Australia/Adelaide · UTC+09:30 |
Shanghai does not observe daylight saving and stays on UTC+08:00 all year.
Salisbury North is currently on standard time (UTC+09:30). Next change: 2026-10-04 03:00.
Hour-by-hour conversion
Calculated for 2026-09-21 local time in Shanghai. The two places start and end daylight saving on different dates, so another day can give a different result.
| Shanghai (source) | Salisbury North (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 Shanghai
FAQ
- How many hours apart are Shanghai and Salisbury North 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. Shanghai uses Asia/Shanghai and Salisbury North 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 Shanghai; the right column is the local time in Salisbury North 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.