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