Time difference between Schaffhausen and Hong Kong

Hong Kong is 6 hours ahead of Schaffhausen.

Europe/Zurich Asia/Hong_Kong already the next day

Local time in both cities

Schaffhausen · Switzerland
18:46
Monday, 21 September 2026
Europe/Zurich · UTC+02:00
Hong Kong · China
00:46
Tuesday, 22 September 2026
Asia/Hong_Kong · UTC+08:00

Hong Kong is 6 hours ahead of Schaffhausen.

already the next day

Time zones

SchaffhausenEurope/Zurich · UTC+02:00
Hong KongAsia/Hong_Kong · UTC+08:00

Schaffhausen is currently on daylight saving time (UTC+02:00). Next change: 2026-10-25 02:00.

Hong Kong 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 Schaffhausen. The two places start and end daylight saving on different dates, so another day can give a different result.

Schaffhausen (source) Hong Kong (target)
00:00 06:00
01:00 07:00
02:00 08:00
03:00 09:00
04:00 10:00
05:00 11:00
06:00 12:00
07:00 13:00
08:00 14:00
09:00 15:00
10:00 16:00
11:00 17:00
12:00 18:00
13:00 19:00
14:00 20:00
15:00 21:00
16:00 22:00
17:00 23:00
18:00 00:00 next day
19:00 01:00 next day
20:00 02:00 next day
21:00 03:00 next day
22:00 04:00 next day
23:00 05:00 next day

FAQ

How many hours apart are Schaffhausen and Hong Kong 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. Schaffhausen uses Europe/Zurich and Hong Kong uses Asia/Hong_Kong; 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 Schaffhausen; the right column is the local time in Hong Kong 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.

Both cities