Time Zones, UTC Offsets and Daylight Saving

UTC and offsets

Coordinated Universal Time (UTC) is the global reference point. Local times are expressed as an offset from UTC: for example, Central European Time is UTC+1 and Eastern Standard Time is UTC-5. Not all offsets are whole hours. India observes UTC+5:30, Nepal observes UTC+5:45, and parts of Australia use UTC+9:30. A time zone is a region whose offset rules have been the same over time, which is why one country can contain several zones with the same current offset.

DateUtils works with dates and times across zones through IANA identifiers (handled by the browser’s Intl) and represents offsets explicitly (e.g. UTC+1, UTC-5). The timezone converter converts a local time in one zone to the equivalent local time in another zone using those rules.

Time zone identifiers and abbreviations

The safest way to name a zone is with its IANA identifier, such as Europe/London, America/New_York or Asia/Kolkata. Abbreviations like IST, CST, EST, PDT are ambiguous: IST can mean India Standard Time, Irish Standard Time or Israel Standard Time; CST can mean Central Standard Time (US) or China Standard Time. Because of that ambiguity, DateUtils always shows the UTC offset alongside any abbreviation it displays.

When you look up times or schedule events, prefer the IANA name or an explicit offset to avoid confusion. The world clock shows current times in selected zones with their offsets.

Daylight saving time

Daylight saving time (DST) shifts clocks forward in spring (a local hour is skipped) and back in autumn (a local hour repeats). The effect is that a calendar day can be 23 hours long when clocks move forward or 25 hours long when clocks move back. That matters for duration calculations like hour counts; more on that in the counting days reference.

Transition dates differ by region. In 2025, the United States changed on 9 March and 2 November; the EU/UK changed on 30 March and 26 October. These dates are Sundays. In the southern hemisphere daylight saving runs during the southern summer: Sydney moves forward on the first Sunday in October and back on the first Sunday in April. Many countries, including India, China and Japan, do not use daylight saving at all.

Effects of different transitions

Because transition dates do not align, the offset gap between two cities changes during the year. For example, London and New York are normally 5 hours apart (New York UTC-5, London UTC+0 in winter standard time; or New York UTC-4, London UTC+1 in summer). But during the weeks between US spring forward (9 March 2025) and EU/UK spring forward (30 March 2025), the US is on DST while Europe is not, so the gap becomes 4 hours. The same happens in autumn: Europe moved back on 26 October 2025 and the US on 2 November 2025, so for that week the gap was again 4 hours. A meeting fixed at 15:00 in London moves from 10:00 to 11:00 in New York for those weeks.

When both places observe daylight saving in opposite seasons, the gap takes three values. London and Sydney are 11 hours apart in the northern winter, 9 hours apart in the northern summer, and 10 hours apart when only one of them has changed its clocks: for one week from the last Sunday in March, and for about three weeks in October.

A countdown measures real elapsed time, so one that crosses a clock change is an hour longer or shorter than the clock-face difference suggests. Unix time avoids the problem entirely by counting seconds in UTC, with no zones or daylight saving.

How DateUtils handles skipped and repeated times

When a local time falls in the skipped hour created by spring forward, DateUtils reads it with the offset that was in force before the change. For example, 02:30 on a spring-forward date in New York becomes 03:30 EDT. When a local time is ambiguous because clocks moved back, DateUtils uses the first occurrence and reports the second. Abbreviations are shown only when Intl provides an unambiguous letter code; the UTC offset is always shown.

Practical guidance

To avoid ambiguity, state times with the zone or with an explicit offset, or use UTC. For recurring meetings across zones, check the weeks around March, April, October and November, when one side may have changed its clocks and the other not. If you need to pin a moment in time, use UTC or an IANA zone plus a concrete date.