Time Zones

Fixed offsets from UTC

The table lists 24 representative cities with standard offsets from Coordinated Universal Time (UTC), stepping from UTC−12 through UTC+11. Each row shows the city’s local clock in 24-hour and 12-hour form based on that fixed offset. Your device’s current UTC time and local zone are shown above the table for reference.

Daylight saving time (DST) is intentionally omitted for the world-city rows. Many regions jump one hour seasonally; a fixed-offset table would be wrong half the year if it pretended to track every DST rule. Labels describe standard-time differences from UTC only.

Why UTC matters

UTC is the modern civil time base that replaced GMT for precise coordination. Aviation, APIs, log files, and distributed systems usually store or display events in UTC, then convert to a local offset for people. When someone says “call me at 15:00 UTC,” every zone can convert without arguing whose “3 pm” they meant.

Worked example

If UTC is 12:00, London on this page (offset 0) shows 12:00, New York (UTC−5 standard) shows 07:00, and Tokyo (UTC+9) shows 21:00. During US daylight saving, real New York clocks may be UTC−4 instead — that seasonal shift is not applied in the city table.

Your local zone row

The “Local zone” readout uses your device clock and system time zone name (for example Australia/Sydney). That value does follow your operating system’s DST rules. Compare it with the UTC now line to see your current offset.

Common mistakes

• Assuming every country in a longitude band shares one offset.
• Using the table for flight schedules that need current DST-aware airports.
• Confusing duration maths with clock time — use Time Duration for lengths of time.

FAQs

Why only 24 cities?

They illustrate each whole-hour offset. Hundreds of civil zones exist; IANA zone databases track them in full.

How do I find days between dates?

Use Date Difference.

Related: Date Difference, Time Duration.