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