Speed, distance and time are connected by one of the most useful and widely applicable formulas in everyday mathematics — used for estimating a journey's duration, checking whether you will arrive on time, working out fuel needs, or converting a running pace into a finish-line estimate. The formula itself is simple, but people trip up surprisingly often on unit consistency and on correctly averaging speed across a journey with multiple legs. This guide covers the formula and the traps to avoid.
The core formula
The relationship is:
Speed = Distance ÷ Time
and this single equation rearranges to solve for whichever variable you are missing: Distance = Speed × Time, or Time = Distance ÷ Speed. If you know any two of the three values, you can always find the third. A car travelling at 60 km/h for 2.5 hours covers 60 × 2.5 = 150 km. The same car needing to cover 150 km and having only 2 hours available needs a speed of 150 ÷ 2 = 75 km/h. The Speed, Distance & Time Calculator solves for any of the three given the other two, handling the rearrangement automatically.
The unit-consistency trap
The single most common mistake with this formula is mixing units — using speed in km/h but time in minutes, or distance in miles but speed in km/h — which produces a numerically wrong answer even though the formula itself was applied correctly. Before calculating anything, make sure all three values share a consistent unit system: if speed is in km/h, time must be in hours and distance in kilometres; if you have time in minutes, either convert it to hours first or use a speed expressed in km/minute. A commonly overlooked version of this trap is forgetting to convert minutes to a fraction of an hour — 30 minutes is 0.5 hours, not 30, and plugging in 30 directly produces an answer 60 times too large.
Average speed is not simply the average of two speeds
This is a genuinely common and important error: if you travel a distance at one speed and then travel the same distance at a different speed, your average speed for the whole trip is not the simple arithmetic average of the two speeds. Because you spend more time travelling at the slower speed (covering the same distance takes longer when moving slower), the correct average speed is weighted toward the slower speed, calculated properly as total distance divided by total time, not by averaging the two speed values directly. For example, travelling 60 km at 30 km/h and then another 60 km at 60 km/h takes 2 hours plus 1 hour, 3 hours total, for 120 km — an average speed of 40 km/h, not the 45 km/h a naive averaging of 30 and 60 would incorrectly suggest.
Calculating a multi-leg journey correctly
For a journey made up of several legs at different speeds, the reliable method is to calculate the time taken for each individual leg separately (time = distance ÷ speed for that leg), sum all the individual times to get the total time, sum all the individual distances to get the total distance, and only then divide total distance by total time to get the genuine overall average speed. Skipping straight to averaging the speed values themselves, without going through the time calculation, is exactly the mistake described above and produces a systematically wrong answer whenever the leg distances or times are not identical.
Practical applications beyond driving
The same formula underlies far more than car journeys. Estimating a flight's arrival time uses the same speed-distance-time relationship, scaled to aviation speeds. Runners and cyclists use a closely related concept — pace, typically expressed as time per unit distance (minutes per kilometre) rather than distance per unit time — to plan race splits and predict finish times; the Pace Converter converts between pace and speed formats, which is useful since running culture typically talks in pace while cycling and driving typically talk in speed. Fuel planning for a trip similarly starts from knowing the distance and your vehicle's expected speed and consumption, which the Fuel Cost Calculator extends into an actual cost estimate once distance is known.
Instantaneous vs average speed
It is worth distinguishing between average speed, which the formula above calculates over an entire journey or leg, and instantaneous speed — what a speedometer shows at any single moment, which can vary considerably throughout a trip due to traffic, stops, and changes in road type. A journey's average speed is almost always lower than its peak instantaneous speed, since it accounts for every slowdown, stop light and traffic delay along the way, not just the moments of free-flowing travel. When planning a trip using the speed-distance-time formula, using a realistic average speed that accounts for expected traffic and stops produces a far more reliable time estimate than using the road's posted speed limit as if it were sustained for the entire journey.
Working backward from a deadline
A frequent real-world use of the formula is working backward from a required arrival time: given a distance and a time you need to arrive by, the formula tells you exactly what average speed you must maintain, which is useful for deciding whether a planned departure time leaves enough margin, or for recognising early that a trip is unrealistic at legal or safe speeds and an earlier departure or a different route is needed. This use case is exactly where unit consistency matters most, since a small conversion slip when working backward from a tight deadline can produce a departure-time recommendation that is subtly, dangerously wrong.
Key takeaways
- Speed = Distance ÷ Time, rearranging to solve for whichever value is missing given the other two.
- Always use consistent units across all three values — mixing minutes with hours is the most common error.
- Average speed over a journey is total distance ÷ total time, never a simple average of individual speeds.
- For multi-leg trips, calculate each leg's time separately, then sum distances and times before dividing.