NOTACAL logo

Time Zone Calculator

Time Zone Converter

Introduction

The Earth is divided into 24 primary longitudinal time zones, each spanning approximately 15 degrees of longitude. All time zones are defined relative to Coordinated Universal Time (UTC), the international time standard maintained by the International Bureau of Weights and Measures (BIPM). Time zone offsets are expressed as differences from UTC — for example, UTC+3 for Moscow, or UTC-5 for New York during standard time.

Some regions use fractional offsets such as UTC+5:30 (India) or UTC+9:30 (central Australia). Additionally, many countries observe Daylight Saving Time (DST), shifting clocks forward by one hour during summer months. DST rules vary by country — some start on different dates, some do not observe it at all, and a few have abandoned it entirely.

This calculator converts any given date and time from one time zone to another. It uses the IANA Time Zone Database to determine correct UTC offsets and automatically adjusts for DST when a specific date is provided. Typical use cases include scheduling international conference calls, planning travel itineraries, and coordinating remote team workflows.

Time zone management has become increasingly critical in the era of global remote work and distributed teams. A company with offices in New York, London, and Tokyo needs to find meeting times that are reasonable for all participants — typically requiring someone to start early or stay late. The global shift to remote work has accelerated this challenge, with teams often spanning 6-12 time zones. Misunderstandings about time zone differences are one of the most common sources of missed meetings and scheduling conflicts in international business, making reliable time zone conversion tools essential infrastructure for modern organizations.

The IANA Time Zone Database, also known as the Olson database, is the global standard for time zone information. Maintained by volunteers and coordinated by the Internet Assigned Numbers Authority (IANA), this database contains the history of time zone changes for every region of the world, including DST start and end dates, offset changes, and even historical variations before standardized time zones were adopted. Governments periodically change their DST rules or time zone boundaries — for example, Russia, Turkey, and Brazil have all made recent changes. Using the IANA database ensures that this calculator reflects the most current information available at the time of its release.

How to Use

  1. Select source time zone — choose from a searchable list of major cities and IANA identifiers.
  2. Enter the date and time — including the date is essential for correct DST application.
  3. Select target time zone — the calculator shows the time difference between the two zones.
  4. View the result — equivalent date and time in the target zone, along with the time difference.
  5. Meeting planner (optional) — shows overlapping business hours across selected zones.

Including the Date is Critical: DST status depends on the specific date, not just the time of day. A meeting scheduled at 10:00 AM in New York on March 10 may be at 15:00 UTC, while the same 10:00 AM meeting on March 20 may be at 14:00 UTC due to DST transitions. Always enter the full date for accurate conversion results. The calculator cannot determine DST correctly from a time-only entry and will assume standard time in that case.

Using the Meeting Planner Feature: Select the time zones of all participants and review the overlapping business hours chart. The ideal meeting time falls within the 9:00 AM to 5:00 PM window for as many participants as possible. For teams spanning more than 5 time zones, finding any overlap may be challenging, and rotating meeting times or alternating between early and late slots can distribute the inconvenience more equitably among team members.

Formulas and Calculations

Step 1: Convert source local time to UTC

t_UTC = t_local - O_source, where O_source is the UTC offset of the source zone.

Step 2: Convert UTC to target local time

t_target = t_UTC + O_target

Daylight Saving Time adjustment

When a date is provided, the offset O equals O_standard if outside DST, or O_standard + 1h if within DST period.

Reference Tables

Major City Time Zone Offsets

CityTime ZoneStandard UTC OffsetObserves DST
London (UK)GMT/BSTUTC+0Yes (+1h summer)
New York (USA)EST/EDTUTC-5Yes (+1h summer)
Los Angeles (USA)PST/PDTUTC-8Yes (+1h summer)
Berlin (Germany)CET/CESTUTC+1Yes (+1h summer)
Moscow (Russia)MSKUTC+3No
Dubai (UAE)GSTUTC+4No
New Delhi (India)ISTUTC+5:30No
Beijing (China)CSTUTC+8No
Tokyo (Japan)JSTUTC+9No
Sydney (Australia)AEST/AEDTUTC+10Yes (+1h summer)
Auckland (NZ)NZST/NZDTUTC+12Yes (+1h summer)

Practical Tips

Double-Check DST Status: During transition periods, the time difference may differ by one hour from what you expect because not all regions switch on the same date.

Use UTC for Scheduling: For recurring international events, schedule in UTC and let each participant calculate their local time.

Account for DST Transition Effects: Be aware that during spring-forward DST transitions (typically March), the day is only 23 hours long, and during fall-back (November), the day is 25 hours long. This affects scheduling in the week before and after transitions when different regions may switch on different dates. When scheduling a recurring meeting across DST transitions, double-check that the scheduled time remains correct for all participants, as the UTC offset difference may change by one hour compared to the previous month.

Use Time Zone Abbreviations with Caution: Time zone abbreviations like EST, PST, and CET are ambiguous. For example, EST can mean Eastern Standard Time in North America (UTC-5) or Eastern Standard Time in Australia (UTC+10). Similarly, IST can mean India Standard Time (UTC+5:30), Israel Standard Time (UTC+2), or Irish Standard Time (UTC+1). This calculator uses IANA time zone identifiers (like America/New_York, Asia/Kolkata) which are unambiguous and always associated with the correct geographic location and its specific DST rules.

Limitations

  • DST rule changes: Governments occasionally change DST rules. May not reflect very recent policy changes.
  • Historical data: Time zone rules before 1970 are incompletely recorded.
  • Fractional offsets: Some less common offsets may require manual verification.
  • Date dependency: Correct result depends on providing a specific date for DST lookup.

Why Time Zone Conversions Are Not Always Precise

Several factors can affect the accuracy of time zone conversions beyond the control of any calculator tool. Political decisions about DST observance can change with little notice — for example, in 2022, Mexico abolished DST for most of the country, and several US states have proposed legislation to adopt permanent DST or permanent standard time. These changes require updates to the IANA database, and the calculator may not reflect very recent or unannounced changes. Always verify critical time conversions against official sources, particularly for dates near DST transition boundaries.

Historical time zone conversions before the standardization of time zones in the late 19th and early 20th centuries are inherently approximate. Before standard time zones were adopted, cities set their clocks based on local solar time, which could vary by several minutes between neighboring towns. Railroads drove the adoption of standard time zones in the 1880s, but many regions did not adopt them until much later. The IANA database includes historical time zone data from 1970 onward with reasonable completeness, but earlier dates may be incomplete or based on interpolation. For genealogical and historical research, specialized tools with more comprehensive historical data may be more appropriate.

Frequently Asked Questions

Why does the time difference between two zones sometimes change?
It changes when one region observes DST and the other does not, or when they switch on different dates.
How do time zones work for China and India?
China uses a single time zone (UTC+8) nationwide despite spanning five geographic zones. India uses UTC+5:30.
What is the International Date Line?
An imaginary line at the 180th meridian where the date changes by one day when crossed.
How do I convert times during DST transition periods?
During spring-forward, the hour from 2:00 AM to 3:00 AM does not exist. During fall-back, the hour from 1:00 AM to 2:00 AM occurs twice.
Which countries have recently changed their time zone or DST policies?
In 2022, Mexico abolished DST nationwide except for border municipalities. In 2023, Egypt reinstated DST after a 10-year hiatus. Ukraine suspended DST in 2024. Jordan, Syria, and Iran have made multiple changes to their DST schedules in recent years. These ongoing changes highlight the importance of using a time zone database that is regularly updated, as well as verifying critical time conversions through official government sources.
How do I handle time zones in software development?
Store all timestamps in UTC and convert to local time only for display. Never store timestamps with local time offsets because DST changes and political decisions can make historical data ambiguous. Use established time zone libraries like Luxon (JavaScript), pytz (Python), or Joda-Time (Java) that are built on the IANA database rather than writing custom time zone logic. Always include the date when recording or processing time zone conversions, as the offset from UTC depends on the date.

References

  • IANA Time Zone Database (tzdata)
  • ISO 8601:2004 — Data elements and interchange formats
  • NIST Time and Frequency Division
  • BIPM — International Bureau of Weights and Measures

Last updated: May 12, 2026