Time difference between Banī Mazār and Shanghai
Shanghai is 5 hours ahead of Banī Mazār.
Local time in both cities
Banī Mazār · Egypt
08:20
Shanghai · China
13:20
Shanghai is 5 hours ahead of Banī Mazār.
same day
Time zones
| Banī Mazār | Africa/Cairo · UTC+03:00 |
|---|---|
| Shanghai | Asia/Shanghai · UTC+08:00 |
Banī Mazār is currently on daylight saving time (UTC+03:00). Next change: 2026-10-29 23:00.
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 Banī Mazār. The two places start and end daylight saving on different dates, so another day can give a different result.
| Banī Mazār (source) | Shanghai (target) |
|---|---|
| 00:00 | 05:00 |
| 01:00 | 06:00 |
| 02:00 | 07:00 |
| 03:00 | 08:00 |
| 04:00 | 09:00 |
| 05:00 | 10:00 |
| 06:00 | 11:00 |
| 07:00 | 12:00 |
| 08:00 | 13:00 |
| 09:00 | 14:00 |
| 10:00 | 15:00 |
| 11:00 | 16:00 |
| 12:00 | 17:00 |
| 13:00 | 18:00 |
| 14:00 | 19:00 |
| 15:00 | 20:00 |
| 16:00 | 21:00 |
| 17:00 | 22:00 |
| 18:00 | 23:00 |
| 19:00 | 00:00 next day |
| 20:00 | 01:00 next day |
| 21:00 | 02:00 next day |
| 22:00 | 03:00 next day |
| 23:00 | 04:00 next day |
Other common differences from Banī Mazār
FAQ
- How many hours apart are Banī Mazār 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. Banī Mazār uses Africa/Cairo 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 Banī Mazār; 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.