Running Pace, Speed and Finish Time: How They're All Connected

Pace, speed and finish time are really just three different ways of expressing the same underlying relationship between distance and time — once you know how to calculate running pace from any two of the three, the third follows automatically.

The two formulas

A worked example

5km run in 25 minutes: pace = 25 ÷ 5 = 5:00 min/km; speed = 5 ÷ (25/60) = 12 km/h. Run 10km in 50 minutes — double the distance, double the time — and both pace and speed come out identical: 5:00 min/km and 12 km/h. The Pace Calculator converts between distance, time, pace and speed automatically.

Using a known pace to predict other distances

If your comfortable training pace is 5:00/km, a straightforward (though optimistic) estimate for a 10K is 50 minutes, and for a half marathon (21.1km) is roughly 1:45:30 — simply pace × distance. Real race times deviate from this simple multiplication for longer distances, since maintaining an identical pace over a much longer effort is physiologically harder than over a shorter one — most runners slow somewhat as distance increases, which is why dedicated race-time prediction formulas (like Riegel’s formula) apply a scaling exponent rather than a flat multiplication for cross-distance predictions.

Distance	Naive estimate at 5:00/km pace
5K	25:00
10K	50:00
Half marathon	~1:45:30
Marathon	~3:31:00 (likely optimistic — real marathon pace is usually slower than 10K pace)

Converting between metric and imperial pace

Pace conventions differ by region — minutes per kilometer is standard in most of the world, while minutes per mile remains common in the United States and UK for road races. Since 1 mile ≈ 1.609km, a 5:00/km pace converts to roughly 8:03/mile — close enough to “8 minutes per mile” that the two get casually conflated, though they’re not quite identical, a distinction worth checking carefully when comparing a training pace quoted in one convention against a race plan quoted in the other.

Why pace matters more than raw speed for training

Runners track pace rather than speed mainly because training plans are typically structured around per-kilometer or per-mile splits — “run your easy days at 6:00/km” is a more directly actionable instruction during a run than a speed figure, since checking a per-distance split against a watch is simpler mid-run than continuously tracking speed.

Why real races slow down over longer distances

The naive “pace × distance” estimate assumes an identical pace can be held regardless of distance, which isn’t physiologically realistic beyond a certain point. Riegel’s formula, a widely used race-time prediction model developed by Peter Riegel in 1977, applies a scaling exponent (commonly around 1.06) to account for this: predicted time for a new distance = known time × (new distance ÷ known distance)^1.06. That small exponent above 1.0 is exactly what captures the real-world tendency to slow down somewhat as distance increases — a runner’s 10K pace reliably predicts a slightly slower marathon pace, not an identical one, and Riegel’s formula is one standard way of quantifying how much slower.

Splits: pace applied to sections of a single run

The same pace math applies at a smaller scale too — a “split” is simply the pace for one segment of a longer run, and comparing splits across a race is a standard way runners check whether they’re pacing evenly, starting too fast, or finishing strong. A negative split (second half faster than the first) is often considered a well-executed race strategy, since starting conservatively and having energy remaining for a strong finish tends to produce better overall times than starting fast and fading — the same reason many pacing plans for longer races deliberately target an even or slightly negative split rather than the fastest possible early pace.

Pairing pace with heart rate zones

Pace measures external output — how fast you’re covering ground — while heart rate measures internal effort. The two don’t always move together: fatigue, heat, and hills can all push heart rate up at an identical pace. Checking your target heart rate zones alongside pace gives a fuller picture of effort than pace alone, particularly for structured interval or tempo training where staying within a specific intensity zone matters more than hitting an exact pace number.

FAQ

Why do pace and speed give different-looking numbers for the same run? They’re just different units for the same information — pace is minutes per kilometer (or mile), speed is kilometers (or miles) per hour. Converting between them doesn’t change the underlying effort.

Can I use a 5K pace to predict my marathon time? Only roughly — most runners can’t sustain their 5K pace over a full marathon, so a direct multiplication tends to be optimistic. Dedicated race-prediction formulas apply a scaling factor to account for this.

Should I train by pace or by heart rate? Many training plans use both — pace for structured workouts, heart rate as a check on whether a given pace is producing the intended intensity on a specific day, since factors like heat and fatigue can shift heart rate at an identical pace.

What’s a negative split and why do coaches recommend it? Running the second half of a race faster than the first — it’s generally associated with better overall race outcomes than starting fast and fading, since even or conservative early pacing tends to preserve more energy for a strong finish.

How accurate is Riegel’s formula for predicting race times across very different distances? Reasonably accurate for moderate distance jumps (like 5K to 10K), but it tends to lose accuracy for very large jumps (like 5K to marathon), where factors beyond pure pacing — like fueling and pacing discipline over hours rather than minutes — start to matter more.