How does race time prediction work?

Race time prediction commonly uses Riegel's formula, developed by Peter Riegel in 1977: predicted time equals known time multiplied by the ratio of target distance to known distance, raised to the power of 1.06. This exponent accounts for the fact that runners naturally slow down over longer distances rather than maintaining the exact same pace.

Why does a predicted marathon time seem slower than just multiplying 5K pace by the distance?

Runners cannot sustain the same pace over a marathon that they can over a 5K, due to fatigue, fueling demands, and pacing strategy differences. Riegel's 1.06 exponent builds in this natural slowdown, which is why the predicted marathon time is proportionally slower than a straight linear projection from a short race pace.

How accurate is Riegel's formula for race prediction?

Riegel's formula tends to be reasonably accurate for predicting races that aren't dramatically different in distance from a known result, such as predicting a 10K from a 5K. Predictions become less reliable across very large distance jumps, such as predicting a marathon time from a very short race, since factors like fueling strategy and mental endurance become increasingly important at longer distances.

What is the difference between pace and speed?

Pace expresses how long it takes to cover a fixed distance, such as minutes per kilometer, and is the format most runners think in. Speed expresses distance covered per unit of time, such as kilometers per hour, and is the more common format for cycling or general fitness tracking.

What is a good running pace for a beginner?

There is no single universal good pace — it depends entirely on individual fitness level and goals. Many beginner running programs target a conversational pace where you can comfortably hold a conversation while running, often somewhere in the range of 7 to 9 minutes per kilometer for new runners, though this varies significantly by individual.

Riegel's Formula Explained: How Race Time Prediction Works (2026)

Q: How do I calculate my running pace?

Divide your total time by the distance covered. For example, running 5 kilometers in 25 minutes gives a pace of 5 minutes per kilometer. A pace calculator does this automatically and also converts between kilometers and miles.

Pace, Speed, and Why Runners Think Differently From Cyclists

Runners almost universally think in pace — minutes per kilometer or mile — while cyclists and general fitness trackers more often think in speed — kilometers or miles per hour. Both describe the same underlying rate, just inverted: a faster pace (fewer minutes per km) corresponds to a higher speed (more km per hour). Converting between the two is simple arithmetic, but predicting a time at a completely different distance is where things get more interesting.

⏱️

Pace

Minutes per kilometer or mile — how runners naturally think

💨

Speed

Distance covered per hour — useful for treadmills and cycling

🎯

Race Prediction

Estimate finish times at other distances from one known result

How Riegel's Race Time Prediction Works

Developed by engineer and running researcher Peter Riegel in 1977, this formula remains the most widely used method for predicting race performance at one distance based on a known result at another. It correctly accounts for something a simple linear projection misses: runners naturally slow down over longer distances due to fatigue, fueling needs, and pacing strategy.

Riegel's Formula

Predicted Time = Known Time × (Target Distance ÷ Known Distance)^1.06

The exponent of 1.06 — rather than 1.0, which would imply maintaining identical pace across any distance — is what builds in the realistic slowdown. The further the target distance stretches beyond the known one, the more this exponent pulls the prediction away from a naive straight-line multiplication, reflecting real endurance limitations.

How Accurate Is Race Prediction, Really?

Riegel's formula tends to be reasonably reliable for predicting races that aren't drastically different in distance from your known result — for example, predicting a 10K time from a recent 5K. Predictions become progressively less certain across very large distance jumps, such as projecting a full marathon from a 5K result, since factors like fueling strategy, mental endurance, and race-day pacing discipline become increasingly influential at longer distances in ways a pure mathematical formula can't capture.

⚠️ Treat race predictions as a useful training benchmark, not a guarantee — actual race-day conditions, weather, course terrain, and pacing strategy all meaningfully affect the real result.

Get your predicted race times

Enter one known result and see 5K to marathon predictions instantly.

Open Running Pace Calculator →

Worked Example

Known: 5K in 25:00 (1500 seconds)

10K prediction: 1500 × (10÷5)^1.06 = 52:07 Half Marathon: 1500 × (21.0975÷5)^1.06 = 1:55:00 Marathon: 1500 × (42.195÷5)^1.06 = 3:59:47

Notice the pace naturally slows across the predictions — the marathon prediction works out to roughly 5:41/km, noticeably slower than the 5:00/km pace of the original 5K, reflecting Riegel's built-in fatigue adjustment.

5 Pacing Tips for Race Day

1 — Don't start faster than your predicted pace

Starting too fast is one of the most common race-day mistakes — going out even 10-15 seconds per km faster than planned often leads to a significant slowdown later.

2 — Use your predicted time as a training benchmark, not a rigid promise

Weather, course elevation, and how you feel on the day all matter — treat the prediction as a useful reference point, not a fixed contract with yourself.

3 — Retest your known-distance time periodically

As fitness improves, your known race result becomes outdated — retest every few months for an updated, more accurate prediction.

4 — Longer-distance predictions need more caution

A 5K-to-marathon prediction has more uncertainty than a 5K-to-10K one — treat big distance jumps as a rough estimate, not a precise target.

5 — Factor in specific race-day training, not just raw pace

Longer races require dedicated endurance and fueling training beyond just running faster at shorter distances — pace alone doesn't guarantee marathon readiness.

Frequently Asked Questions

Divide your total time by the distance covered. Running 5km in 25 minutes gives a pace of 5 minutes per kilometer. A pace calculator does this automatically and converts between km and miles.

Commonly uses Riegel's formula: predicted time equals known time multiplied by the ratio of target to known distance, raised to the power of 1.06 — accounting for natural slowdown over longer distances.

Runners can't sustain 5K pace over a marathon due to fatigue and fueling demands. Riegel's 1.06 exponent builds in this natural slowdown compared to a straight linear projection.

Reasonably accurate for races not dramatically different in distance from a known result. Less reliable across very large distance jumps, like predicting a marathon from a very short race.

Pace expresses time to cover a fixed distance, like minutes per km. Speed expresses distance covered per unit time, like km per hour — the more common format for cycling.

Depends entirely on individual fitness and goals. Many beginner programs target a conversational pace, often around 7-9 minutes per kilometer, though this varies significantly by individual.