UTC to MST

About Coordinated Universal Time

UTC never shifts. It is the reference every other zone is defined against, which is why logs, flight schedules and protocol timestamps use it. GMT is the same clock for every civil purpose, so a query for one is answered by the other.

Cities on this clock: Reykjavik, Accra, Abidjan, Dakar.

Watch out: GMT is also used loosely to mean "UK time", and those are not the same thing for seven months of the year — the United Kingdom moves to BST (UTC+1) while UTC stays put.

About Mountain Time

Mountain Time is UTC−7 as MST and UTC−6 as MDT, on the same transition dates as the rest of the United States. Arizona is the exception worth knowing: almost all of it stays on MST all year, so for the eight months the rest of the zone is on MDT, Phoenix keeps the same clock as Los Angeles rather than Denver.

Cities on this clock: Denver, Salt Lake City, Calgary, Edmonton.

How the difference is worked out

The gap between Coordinated Universal Time and Mountain Time is not one number. The two zones change their clocks on different dates, so for part of the year the difference is 6 hours and for the rest it is something else — the table above lists each stretch of 2026 with the date it starts and which country's clocks moved.

With both zones on their own standard time — daylight saving not in force anywhere — Mountain Time is 7 hours behind Coordinated Universal Time. That figure never changes; everything else on this page follows from it plus whichever clocks have moved.

Every figure here comes from the IANA time zone database via your browser's own Intl engine, using the zone ids UTC and America/Denver. Nothing is looked up on a server and nothing about your visit is recorded.