Quick answer

Convert both local date-times to UTC using their offsets, subtract there, and present the result with both offsets visible.

Local time is a label

A local date-time is a rendering of an instant, not the instant itself. "9:00 on 16 August" describes different moments in Chicago and in Mumbai, separated by ten and a half hours. Subtracting the two labels as if they were numbers produces a result with no physical meaning.

The reliable procedure has three steps: convert each local time to UTC by subtracting its offset, subtract the UTC values, then present the answer. The intermediate UTC values are worth showing, because they are where a wrong offset becomes visible.

Use this guide with the right tool: Open the Time Zone Date Difference Calculator for the real elapsed interval between two local date-times in different UTC offsets. If the question shifts, compare it with the Date Difference Calculator or the Weekday Calculator.

Two wall clocks side by side showing different times
Two clocks can disagree about the date even when they agree about the time — offsets are not time zones.

Offsets are not time zones

An offset is a number of hours from UTC at a particular moment. A time zone is a rule that says which offset applies on which dates. Chicago is UTC−6 in winter and UTC−5 in summer; the zone is constant, the offset is not.

This calculator works with fixed offsets, which is exactly right when you know the offset that applied — for example, when reading it from a timestamp in a log or an email header. It is not right for a future date in a region that observes daylight saving, because the applicable offset may not be the one you expect. For scheduling ahead, work from zone identifiers and a maintained time-zone database rather than from a fixed number.

Half-hour and quarter-hour offsets

Not every offset is a whole number of hours. India is UTC+5:30, Nepal is UTC+5:45, parts of Australia are UTC+9:30, and the Chatham Islands are UTC+12:45. Systems that store offsets as integers silently corrupt these.

If you are entering an offset manually, enter the fractional value — 5.5 rather than 5 — and check the result against a known reference point. A thirty-minute error is small enough to survive review and large enough to move an event across a date boundary.

The date can differ even when the time does not

Because offsets span more than a day in total range, two people can be on different calendar dates at the same instant. A meeting at 22:00 UTC on 16 August is late Sunday evening in London and early Monday morning in Tokyo.

When you communicate a time across zones, give the date in each recipient's local terms, or give the UTC instant and let their calendar render it. Sending only a local time and a zone abbreviation is how people arrive a day late — and abbreviations are ambiguous in their own right, since several are used for more than one zone.

Worked example

A meeting starting at 09:00 local time at UTC−5 and ending at 09:00 local time at UTC+5:30 has not lasted zero hours. In UTC the start is 14:00 and the end is 03:30, so the end precedes the start by ten and a half hours — the offset difference exactly.

A 09:00 start at UTC-5 is 14:00 in UTC, while a 09:00 end at UTC+5:30 is 03:30, so the end precedes the start by ten and a half hours. Convert your own local times to UTC first and compare them there.

Arriving before you leave

The worked example subtracts two labels for the same time of day. A complete journey, worked by the three-step procedure from earlier in this guide, shows the same effect at full size. The offsets are the ones in force in August: Sydney at UTC+10, Los Angeles at UTC-7.

A flight leaves Sydney at 09:00 on Monday 17 August 2026 and arrives in Los Angeles at 06:30 on Monday 17 August 2026. Converted, the departure is 23:00 UTC on Sunday 16 August and the arrival is 13:30 UTC on Monday 17 August, so the flight lasts fourteen and a half hours. The labels alone tell a different story: 06:30 from 09:00 is two and a half hours backwards, an arrival before the departure on the same named day. Both labels even carry the same weekday, which is what makes the naive reading feel safe. The seventeen hours of offset difference between the two cities are invisible in it.

The return journey breaks the date instead. Leaving Los Angeles at 22:00 on Friday 21 August 2026 — 05:00 UTC on Saturday 22 August — and arriving in Sydney at 06:00 on Sunday 23 August, which is 20:00 UTC on the Saturday, takes fifteen hours. The traveller's local dates jump from Friday straight to Sunday. Saturday exists throughout the flight in UTC, and the aircraft crosses it, but it is never the local date at either end of the journey while the traveller is on the ground at that end. A diary kept in local dates has a day missing from it, and no day was skipped in elapsed time.

The limiting case sits at the edges of the offset range. Kiritimati observes UTC+14 and Honolulu UTC-10, twenty-four hours of offset between them, so 09:00 on Tuesday 18 August 2026 in Kiritimati is the same instant as 09:00 on Monday 17 August in Honolulu: the identical clock reading, on dates a full day apart. Any calculation that treats those two labels as simultaneous events on the same day is wrong by exactly twenty-four hours, and wrong in a way no rounding will reveal, because every individual number in it looks reasonable.

None of these cases involves exotic arithmetic. Each one is the three steps from earlier in this guide — convert both labels to UTC, subtract there, present the result with the offsets visible — applied to dates rather than to a single pair of times. The flights feel paradoxical only when the labels are compared directly, which is the one operation this guide has been arguing against from its first section.

Common mistakes to avoid

  • Subtracting local times directly. Convert both to UTC first. Direct subtraction of labels is not an interval.
  • Storing an offset as a whole number. Several zones use half- and quarter-hour offsets. Use a fractional value.
  • Using a fixed offset for a future date. Daylight saving changes the offset. For scheduling ahead, use a zone identifier and a current time-zone database.

Use the right calculator

The Time Zone Date Difference Calculator finds the elapsed interval between local date-times in different offsets, the Date Difference Calculator gives calendar differences, and the Weekday Calculator names the weekday of any date.

Time Zone Date Difference Calculator
Date LabTime Zone Date Difference Calculatorthe real elapsed interval between two local date-times in different UTC offsets
Date Difference Calculator
Date LabDate Difference Calculatorcalendar difference in years months days and total days
Weekday Calculator
Date LabWeekday Calculatorday of the week for any valid calendar date
Processed locally: the local times and offsets you enter are converted in your browser, with no account required and nothing sent to a server at all.

Frequently asked questions

Does this handle daylight saving?

No. It applies the offsets you enter. Use it when you know the offsets that applied; use zone-aware software when the offset must be determined for you.

Which offset applies to a past timestamp?

The one in force at that location on that date. Historical time-zone rules change, so a maintained database is the authority.

Why does the tool show UTC values?

Because that is where the arithmetic happens, and seeing them makes an incorrect offset obvious immediately.