Time difference between Komendantsky aerodrom and London

London is 2 hours behind Komendantsky aerodrom.

Europe/Moscow Europe/London still the previous day

Local time in both cities

01:15
Tuesday, 22 September 2026
Europe/Moscow · UTC+03:00
London · United Kingdom
23:15
Monday, 21 September 2026
Europe/London · UTC+01:00

London is 2 hours behind Komendantsky aerodrom.

still the previous day

Time zones

Komendantsky aerodromEurope/Moscow · UTC+03:00
LondonEurope/London · UTC+01:00

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

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

Hour-by-hour conversion

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

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

FAQ

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