Average Travel Speed Calculator
Calculate your average travel speed over an entire journey by dividing total distance by total elapsed time - including stops, traffic, and delays. Use it for road trips, train rides, and multi-leg flights when you need a realistic door-to-door pace rather than a peak cruising speed.
Last updated: May 2026
Compare with similar
About this calculator
The formula is averageSpeed = totalDistance / travelTime. Variables: totalDistance is the full journey length in your distance unit (miles or kilometers); travelTime is total elapsed time from departure to arrival in hours, including stops, fuel breaks, traffic delays, and any layovers. The output is the effective speed that captures real travel experience, distinct from peak instantaneous speed (your speedometer reading) or scheduled vehicle cruise speed. Edge cases: average speed over multi-segment journeys with very different cruising speeds requires using the harmonic mean of segment speeds weighted by distance - not the arithmetic average of speeds - because slower segments take disproportionately more time. For example, 100 miles at 60 mph and 100 miles at 20 mph has average speed 200 / (100/60 + 100/20) = 200 / 6.67 = 30 mph, not (60 + 20)/2 = 40 mph. Door-to-door flight comparisons must include ground transport to and from airports, security, and boarding/deboarding - often 3 hours of overhead that pulls a 500-mph cruise down to an effective ~200 mph for short trips. Round trips with different one-way speeds (e.g. uphill vs downhill, or with vs against jet stream) have an average speed below the arithmetic mean of the two legs for the same harmonic-mean reason. Speed limits and posted maximums are upper bounds on legal cruising speed only; the average speed achievable on a long trip with breaks rarely exceeds 75% of the speed limit.
How to use
Example 1 - A 350-mile road trip taking 6 hours including a 30-minute lunch stop and 15 minutes of fuel/restroom. averageSpeed = 350 / 6 = 58.3 mph. Verify against the cruising assumption: 350 miles ÷ (6 - 0.75 stop hours) = 350 / 5.25 = 66.7 mph cruising speed, consistent with a 70-mph interstate with occasional slowdowns. The 58.3 mph average is the realistic door-to-door pace; planning a 700-mile day at "70 mph average" is unrealistic - at 58.3 mph average, 700 miles takes 12 hours, not 10. Example 2 - A 2,800-mile flight from NY to LA taking 6.5 hours gate-to-gate but 11 hours door-to-door (90 min to airport, 90 min through security and boarding, 6.5 hours airborne, 30 min deplaning, 90 min from LAX to destination, 30 min total small buffers). Pure flight average: 2,800 / 6.5 = 431 mph. Door-to-door average: 2,800 / 11 = 254 mph - almost half the airborne speed. Verify by checking that for short distances (~300 miles) the door-to-door average for a flight collapses to ~50 mph because the fixed airport overhead dominates, often making driving or rail competitive. This is the math behind "why bother flying for under 500 miles" - the cruising speed advantage is real, but the overhead costs eat most of it on short trips.
Frequently asked questions
Why is my actual road-trip average always lower than the speed limit?
Even cruising exactly at the speed limit, average speed over a multi-hour trip drops because of fuel stops, food breaks, traffic slowdowns, road work, and the time spent accelerating and decelerating at every exit. A typical interstate trip averages 75-85% of the posted limit over distances above 200 miles: a 70-mph interstate corridor produces a real average around 55-60 mph. Mountain passes, urban areas, and weather can push it to 65-70% (45-50 mph average on a 70-mph road). To plan realistically, multiply the posted limit by 0.8 for highway-dominant trips, 0.7 for mixed routes, and 0.6 for trips with significant urban or mountain segments. This is why "700 miles is an 8-hour drive" estimates often turn into 10 hours in practice - they assume cruising speed rather than average speed.
How do I correctly average speed across segments with different cruising speeds?
You must use the harmonic mean weighted by distance, not the arithmetic mean of speeds. The formula is averageSpeed = totalDistance / totalTime, where totalTime is the sum of (segmentDistance / segmentSpeed) for each segment. For example, driving 100 miles at 60 mph then 100 miles at 30 mph gives total time = 100/60 + 100/30 = 5 hours, average = 200 / 5 = 40 mph - not (60 + 30) / 2 = 45 mph. The arithmetic mean overestimates because slower segments take more time and thus have more weight in the real average. The intuition: speed contributes to the answer per unit time, and slower segments contribute more time. This matters most when segment speeds differ by more than 2x - long flights with short connections, or fast interstates broken by slow city segments. The simple totalDistance / totalTime formula in this calculator handles this correctly as long as you give it the total time, not segment averages.
When does flying beat driving on door-to-door average speed?
Including airport overhead (typically 3-4 hours total: drive to airport + parking + security + boarding + deplaning + baggage + onward transit), flying breaks even with driving at roughly 200-300 miles. Below 300 miles, driving is often faster door-to-door, especially if your origin or destination is far from major airports. Between 300 and 600 miles, flying wins on speed but the time advantage is modest (often only 1-2 hours) and the cost premium can be 5-10x driving for short trips with limited bookings; rail (Amtrak Acela, European HSR) is often the right choice in this band. Above 600 miles, flying decisively wins on speed regardless of overhead, and above 1,500 miles it is the only practical option for same-day or next-day arrival. The door-to-door average for a 500-mile flight is typically 100-150 mph; for 2,000 miles it is 250-400 mph; for 5,000 miles (transcontinental) it can exceed 500 mph because the overhead becomes a small fraction.
What are common mistakes when computing average travel speed?
The most common mistake is using arithmetic mean of segment speeds instead of distance/total-time - this overstates the true average and produces optimistic ETAs. Another frequent error is using moving time rather than elapsed time - Google Maps and Waze report moving time excluding stops, which can understate door-to-door duration by 20-30% on long trips. For flights, people commonly use the in-air time from departure-to-arrival airport rather than door-to-door, which ignores 3+ hours of overhead that dominate on short flights. Failing to factor in time zones is another common error: a 6-hour westbound flight arrives "3 hours later" by clock time because of zone change, not a 9-hour flight. Finally, planning a long road trip at speed-limit average ignores that fatigue caps continuous driving at 4-5 hours before a real break is needed for safety, which compresses how far you can realistically go in a day to ~500 miles rather than 700+.
When should I NOT use an average-speed calculator?
Skip it for short trips under an hour where stops are minimal and a single-segment estimate (distance / cruising speed) is accurate enough. The calculator is the wrong tool for real-time speed; for that, use your speedometer or GPS, which gives instantaneous rather than averaged values. Do not use it to set your driving speed - speed limits and road conditions determine safe cruising speed, not arrival-time math; pushing average speed up is rarely worth the safety, ticket, and fuel-cost penalty. It is also not useful for planning multi-modal trips (car + train + plane), where each segment has different overhead structures that do not combine cleanly into a single average. Finally, for endurance cycling or running where the goal is a target pace, use cadence/heart-rate metrics rather than average speed - sports physiology cares about sustained output, not elapsed time.