Convert UTC to Moscow time: when it is 12:00 UTC it is 15:00 in Moscow in January and 15:00 in July. Moscow is on UTC+03:00 in standard time, all year. The full 24-hour conversion table is below, and the UTC converter does the conversion live for any date and time.

Try the tool: UTC Converter — convert any UTC time to Moscow time, or Moscow time back to UTC, with the offset shown.

Current UTC time and the time in Moscow

UTC is the world's reference time — it never observes daylight saving, and every other time zone is defined as an offset from it. The table shows four reference instants and what time they are in Moscow, in January and in July.

UTC Moscow in January Moscow in July
00:00 03:00 03:00
06:00 09:00 09:00
12:00 15:00 15:00
18:00 21:00 21:00

If the January and July columns are the same, Moscow's offset does not change — it does not observe daylight saving. If they differ by an hour, that hour is daylight saving, and the Moscow DST 2026 page gives the exact dates. The world clock shows the current time in Moscow live, and the time in Moscow page explains the city's time zone in full.

Moscow's offset from UTC

Moscow stays on UTC+03:00 all year — it does not observe daylight saving, so its offset from UTC never changes.

Period Offset In effect
All year UTC+03:00 The offset never changes
Right now (11 November 2026) UTC+03:00 The offset never changes

The offset is the only number you need. To convert UTC to Moscow time, add the offset. To convert Moscow time to UTC, subtract it. The offset to use is the one in effect on the date you are converting — not today's offset, and not the offset you remember from last summer. The converter on this page's tool does that for you: enter the UTC time and the date, and it looks up the offset from the IANA database for that date.

UTC to Moscow — full conversion table

Every hour of the day, converted from UTC to Moscow local time. The January column uses the winter offset (UTC+03:00); the July column uses the summer offset (UTC+03:00). The two columns are identical, because Moscow does not observe daylight saving.

UTC Moscow (January) Moscow (July)
00:00 03:00 03:00
01:00 04:00 04:00
02:00 05:00 05:00
03:00 06:00 06:00
04:00 07:00 07:00
05:00 08:00 08:00
06:00 09:00 09:00
07:00 10:00 10:00
08:00 11:00 11:00
09:00 12:00 12:00
10:00 13:00 13:00
11:00 14:00 14:00
12:00 15:00 15:00
13:00 16:00 16:00
14:00 17:00 17:00
15:00 18:00 18:00
16:00 19:00 19:00
17:00 20:00 20:00
18:00 21:00 21:00
19:00 22:00 22:00
20:00 23:00 23:00
21:00 00:00 00:00
22:00 01:00 01:00
23:00 02:00 02:00

Use the table by finding the UTC hour in the first column and reading across. Note the date change: a UTC time late in the evening is the next day in Moscow when the offset is positive and large — 22:00 UTC is 01:00 the next day in Moscow in January — and a UTC time early in the morning is the previous day in Moscow when the offset is negative. The date matters as much as the time: a meeting at 02:00 UTC on Tuesday is a Monday evening meeting in the Americas.

When the offset changes

The offset never changes. Moscow does not observe daylight saving, so the table above is right on every day of the year. Russia abolished daylight saving in 2014 and stays on permanent 'winter time' — Moscow is on UTC+3 all year. Russia had tried permanent summer time in 2011 and dropped it after complaints about dark winter mornings. The only thing that changes is the time in the place you are converting from — if that place observes daylight saving, its offset from UTC will move, and the difference between it and Moscow will move with it.

Moscow time to UTC

The reverse conversion — Moscow local time back to UTC — is the same table read backwards. Six examples, for January:

Moscow local UTC (January) UTC (July)
00:00 21:00 21:00
06:00 03:00 03:00
09:00 06:00 06:00
12:00 09:00 09:00
15:00 12:00 12:00
21:00 18:00 18:00

The reverse table is the one to use when you are telling someone in another time zone when something happens in Moscow. A flight that departs Moscow at 09:00 local time departs at 06:00 UTC in January — and that UTC time is what the airline's systems, the air traffic controllers and the arrival airport all use. The flight time calculator works out the arrival time as well, including the date change.

Scheduling with UTC-based teams

Teams that work in UTC — software teams, aviation, shipping, scientific collaborations — schedule in UTC precisely because it never changes. If your team works in UTC, the time in Moscow is UTC plus UTC+03:00 in January and UTC plus UTC+03:00 in July, and the only question is which of those applies on the meeting date. Put the UTC time in the invitation as well as the local time, and nobody has to convert.

The practical working hours for a UTC-based team and Moscow are: 09:00–17:00 in Moscow is 06:00–14:00 UTC in January and 06:00–14:00 UTC in July. A meeting at 14:00 UTC is 17:00 in Moscow in January — inside the working day — and 17:00 in July. A meeting at 08:00 UTC is 11:00 in Moscow in January, which is before the working day starts. The meeting planner finds the overlap for any two cities, and the meeting time finder finds it for a whole team.

Frequently asked questions

What time is it in Moscow when it is 12:00 UTC?

It is 15:00 in January and 15:00 in July. The answer is the same all year, because Moscow does not observe daylight saving.

What is Moscow's offset from UTC?

Moscow is on UTC+03:00 in standard time, all year.

How do I convert UTC to Moscow time?

Add Moscow's offset to the UTC time: UTC+03:00 in January, UTC+03:00 in July. The UTC converter does it for any date, and the table above covers every hour.

Does Moscow observe daylight saving time?

No. Moscow does not observe daylight saving, so its offset of UTC+03:00 never changes.

What date is it in Moscow when it is 22:00 UTC?

It is the next day: 22:00 UTC is 01:00 the following day in Moscow in January (and 01:00 in July). The date change is the part of UTC conversion people most often forget.

What time zone is Moscow in?

Moscow is in the IANA time zone Europe/Moscow, in Russia. See the time in Moscow page for the full explanation.

Sources

  • IANA Time Zone Database, via Node.js Intl (Intl.DateTimeFormat with timeZone) — offsets, daylight saving dates and local times in this article were worked out from the IANA database, not typed from memory.
  • TimeFlow's own time-zone data (data/cities.ts, data/dst.ts), computed from the IANA database.
  • TimeFlow's UTC converter and world clock — the live tools behind the numbers on this page.
  • Time-zone and daylight saving rules are set by governments and can change. For flights, deadlines and meetings that cannot move, confirm the time with an official source.