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