Reference offset
UTC is commonly associated with UTC+0. The live clock shows the current regional offset separately.
UTC is the neutral global reference used behind timestamps, logs, APIs, and cross-border scheduling.
Enable JavaScript for the live regional clock.
Enable JavaScript for the live regional clock.
UTC is the time reference against which numeric offsets are stated. The clock on this page is the UTC reading of your device’s current instant. Its accuracy still depends on your system clock; the page does not independently synchronize to a laboratory or time service.
A timestamp ending in Z is written in UTC. This is useful when logging events from many countries because every event shares a common reference. Convert to a local city for display, keeping the original instant for comparison.
2026-01-15T14:30:00Z and 2026-01-15T09:30:00-05:00 represent the same instant.
UTC has no seasonal daylight-saving adjustment. An office that promises a fixed 14:00 UTC meeting may attend it at different local hours during the year.
Regional rules: IANA Time Zone Database Our calculation methods
Use this page when you need the current UTC time, the role of UTC in software, or a clean point of comparison for other zones.
Each hour of UTC (UTC+0) converted to other common standard-time abbreviations. “+1” and “−1” mark the next or previous calendar day.
| UTC | PST | EST | CET | IST | JST | AEST |
|---|---|---|---|---|---|---|
| 00:00 | 16:00−1 | 19:00−1 | 01:00 | 05:30 | 09:00 | 10:00 |
| 01:00 | 17:00−1 | 20:00−1 | 02:00 | 06:30 | 10:00 | 11:00 |
| 02:00 | 18:00−1 | 21:00−1 | 03:00 | 07:30 | 11:00 | 12:00 |
| 03:00 | 19:00−1 | 22:00−1 | 04:00 | 08:30 | 12:00 | 13:00 |
| 04:00 | 20:00−1 | 23:00−1 | 05:00 | 09:30 | 13:00 | 14:00 |
| 05:00 | 21:00−1 | 00:00 | 06:00 | 10:30 | 14:00 | 15:00 |
| 06:00 | 22:00−1 | 01:00 | 07:00 | 11:30 | 15:00 | 16:00 |
| 07:00 | 23:00−1 | 02:00 | 08:00 | 12:30 | 16:00 | 17:00 |
| 08:00 | 00:00 | 03:00 | 09:00 | 13:30 | 17:00 | 18:00 |
| 09:00 | 01:00 | 04:00 | 10:00 | 14:30 | 18:00 | 19:00 |
| 10:00 | 02:00 | 05:00 | 11:00 | 15:30 | 19:00 | 20:00 |
| 11:00 | 03:00 | 06:00 | 12:00 | 16:30 | 20:00 | 21:00 |
| 12:00 | 04:00 | 07:00 | 13:00 | 17:30 | 21:00 | 22:00 |
| 13:00 | 05:00 | 08:00 | 14:00 | 18:30 | 22:00 | 23:00 |
| 14:00 | 06:00 | 09:00 | 15:00 | 19:30 | 23:00 | 00:00+1 |
| 15:00 | 07:00 | 10:00 | 16:00 | 20:30 | 00:00+1 | 01:00+1 |
| 16:00 | 08:00 | 11:00 | 17:00 | 21:30 | 01:00+1 | 02:00+1 |
| 17:00 | 09:00 | 12:00 | 18:00 | 22:30 | 02:00+1 | 03:00+1 |
| 18:00 | 10:00 | 13:00 | 19:00 | 23:30 | 03:00+1 | 04:00+1 |
| 19:00 | 11:00 | 14:00 | 20:00 | 00:30+1 | 04:00+1 | 05:00+1 |
| 20:00 | 12:00 | 15:00 | 21:00 | 01:30+1 | 05:00+1 | 06:00+1 |
| 21:00 | 13:00 | 16:00 | 22:00 | 02:30+1 | 06:00+1 | 07:00+1 |
| 22:00 | 14:00 | 17:00 | 23:00 | 03:30+1 | 07:00+1 | 08:00+1 |
| 23:00 | 15:00 | 18:00 | 00:00+1 | 04:30+1 | 08:00+1 | 09:00+1 |
UTC is a reference standard. No city uses it as a local clock label, although several places share its offset at certain times of year. Servers, aviation, and many logging systems keep UTC so that records from different regions line up.
For everyday scheduling, yes: both are written as UTC+0 and show the same clock reading. Technically UTC is an atomic time scale kept within 0.9 seconds of the Earth’s rotation by leap seconds, while GMT is a time-zone name. The United Kingdom uses GMT only in winter and BST (UTC+1) in summer, so “GMT” is not a safe label for London time all year.
No. UTC stays at UTC+0 all year. Its difference from zones that do observe daylight saving still changes when those regions move their clocks.
UTC is a reference standard rather than a local clock, so no city keeps it as its civil time label.
These are the abbreviations people most often compare against this reference.