irmion
AideLog in Trouver un outil

BROWSER-ONLY DATE TOOL · Date, Time & Scheduling

Multi-Stop Time Zone Adjustment

Convert a two-leg trip through origin, stop, and destination time zones.

Depart New York at 09:00 on 1 March 2025; after 2 hours to London, 1 hour layover, and 8 hours onward, Tokyo local arrival is 10:00 on 2 March.

Set up your dates

Enter the values for this task. The example shows the expected input format.

Use a real date from 1900 to 2100 in YYYY-MM-DD format.

Use 24-hour local time, such as 09:00.

Choose a named IANA time zone.

Choose a named IANA time zone.

Choose a named IANA time zone.

Elapsed minutes from origin to stop.

Allowed range: 1 to 2880.

Elapsed minutes at the stop before departing again.

Allowed range: 0 to 2880.

Elapsed minutes from stop to destination.

Allowed range: 1 to 2880.

Your result

Destination arrival

UNDERSTAND THE RESULT

How to use the Multi-Stop Time Zone Adjustment

Use this to compare local arrival times for an origin, stop, and destination without manually adding time-zone offsets. The calculation follows one UTC timeline across both travel legs.

  1. What to enter

    Enter the origin local date and time, three IANA zones, first-leg minutes, layover minutes, and second-leg minutes. Durations are elapsed time, not clock readings in the arrival zones.

  2. Worked example

    Depart New York at 09:00 on 1 March 2025; after 2 hours to London, 1 hour layover, and 8 hours onward, Tokyo local arrival is 10:00 on 2 March.

  3. How to read the result

    The rows show each location's local date-time alongside the reference instant. Read the date as well as the hour: a trip can cross midnight or a daylight-saving change.

How the result is worked out

Resolve the entered origin local time to one UTC instant, add each elapsed travel and layover duration, then display arrival in each named zone.

What to check

A local departure that is skipped or repeated during a clock change is rejected. Future zone rules may change after browser updates.

A common mistake to avoid

A skipped or repeated local departure time is rejected because it cannot identify one instant. Real itinerary times may change; verify travel details with the carrier.

Named time-zone results use the time-zone data installed in your browser. Future rules can change. How JavaScript handles named time zones

This tool calculates in your browser. The dates you enter are not sent to the Nirmion API.

Questions to check

What if departure time occurs twice?

The tool asks for a different unambiguous local time instead of choosing one instant silently.

Does the layover use the stop's clock time?

The entered layover is elapsed minutes. It is added on the UTC timeline before the second leg, then displayed in the selected local zones.

Why can an arrival date differ from departure?

Elapsed travel time and the destination's dated UTC offset can cross a local midnight, even when the displayed hour appears earlier.