Paste a timestampISO 8601, an email header, a date in words, Unix, FILETIME — or just “08:41 UTC”
Examples:
Date and time
From
—
—
—
To
—
—
—
Difference: —
02
World clock
world clocks, refresh once per second
City
Time
Date
UTC
Moscow
—
—
—
London
—
—
—
New York
—
—
—
Los Angeles
—
—
—
Tokyo
—
—
—
Beijing
—
—
—
Dubai
—
—
—
Singapore
—
—
—
Sydney
—
—
—
Berlin
—
—
—
Istanbul
—
—
—
Antalya
—
—
—
Punta Cana
—
—
—
Krasnoyarsk
—
—
—
Vladivostok
—
—
—
Petropavlovsk-Kamchatsky
—
—
—
03
About timezones
To convert a time between zones, bring it to UTC and add the offset of the place you need: 15:00 in Moscow (UTC+3) is 12:00 UTC and 19:00 in Novosibirsk (UTC+7). The hard part is not the arithmetic but the date. Daylight saving time in Europe and the US changes the gap twice a year, so Moscow and London are two hours apart in summer and three in winter. This tool knows the clock-change rules for the exact date and reads a string as it is — «16 August 2026, 22:02 UTC», an email header or Unix time. Ambiguous abbreviations such as CST and IST are not guessed but honestly left unrecognised.
UTC — reference
Universal
UTC+0 = Greenwich · Coordinated Universal Time
UTC is Coordinated Universal Time, an atomic standard. All time zones are defined as offsets from UTC. Kept within 0.9 seconds of atomic clocks. In programming and aviation it's used as the single reference point.
DST — daylight saving
Not everywhere
US, EU — yes · RU, China, India — no
Daylight Saving Time shifts clocks forward by 1 hour for the summer. In effect in the US, Canada, EU, Australia. Russia abandoned it in 2011, China never used it. Because of DST, winter and summer offsets can differ: EDT (UTC-4) vs EST (UTC-5).
Non-round offsets
IST, NPT
India: +5:30 · Nepal: +5:45 · Iran: +3:30
Not every zone is a whole hour. India (IST) — UTC+5:30, Nepal (NPT) — UTC+5:45, Iran (IRST) — UTC+3:30, parts of Australia — UTC+9:30. The reason is historical: countries chose an offset that matched sun time in the capital.
IANA names
Database
Europe/Moscow · America/New_York
The canonical timezone database is IANA Time Zone Database (tzdata). Format is 'Region/City'. Accounts for historical changes: DST rules, moves, abolitions. Updated several times per year. Used across Unix systems, JavaScript, Python and most databases.
Reading a timestamp
Z, +03:00
22:02Z = 22:02 UTC · 22:02+03:00 = 19:02 UTC
The tail of a timestamp says which zone the time is written in. “Z” means zero — a suffix from aviation and military standards, where the zero zone is called Zulu. “+03:00” means the time shown is **ahead** of UTC by three hours, so getting to UTC means subtracting, not adding. The sign is the most common mistake when reading mail headers and logs, and it is not obvious: the time still looks plausible, it just refers to a different moment.
Time zones of Russia
11 zones
Kaliningrad +2 · Moscow +3 · Kamchatka +12
From Kaliningrad (UTC+2) to Kamchatka (UTC+12) — eleven zones and ten hours of difference inside one country: when the working day ends in Moscow, it is the middle of the night in Vladivostok. Clocks have not been changed since 2014, so the offset of any Russian zone is the same in winter and summer — unlike Europe and the US, where the difference from Moscow shifts twice a year.
Sunlight over Russia
180 days
23 March — 18 September · up to 7 dark hours in winter
For half the year it is daytime somewhere in the country at every moment: the sun is still setting on the Baltic Spit while it is already rising in Chukotka, and beyond the Arctic Circle the polar day is under way. We computed solar elevation at the country's extreme points across a year — there are exactly 180 such days, from 23 March to 18 September. On the remaining 185 the whole of Russia goes dark at once: over seven hours straight in mid-December, and the last place to hold the sun is Ratmanov Island in the Bering Strait.
04
Frequently asked questions
Pick the zones and the page shows the local time in each along with the gap between them, with world clocks for a dozen major cities below. Daylight saving is handled for you: the arithmetic goes through the timezone database built into your browser rather than through fixed offsets.
The page works it out, but the useful part is knowing the gap is not constant. Moscow and New York are seven or eight hours apart depending on the season, because the United States still shifts its clocks and Russia stopped in 2014. Memorising a single number will eventually mislead you.
UTC is the modern standard kept by atomic clocks; GMT is the historical one tied to astronomical observation at Greenwich. Numerically they agree to within a fraction of a second and nobody notices the difference in conversation, but technical documents and standards should say UTC.
Look for the overlap in working hours: the world clocks show several cities at once, so the shared window is visible without arithmetic. Remember the working week itself varies — in parts of the Middle East it starts on Sunday and Friday is the day off, which no offset calculation will tell you.
History and politics rather than astronomy. India runs the whole country on UTC+5:30, Nepal on UTC+5:45, parts of Australia on UTC+9:30. Such offsets were compromises between local solar time and the wish to keep a single clock inside one state, and they simply never got tidied up.
No. Everything is computed in your browser against its own timezone database, and the zones you choose are neither transmitted nor stored. One practical consequence: a browser that has not been updated for a long time may not know the newest daylight saving rule changes.