Time difference between Debre Birhan and Hong Kong

Hong Kong is 5 hours ahead of Debre Birhan.

Africa/Addis_Ababa Asia/Hong_Kong already the next day

Local time in both cities

Debre Birhan · Ethiopia
23:07
Monday, 21 September 2026
Africa/Addis_Ababa · UTC+03:00
Hong Kong · China
04:07
Tuesday, 22 September 2026
Asia/Hong_Kong · UTC+08:00

Hong Kong is 5 hours ahead of Debre Birhan.

already the next day

Time zones

Debre BirhanAfrica/Addis_Ababa · UTC+03:00
Hong KongAsia/Hong_Kong · UTC+08:00

Debre Birhan does not observe daylight saving and stays on UTC+03:00 all year.

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

Debre Birhan (source) Hong Kong (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

FAQ

How many hours apart are Debre Birhan 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. Debre Birhan uses Africa/Addis_Ababa 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 Debre Birhan; 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