ETA Calculator
Departure plus duration is arrival — plus distance and speed mode
Arrival math is addition with units
Every ETA is one addition: departure plus duration. The only real work is keeping units straight — hours with hours, and distance over speed collapsing to time. Get the units consistent and arrival time falls out exactly.
What this tool does
- 🛬 Adds trip duration to departure for arrival time
- 🗺️ Converts distance ÷ speed into travel time
- 📦 Breaks durations into days, hours, minutes
- 🕐 One-click fill of the current moment
When to use it
- Flight lands in 7h40 — what time is that here?
- 300 km at 100 km/h — when do we arrive?
- Splitting a drive into day chunks
Privacy: pure date arithmetic locally — itineraries you type never leave your browser.
Last updated · 2026-09-01
How the math works
Datetime-local values parse to epoch milliseconds; durations add directly. Distance over speed multiplies to milliseconds (unit-agnostic). Results render as local YYYY-MM-DD HH:MM with durations split into days/hours/minutes.
Why ETA here?
Two questions, one answer
Departure-plus-duration and distance-over-speed live side by side — the two shapes every when-do-we-get-there question takes.
Honest precision
Days, hours, minutes — no fake seconds, no time-zone theater. The page says what it knows and names what it doesn't.
Now in one click
The Use-now button stamps the current local moment, so most trips need exactly two more inputs.
Frequently asked questions
Does it handle time zones?⌄
No — everything computes in your device's local time. Crossing zones, add the offset yourself; the math stays simple and honest instead of half-handling zones.
Distance and speed in which units?⌄
Any matching pair: km with km/h, miles with mph, meters with m/s. The tool divides distance by speed, so only consistency matters, not the specific units.
Why no seconds in the result?⌄
Travel estimates below a minute are noise — traffic lights dwarf them. Minutes are the honest precision for trips; the stopwatch covers split seconds.
Frequently asked questions
Does it handle time zones?
No — everything computes in your device's local time. Crossing zones, add the offset yourself; the math stays simple and honest instead of half-handling zones.
Distance and speed in which units?
Any matching pair: km with km/h, miles with mph, meters with m/s. The tool divides distance by speed, so only consistency matters, not the specific units.
Why no seconds in the result?
Travel estimates below a minute are noise — traffic lights dwarf them. Minutes are the honest precision for trips; the stopwatch covers split seconds.