Time difference between Shanghai and North Lakhimpur
North Lakhimpur is 2 hours 30 minutes behind Shanghai.
Local time in both cities
Shanghai · China
00:37
ChinaNorth Lakhimpur · India
22:07
IndiaNorth Lakhimpur is 2 hours 30 minutes behind Shanghai.
still the previous day
Time zones
| Shanghai | Asia/Shanghai · UTC+08:00 |
|---|---|
| North Lakhimpur | Asia/Kolkata · UTC+05:30 |
Shanghai does not observe daylight saving and stays on UTC+08:00 all year.
North Lakhimpur does not observe daylight saving and stays on UTC+05:30 all year.
Hour-by-hour conversion
Calculated for 2026-09-22 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) | North Lakhimpur (target) |
|---|---|
| 00:00 | 21:30 prev day |
| 01:00 | 22:30 prev day |
| 02:00 | 23:30 prev day |
| 03:00 | 00:30 |
| 04:00 | 01:30 |
| 05:00 | 02:30 |
| 06:00 | 03:30 |
| 07:00 | 04:30 |
| 08:00 | 05:30 |
| 09:00 | 06:30 |
| 10:00 | 07:30 |
| 11:00 | 08:30 |
| 12:00 | 09:30 |
| 13:00 | 10:30 |
| 14:00 | 11:30 |
| 15:00 | 12:30 |
| 16:00 | 13:30 |
| 17:00 | 14:30 |
| 18:00 | 15:30 |
| 19:00 | 16:30 |
| 20:00 | 17:30 |
| 21:00 | 18:30 |
| 22:00 | 19:30 |
| 23:00 | 20:30 |
Other common differences from Shanghai
FAQ
- How many hours apart are Shanghai and North Lakhimpur 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 North Lakhimpur uses Asia/Kolkata; 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 North Lakhimpur 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.