Running Pace Explained: What's a Good Pace, and How to Predict Your Race Time
What running pace means, how to read min/mile and min/km, real pace benchmarks by level and distance, and how race predictors work (and when they lie).
Ask ten runners what a “good pace” is and you’ll get ten answers — because the honest one is “good relative to your goal and your body.” But there are real benchmarks, and the math for turning your training pace into a race prediction is genuinely useful. Here’s both.
Pace vs. speed: the same thing, two directions
Pace is minutes per mile (or per kilometer): how long one unit of distance takes you. Speed is the inverse — miles per hour. Runners talk in pace because it maps directly onto the watch: run a 9:00/mile pace and you cross every mile marker at 9-minute intervals.
A few conversions worth knowing:
- 8:00/mile = 7.5 mph = 12.9 km/h (about 5:00/km)
- 10:00/mile = 6.0 mph = 9.7 km/h (about 6:13/km)
- 6:13/km = 10:00/mile — the crossover most treadmills won’t show you directly
So what IS a good pace?
For context, here’s where common paces sit:
| Pace (per mile) | Per km | What it looks like |
|---|---|---|
| 12:00+ | 7:27+ | Brisk walk / easy jog — completely normal for beginners |
| 10:00 | 6:13 | Typical recreational runner’s easy pace |
| 9:00 | 5:35 | Solid recreational pace; a common first-race effort |
| 8:00 | 4:58 | Competitive club runner on a long run; race pace for many |
| 7:00 | 4:21 | Fast amateur — sub-25 5K territory |
| 5:30 | 3:25 | Elite amateur racing; sub-3 marathon requires roughly this |
Two honest caveats:
- Age and sex adjust the “good” line. A 9:00/mile 10K at 60 years old is nationally competitive in some age groups. Use age-graded calculators for a fair comparison.
- Distance changes everything. A pace that feels conversational for one mile will end you over 26.2. Always read pace claims with the distance attached.
The rule that actually predicts race times
The most reliable piece of running math is Riegel’s formula, which predicts race times from a known performance:
T₂ = T₁ × (D₂ / D₁)^1.06
The exponent 1.06 captures the fact that humans fatigue non-linearly: doubling distance more than doubles time. Worked example — you ran a 5K in 25:00 and want to predict a marathon:
- Ratio: 42.195 / 5 = 8.439
- 8.439^1.06 ≈ 9.55
- 25:00 × 9.55 ≈ 3:58:45 — a sub-4 marathon, on paper
Predictions from common efforts:
| If you run a 5K in… | Predicted 10K | Predicted half | Predicted marathon |
|---|---|---|---|
| 30:00 | 1:02:15 | 2:18 | 4:47 |
| 25:00 | 51:53 | 1:55 | 3:59 |
| 20:00 | 41:31 | 1:32 | 3:11 |
Where predictions lie
Riegel assumes you’ve actually trained for the target distance. It fails in predictable ways:
- Predicting a marathon from a 5K you squeezed in during a busy week. The formula doesn’t know your long run maxed out at 8 miles. Reality will be 15–30+ minutes slower.
- Hot, hilly, or windy races. Pace calculators assume ideal conditions. Add roughly 1–2% per 5°F above ~55°F (13°C) for the heat tax.
- First-at-a-distance races. The formula is fitted on trained performances. For your first half or full marathon, treat the prediction as a ceiling, not a target.
The practical protocol: use the prediction as your optimistic goal, then set your race-day plan at prediction +5%, and adjust at the halfway point based on how it actually feels.
Turn training numbers into targets
Our calculator does the Riegel math for you, including the full prediction table for 5K/10K/half/marathon from any single measured effort:
If you think in treadmill speeds rather than pace, the Speed Calculator converts between mph, km/h, and pace in either direction — useful when a training plan says one thing and your treadmill displays another.