Distance = Rate x Time: The Formula That Moves the World

The shortcut that cost us four minutes

My daughter asked whether the shortcut past the reservoir would get us to the library faster. The long way was 2 kilometres of flat path at a comfortable 15 km/h. The shortcut was 1.6 kilometres, mostly uphill, at about 8 km/h. My brain averaged the two speeds, got 11.5, and told her we would save a few minutes.

We lost four. She said nothing, which was the worst part. The arithmetic was not wrong — the mistake was one level up, in choosing what to average. I had averaged two rates while spending equal distances, and that is the one situation where averaging rates is not allowed. It is a small, extremely common error, and it deserves more than a memorised line.

One equation, three questions

Everything in motion collapses into one relationship. It is worth seeing it as a shape, because the shape tells you how to rearrange it:

The move is the same every time: cover up the piece you want, then multiply the two leftovers or divide by the one left over. Distance sits alone on top, so it always comes from multiplying. Rate and time sit on the bottom, so either one always comes from dividing. That is the whole decision procedure, and it is why distance is the only one of the three that never needs a division.

Same equation, three different questions:

Before you touch the triangle, make sure the two known units can cancel. Mixing minutes with hours is the classic way to be right about the method and wrong about the answer; our article on converting units fixes that first.

A rate is a promise about the future, not a fact about the past

A rate you measured on a finished trip is history. A rate you plug in before leaving is a forecast — a promise to somebody else about a number you have not observed. That reframing explains the dashboard better than trusting it.

The range reading on a fuel gauge is this equation run backwards: the car takes the fuel in the tank, estimates a rate from your recent driving, and multiplies to offer a distance. A weather forecast wearing a decimal point. When it runs low the estimate comes from slow recent driving, so it overpromises — which is why the number drops faster than the tank empties. A trip computer is the same idea with a better rate and the same optimism bias.

A rate is also just a slope. Graph distance against time and the three numbers become a straight line, steeper for faster, exactly as our article on slope describes.

You may only average rates under one condition

Here is the rule that would have saved me four minutes: average the rates only if you spent equal time at each rate. Otherwise add up the distances and divide by the total time. A slow hour counts exactly as much as a fast one, so when the time is uneven, averaging over-counts the slow rate.

Split a trip by equal time and averaging works: one hour at 60 km/h and one hour at 20 km/h gives 80 km in 2 hours, and 40 km/h, exactly the average of the two. Now split the same 80 km by equal distance instead — 40 km at 60 km/h takes 40 minutes, 40 km at 20 km/h takes two hours:

Same journey, same two speeds, and the arithmetic mean says 40 while the truth is 30. The average always leans toward the slower speed, and leans harder the more of the trip you spend crawling — often the difference between making the meeting and missing it.

Two vehicles, one road

Catch-up problems look intimidating and are really two rate questions stacked on top of each other. Step one converts the head start into a distance. Step two asks when that distance disappears.

I leave at 6:00 doing 50 km/h. My brother leaves thirty minutes later doing 80 km/h. When does he catch me? In half an hour I am 25 km ahead. He gains 80 − 50 = 30 km every hour. So 25 ÷ 30 = 50 minutes, and he catches me at 7:20, about 67 km from the door. Notice the second subtraction: the speeds never touch each other in the answer, only in the rate of closing.

The method also tells you when there is no answer. If the second vehicle is not faster, the gap never closes. And if the head start is already too large to recover in the time available, no cleverer method helps — you only have to notice they will not meet. Knowing a problem has no solution is half of solving rate problems.

This is not the unit-rate question

Rate and unit rate are neighbours that get confused. Our article on unit rate answers a comparison question — two jars, two prices, two athletes: which one wins? Its job is shrinking a ratio to exactly one unit. This article is about a different question: I have a rate and a time and I am about to make a prediction. Comparing two speeds is not the same as committing to one.

Try it on these three

A train leaves at 09:00 at 90 km/h; a second leaves the same station at 09:40 at 120 km/h. When and where does the second catch the first? Then: you drive 30 km at 60 km/h and 30 km at 40 km/h — what is your average speed, and what is the wrong answer most people give? Finally: a bus reaches the depot at 11:00, having left at 08:20, and the odometer says 148 km. How fast was it going on average, and should you trust the driver's claim of 90 km/h the whole way?

Frequently Asked Questions