At 14:00 on 1 October 2026, Moscow and Kiev read the same clock

On that date, both cities sit on UTC+3. Moscow stays there permanently. Kiev got there by advancing to Eastern European Summer Time. The clocks match.

Rewind to 15 January 2026. At 14:00 in Moscow, it was 13:00 in Kiev. Moscow ran one hour ahead. The gap appears every year when Kiev falls back to Eastern European Time (EET, UTC+2) on the last Sunday of October. Moscow, fixed at Moscow Standard Time (MSK, UTC+3), never moves. Russia scrapped daylight saving in 2014. Ukraine still shifts forward on the last Sunday of March and back on the last Sunday of October. That single policy choice creates the split.

Why does Moscow stay fixed while Kiev jumps?

Moscow operates on MSK, a permanent UTC+3 zone. The 2014 amendment to Russia’s “On the Calculation of Time” law abolished seasonal clock changes and locked the country onto standard time. No spring forward, no fall back.

Kiev follows EET (UTC+2) in the colder months and EEST (UTC+3) in the warmer months, aligning with the European Union’s daylight saving calendar. Ukraine’s clocks jump forward at 03:00 on the last Sunday of March and drop back at 04:00 on the last Sunday of October. The offset between the two capitals therefore depends entirely on the calendar.

When does Moscow run one hour ahead of Kiev?

From the last Sunday of October until the last Sunday of March. Kiev sits on EET, UTC+2. Moscow sits on MSK, UTC+3. A 09:00 start in Moscow is 08:00 in Kiev.

From the last Sunday of March until the last Sunday of October, the gap disappears. Kiev moves to EEST, UTC+3. Both cities read the same hour. A 09:00 call connects at 09:00 in both places.

In 2026, the switches land on 28 March and 25 October. On those Sundays, Kiev’s clock jumps or falls by one hour relative to Moscow for that day only. After the change, the new pattern holds until the next transition.

How do I schedule a call between Moscow and Kiev?

Pin the date first.

Late October to late March: add one hour when converting from Kiev to Moscow. A 10:00 meeting in Kiev is 11:00 in Moscow.

Late March to late October: no conversion. A 10:00 meeting in Kiev is 10:00 in Moscow.

The two transition weekends demand extra attention. On 28 March 2026, Kiev leaps from UTC+2 to UTC+3 at 03:00 local time. A 10:00 Kiev meeting that day happens at the same moment as 10:00 Moscow. On 25 October 2026, Kiev retreats from UTC+3 to UTC+2 at 04:00 local time. A 10:00 Kiev meeting that day is 11:00 in Moscow. Recurring meetings that straddle a switch date will shift by an hour overnight. Confirm the exact Sunday before locking the series.

Where do people get the Moscow, Kiev gap wrong?

Assuming a fixed one-hour difference. Wrong. The gap exists only in the winter half of the year. In summer the cities align. Hard-coding a one-hour offset into a calendar invite guarantees errors for six months.

Calling Moscow “Eastern European Time.” Wrong. Moscow uses MSK, which is UTC+3 year-round. EET is UTC+2 in winter and UTC+3 in summer. They coincide only during summer. In winter, Moscow stands one hour ahead of EET.

Saying Ukraine runs on Moscow time. Wrong. Ukraine’s official zone is EET/EEST. Some occupied territories have been forcibly switched to MSK, but Kiev and the rest of government-controlled Ukraine observe Eastern European Time. Check the specific location before dialling.

Believing all of Europe observes DST the same way. Wrong. Russia does not observe DST. Ukraine does. That single divergence creates the entire seasonal gap.

How do I handle the one-hour winter gap between Moscow and Kiev?

For a single call:

  1. Check the date. If it falls between late March and late October, the times are identical.
  2. If it falls between late October and late March, add one hour to Kiev time to get Moscow time, or subtract one hour from Moscow time to get Kiev time.
  3. On the two transition Sundays, confirm the exact moment of the clock change and schedule around it. A 10:00 meeting on the Sunday of the autumn fallback in Kiev will be 11:00 in Moscow, even though the day before it would have been 10:00 in both cities.
  4. Set calendar tools to “Europe/Kiev” and “Europe/Moscow.” Never use a fixed numeric offset like UTC+2 or UTC+3. It will be wrong for half the year.

For teams with desks in both cities, let the calendar system handle the seasonal flip automatically. Travellers crossing the border will see their phone clock update in summer but not in winter. For a recurring weekly call, either schedule it for the summer alignment and accept the one-hour winter shift, or pick a time that works in both seasons by testing against the winter offset first.