Time difference between Anchorage and Moscow

Moscow is 11 hours ahead of Anchorage.

America/Anchorage Europe/Moscow already the next day

Local time in both cities

Anchorage · United States
14:34
Sunday, 20 September 2026
America/Anchorage · UTC-08:00
Moscow · Russia
01:34
Monday, 21 September 2026
Europe/Moscow · UTC+03:00

Moscow is 11 hours ahead of Anchorage.

already the next day

Time zones

AnchorageAmerica/Anchorage · UTC-08:00
MoscowEurope/Moscow · UTC+03:00

Anchorage is currently on daylight saving time (UTC-08:00). Next change: 2026-11-01 01:00.

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

Hour-by-hour conversion

Calculated for 2026-09-20 local time in Anchorage. The two places start and end daylight saving on different dates, so another day can give a different result.

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

FAQ

How many hours apart are Anchorage and Moscow 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. Anchorage uses America/Anchorage and Moscow uses Europe/Moscow; 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 Anchorage; the right column is the local time in Moscow 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