Departure, offsets and travel time
Arrival and duration
All four readings
This tool uses fixed UTC offsets with no daylight-saving or time-zone database; check your flight's actual times with the carrier.
Method and rules
Everything is first converted to absolute minutes: the departure date becomes a civil day number, times 1440 plus the departure clock time, minus the departure offset, giving one absolute instant; the arrival instant is then read back at the arrival offset as a local date and time. The day-shift label is the difference in day numbers between the arrival date and the departure date.
In "From arrival time" mode, the arrival date is the departure date, or one day later when the next-day toggle is on — nothing else. The tool never adds 24 hours just because the arrival clock reading is smaller. The implied duration must be greater than 0 and at most 48 hours, otherwise an error is reported.
Crossing the date line, the arrival date can be one day — even two days — before the departure date; with long flights plus an offset difference the day shift can reach +4 days. Trust the date and the day-shift label, not the clock reading alone.
Frequently asked questions
Why can the arrival clock time look earlier than the departure time?
The destination may be in a later-offset zone, so the clock reading moves backwards, even to the day before; check the day-shift label and the arrival date.
Does it handle daylight saving time?
No. It uses only the fixed UTC offsets you enter; during daylight saving time, enter the offset actually in effect, and always confirm real flight times with the carrier.
All computation happens in your browser; nothing is sent anywhere.