Time difference between Salisbury North and Tokyo
Tokyo is 30 minutes behind Salisbury North.
Local time in both cities
Salisbury North · Australia
10:34
Tokyo · Japan
10:04
Tokyo is 30 minutes behind Salisbury North.
same day
Time zones
| Salisbury North | Australia/Adelaide · UTC+09:30 |
|---|---|
| Tokyo | Asia/Tokyo · UTC+09:00 |
Salisbury North is currently on standard time (UTC+09:30). Next change: 2026-10-04 03:00.
Tokyo does not observe daylight saving and stays on UTC+09:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-21 local time in Salisbury North. The two places start and end daylight saving on different dates, so another day can give a different result.
| Salisbury North (source) | Tokyo (target) |
|---|---|
| 00:00 | 23:30 prev day |
| 01:00 | 00:30 |
| 02:00 | 01:30 |
| 03:00 | 02:30 |
| 04:00 | 03:30 |
| 05:00 | 04:30 |
| 06:00 | 05:30 |
| 07:00 | 06:30 |
| 08:00 | 07:30 |
| 09:00 | 08:30 |
| 10:00 | 09:30 |
| 11:00 | 10:30 |
| 12:00 | 11:30 |
| 13:00 | 12:30 |
| 14:00 | 13:30 |
| 15:00 | 14:30 |
| 16:00 | 15:30 |
| 17:00 | 16:30 |
| 18:00 | 17:30 |
| 19:00 | 18:30 |
| 20:00 | 19:30 |
| 21:00 | 20:30 |
| 22:00 | 21:30 |
| 23:00 | 22:30 |
Other common differences from Salisbury North
FAQ
- How many hours apart are Salisbury North and Tokyo 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. Salisbury North uses Australia/Adelaide and Tokyo uses Asia/Tokyo; 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 Salisbury North; the right column is the local time in Tokyo 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.