Average Speed Calculator

Why average speed is not the arithmetic mean of speeds

If you drive 50 km at 50 km/h and then 50 km at 100 km/h, your average speed is not 75 km/h. The first leg takes one hour and the second takes half an hour, so you cover 100 km in 1.5 hours, giving an average of 66.7 km/h. Arithmetic averaging ignores the time spent at each speed.

The correct approach is to divide total distance by total time. For a multi-segment journey the time per segment is the segment distance divided by the segment speed. Summing all segment times and dividing total distance by that total time gives the true average speed.

That is why searchers looking for an average speed formula often end up needing a time-weighted calculation rather than a direct mean of two or more speeds. When equal distances are covered at different speeds, the harmonic-mean idea explains why the slower segment pulls the final answer down more than intuition suggests.

Practical uses

Average speed calculators are useful for road trips where rest stops and urban sections reduce overall pace, cycling or running events where pace varies by terrain, and logistics planning where delivery windows depend on realistic journey times.

When planning a journey you can enter each leg separately to model motorway, A-road, and urban segments at realistic speeds and see the overall average for the full trip.

This also helps if you want an average speed calculator with solution for a worked problem: instead of guessing, you can break the journey into legs, compute the time for each one, and then combine them into a single trip average.

Worked example: average speed across two equal-distance legs

Suppose a 100 km trip is split into two equal 50 km legs. You travel the first 50 km at 50 km/h and the second 50 km at 100 km/h. The first leg takes 1 hour and the second leg takes 0.5 hours, so total time is 1.5 hours.

Average speed = 100 km / 1.5 h = 66.7 km/h. This is the standard answer for the classic average speed formula example, and it shows why you cannot just average 50 and 100 to get 75 km/h.

The same logic works for miles, cycling rides, and mixed driving conditions. As long as distance and time units stay consistent, the formula is unchanged.

Average speed with stops, delays, and moving speed

Trip average speed includes every minute in the elapsed time if you choose to count stops. That means traffic lights, rest breaks, loading delays, and waiting time all reduce the final answer even though the vehicle may have been travelling quickly while moving.

Moving speed is different: it counts only the time when the vehicle, rider, or runner is actually in motion. If your sat-nav or bike computer shows both moving speed and trip average speed, the lower figure is usually the better planning number for arrival time.

For a travel or cycling use case, decide up front whether your average speed with stops should include the whole journey clock. If it should, use total elapsed time in single-leg mode or include slower or stopped segments explicitly in multi-segment mode.

The live calculator includes an optional stops and delays field for single-leg trips. Enter the moving time in hours and minutes, then add stop minutes separately. The result shows the stop-inclusive trip average and, when stops are present, the moving speed so you can see how much waiting time changed the practical planning number.

Comparing actual average speed with a target speed

For road trips, delivery planning, time trials, and commute estimates, the useful question is often not just “what was my average speed?” but “how far ahead or behind the target pace was this trip?” The optional target-speed field answers that by comparing your actual elapsed time with the time the same distance would take at the benchmark speed.

For example, if you cover 120 km in 2 hours, your trip average is 60 km/h. If the target speed was 80 km/h, the same distance would take 1.5 hours, so the trip is 30 minutes slower than target. This is more actionable than a percentage alone because it translates speed differences into arrival-time impact.

Use a realistic target. A legal speed limit, moving-speed target, race goal, or scheduled route average may all mean different things. If stops, traffic, gradients, loading time, or border checks matter, use the stop-inclusive result for the plan instead of comparing only the moving portions of the trip.

Round trips and equal-distance journeys

A round trip where the outward and return legs cover the same distance is another place where the harmonic-mean pattern appears. If you drive out at 40 mph and return at 60 mph over the same distance, the overall average is 48 mph, not 50 mph.

The reason is the same as before: the slower leg consumes more time. Whenever equal distances are covered at different speeds, the lower speed weighs more heavily in the final average because time, not just distance, drives the formula.

That makes an average speed finder especially useful for road-trip planning, bike rides with climbs and descents, or delivery routes where one congested leg can drag down the full-day average.

Scope and limits of an average speed calculator

This page calculates average speed from distance and time only. It does not estimate fuel use, traffic conditions, acceleration, gradient effects, or legal speed compliance, and it does not replace a dedicated speed-distance-time solver when you need to solve for a different variable.

Results are only as good as the inputs. If one segment uses the wrong distance, the wrong time basis, or a moving speed when you meant total trip time, the final average will be misleading. Treat the result as a planning or explanation aid rather than an exact reconstruction of every real-world condition.