You know the distance — say it is 300 miles from one city to the next. The question everyone actually wants answered is the next one: how long will it take to get there? Distance is fixed, but time depends on how fast you can really travel, how often you stop, and what the roads are like in between. This guide turns a distance into a believable arrival time, explains how to pick a realistic average speed, and shows why a live map app's ETA almost never matches the back-of-the-envelope number you started with.
The one formula you need
Estimating drive time starts with a single, friendly piece of arithmetic:
time = distance ÷ speed
If you are driving 300 miles at an average of 60 miles per hour, the journey takes 300 ÷ 60 = 5 hours. That is the whole idea. The trick is not the formula — it is choosing the right number for "speed." People almost always plug in the speed limit, and that is exactly where the estimate goes wrong.
The speed you want is your average speed for the entire trip, not the top speed you reach on the open highway. Average speed quietly absorbs every slow stretch: the crawl out of the city, the roundabouts, the road that drops to 40 because of a village, the few minutes stuck behind a tractor. Even a motorway journey with no traffic rarely averages the posted limit once you fold in the start and the finish at each end.
A useful rule of thumb: your real average speed is often 10 to 20 percent below the speed limit of the fastest road on your route, before you add any stops at all.
Choosing a realistic average speed
Different kinds of road move you along at very different rates. Rather than guess one number for the whole country, it helps to think in road types and blend them. Here are sensible planning averages — deliberately conservative, because optimism is what makes you late.
| Road type | Typical planning average | What slows you down |
|---|---|---|
| Motorway / interstate | 60–70 mph (95–110 km/h) | Merging, tolls, the occasional jam |
| Rural highway / A-road | 45–55 mph (70–90 km/h) | Junctions, towns, slower traffic, bends |
| City and suburban streets | 15–25 mph (25–40 km/h) | Traffic lights, turns, pedestrians, parking |
| Mountain or coastal road | 25–40 mph (40–65 km/h) | Switchbacks, gradients, single lanes |
For a long intercity trip that is mostly highway with a city at each end, a blended average of around 55 mph (90 km/h) is a reliable starting point. For a winding regional route with several towns, drop to 40–45 mph (65–70 km/h). These are not laws of physics — they are planning numbers chosen to keep you honest. If you reach your destination a little early, that is a much nicer surprise than the reverse.
A quick worked example
Imagine a 300-mile trip: 40 miles of city streets on each end (80 miles total) and 220 miles of motorway in between.
- City portion: 80 miles ÷ 20 mph = 4 hours
- Motorway portion: 220 miles ÷ 65 mph = about 3.4 hours
- Driving time: roughly 7.4 hours
Notice that the 80 city miles eat up more clock time than the 220 highway miles. That is the single most common reason a "five-hour trip" turns into a seven-hour day — the slow miles at each end count far more than people expect.
Don't forget the stops
The formula gives you driving time. A real journey also includes the time you are not moving, and those minutes add up fast. Build them in deliberately rather than pretending they will not happen.
- Rest and meal breaks. A common, safe rhythm is a short break every two hours. On a full-day drive that is easily 45–90 minutes of stops, and it is non-negotiable for staying alert.
- Fuel or charging. A fuel stop is 10–15 minutes; charging an electric car is more like 20–45 minutes depending on the charger and how low you let the battery get. Plan charging stops around towns where you would want to stretch anyway.
- The "found time" tax. Detours for a view, a wrong turn, hunting for parking at the other end, a queue at a toll booth. Twenty minutes of slack across a long day is realistic, not pessimistic.
A simple, honest way to plan: take your driving-time estimate and add roughly 15 minutes of stops for every two hours behind the wheel. Our 7.4-hour drive above becomes closer to a 9-hour day door to door. That is the number you should tell the people waiting for you.
Why live map ETAs are different (and usually better)
Punch the same trip into a navigation app and its ETA will rarely match your hand calculation. That is not a flaw in either method — they are doing different jobs. A live router has information you do not.
- It knows the actual route, segment by segment. Instead of one blended average, it applies a real speed to every individual road, including the slow last mile to your exact address.
- It sees current traffic. Live and historical traffic data nudges the estimate up at rush hour and down at 3 a.m. on the same road.
- It factors in time of day and day of week. The same route can differ by an hour between a Tuesday morning and a Friday evening.
- It usually ignores your stops. Most apps estimate continuous driving. The coffee, the lunch, the fuel — those are still on you to add.
So the two approaches complement each other. The hand estimate is perfect for early planning, when you only know the cities and want a ballpark before you have committed to a date or a route. The live ETA is what you trust on the day, once traffic and your exact start and end points are real. If your hand estimate and the app disagree wildly, it is usually because the app is counting traffic and the precise route — and you forgot to add your breaks.
Arriving across a time-zone change
Drive far enough east or west and a new wrinkle appears: the clock at your destination is not the clock you left behind. Drive time and arrival time are two different things, and confusing them is how people end up an hour off for a dinner reservation or a hotel check-in.
The method is simple once you separate the two ideas:
- Work out your total journey time (driving + stops) using everything above.
- Add that to your departure time to get the arrival time in your home time zone.
- Then shift the clock for the time-zone difference at the destination.
For example: you leave at 8:00 a.m. and the trip takes 9 hours, so you would arrive at 5:00 p.m. by your home clock. But if your destination is one hour ahead, the local time on arrival is actually 6:00 p.m. Cross westward into a zone an hour behind and it becomes 4:00 p.m. instead. The drive is identical; only the clock on the wall changes.
This catches people most on long north-south-leaning routes that still nick a zone boundary, and on any trip near the edge of a time zone. Before you promise an arrival time, check what the clock will actually read where you are going with our time in a place tool — it shows the current local time and UTC offset for any city, so you can do the shift with confidence. If you want the full background on why offsets land on odd half-hours and shift with daylight saving, see our guide to time zones and UTC offsets.
Putting it all together
Estimating a drive is less about precision and more about not fooling yourself. Start with the distance, divide by a realistic average speed rather than the speed limit, add honest time for rest and fuel, and remember the clock can move under you when you cross a time zone. Do that and your "how long will it take?" answer will land close to reality — and the live ETA on the day becomes a refinement, not a nasty surprise.
Ready to plan a real trip? Start by getting the honest distance between your two cities with our distance between cities calculator, then divide by your chosen average speed to turn those miles into hours. And before you tell anyone when you will arrive, confirm the local clock at the far end with the time in a place tool.