ETA Calculator

ETA Calculator

Estimate arrival time from remaining distance, average speed or pace, planned stops, delay allowance, rounding, and a manual timezone offset.

📌ETA presets
⚙Trip inputs

Use the distance still to go, not the original route length.

Moving average in the selected distance unit per hour.

Example: 8.5 means 8 minutes 30 seconds per mile or kilometer.

Use -4 for UTC-04:00, 5.5 for UTC+05:30, or 8 for UTC+08:00.

🕒ETA results
Arrival ETA
--
local offset clock time
Travel Time
--
distance / average speed
Stops + Buffer
--
planned non-moving time
Average Basis
--
speed or pace used
🧭Comparison grid
No Stops
--
Pure moving time only.
Planned ETA
--
Stops and buffer included.
Fast Case
--
10% faster moving segment.
Slow Case
--
15% slower moving segment.
📊Route profile cards
đŸ—‚ïžPreset comparison table
PresetModeDistanceSpeed or paceStop plan
⇄Speed and pace lookup
ActivityTypical speedPace per milePace per kmBest use
City traffic18 mph / 29 km/h3:20 min2:04 minDense local driving
Suburban driving35 mph / 56 km/h1:43 min1:04 minMixed lights and roads
Highway driving65 mph / 105 km/h0:55 min0:34 minOpen road estimates
Easy running6 mph / 9.7 km/h10:00 min6:13 minTraining runs
Road cycling15 mph / 24 km/h4:00 min2:29 minCommutes and rides
Moderate hiking2.5 mph / 4 km/h24:00 min14:55 minTrail planning
Small boat18 kn / 33 km/h3:20 min per nmi1:49 minMarine ETAs
⏳Stop and buffer guide
SituationStop minutesDelay percentFixed bufferReason
Short errand0 to 105%5 minParking, lights, elevator time
Highway trip10 to 258% to 12%10 to 20 minFuel, restrooms, slow exits
Delivery route4 to 8 each10% to 20%10 minDrop-off dwell time varies
Airport transfer0 to 515% to 30%20 to 40 minLate arrival has high penalty
Running event0 to 20% to 5%0 to 5 minAid stations and course crowding
Trail hike5 to 15 each15% to 30%15 to 45 minTerrain, photos, navigation
Freight leg20 to 4510% to 25%30 to 60 minInspection, gates, dispatch windows
🌐Timezone offset reference
Offset inputMeaningExample citiesWhen to adjust
-8UTC-08:00Los Angeles standard timeUse -7 during daylight time
-5UTC-05:00New York standard timeUse -4 during daylight time
0UTCLondon winter, ReykjavikUse 1 for UK summer time
1UTC+01:00Paris winter, LagosUse 2 for much of Europe in summer
5.5UTC+05:30India standard timeHalf-hour offsets are valid
8UTC+08:00Singapore, Perth, BeijingCheck regional daylight rules
9.5UTC+09:30Adelaide, DarwinSome locations change seasonally
🧼Formula method
StepFormulaWhat it controlsCommon mistake
Travel timeremaining distance / average speedMoving portion of the tripUsing posted speed instead of real average
Pace conversionspeed = 60 / pace minutesRunning, cycling, hiking, marine paceMixing mile pace with km distance
Stopsstop count x minutes per stopPlanned non-moving timeHiding stops inside speed and double counting
Delaytravel time x delay percentTraffic, terrain, weather, uncertaintyAdding delay only after the ETA is late
ETAstart/current time + travel time + stops/bufferArrival clock timeForgetting timezone offset or date rollover
💡ETA tips
Separate moving time from stop time. If your average speed already includes lunch, charging, fuel, or delivery dwell time, set planned stops to zero so the same delay is not counted twice.
Use the offset at the arrival location only when needed. This calculator treats the entered date and time as the clock in the selected offset. For a route crossing zones, recalculate with the destination offset to communicate the local arrival time.
Round upward for appointments. A 7:41 ETA is useful for tracking, but a 7:45 or 8:00 ETA is usually clearer for pickups, gates, bookings, or delivery promises.
Use pace mode when speed feels unnatural. Runners, hikers, cyclists, and paddlers often know minutes per mile, kilometer, or nautical mile more accurately than average speed.

When estimating how long it’ll take, factor in slow traffic and red lights. A lot of people just divides miles by mph. That doesn’t account for uncertainty!

You don’t have to try to manually convert minutes to hours; the calculator does that for you. It will also tell you whether a stop is eating into your buffer or adding to your total time. Planned stops are an afterthought for most. “The clock stops when I stop to get gas and then wait for inspection.” Nope. Clock never stops.

How to Plan Your Trip Time

A delivery route might look like a three-hour drive on a map, but if you add four stops at eight minutes each, you’ve added thirty-two minutes of non-moving time to your day. That is thirty-two minutes of total non-moving time.

A complex logistics leg looks very different than a simple errand, as illustrated by the reference table. Moving time versus dwell time has to be separated. Don’t double count for average speed, which includes time spent idling at lights. Don’t double count by adding those same minutes back in as stops. That’s the trick, knowing what you’re measuring.

How fast are you going? That’s a question more important than many realize. Sixty-five miles an hour on the highway feels different than creeping along in city traffic where your average speed might be barely eighteen miles per hour.

For mixed situations (technical terrain, weather, or just general urban congestion), you can add a delay percentage to your profile with the tool. It’s not pessimism; it’s risk management. Adding a ten-percent buffer goes from rushing to arrive to arriving calmly. One surprise traffic jam turns into a crisis without it. Sometimes that little bit of extra room makes all the difference between being late or on time.

If you’re planning a trip across a dateline (or working with people in various parts of the world), there’s another complication: timezones. Get those wrong and you could be setting your whole schedule off by hours. With this calculator, you can manually specify an offset for any timezone, ensuring that the total time aligns with local clock where you arrive. A four-hour mismatch can mean missing a flight or a meeting. Double-check the offset to what the real-world place will be when you arrive.

And then there’s rounding. Rounding is another psychological trick. When the calculator says your ETA is seven-forty-one, round it up to eight o’clock or seven forty-five. This creates a safer estimate that doesn’t force you to drive slower. This is especially true when penalty for being late is high (such as delivering something or picking someone up from airport). Notice how in the comparison grid, the fast and slow cases moves the timeline around? Better to show up early and wait versus showing up late and say sorry.

The device has marathon pacing and bike commute presets. I like that it allows you to switch from entering speed to entering pace, which is what runners understand (minutes per mile vs. Miles per hour. Miles per hour). It’s easier for me to enter eight minutes/mile than to figure out that’s the same as 12 mph. That means less thinking required on my part (less brainpower) and it automatically converts to speed/pace for you, no math required. Plan a route without needing to be a mathematician.

Just be honest about your conditions. Your ETA isn’t a prophecy; it’s an admission of what you intend to do now, given your assumptions about things that might go wrong. An ETA is more than a guess. It’s a plan with realistic speeds, reasonable buffer times, and stop time accounted for. It’s math (and there are some variables in there). If you forget about traffic, if you don’t include stops, then you’re not planning. You’re wrong. Plan with all the inputs and create a schedule that has a chance at standing up to real life. That’s how you transform a stressful guess into a solid plan.

And remember: The clock doesn’t care how confident you feel. Let the math handle it.

ETA Calculator