Running Pace, Race Prediction, and the Riegel Formula
Why pace is the inverse of speed, how to predict marathon times from a 5K, and the pacing strategies that win races
1. What Is Pace, Exactly?
Pace is the inverse of speed: time per unit distance instead of distance per unit time. Runners express pace as minutes per mile (min/mi) or minutes per kilometer (min/km). A runner covering 5K in 25:00 has a pace of 5:00/km. The same runner has a pace of 8:02/mi.
Speed (units/sec) = Distance ÷ Time
Pace = 1 ÷ Speed (with unit conversion)
A faster pace is a lower number. 4:30/km is faster than 5:30/km. Most running watches display pace in real time and alert you when you deviate from a target pace. Training plans prescribe pace ranges for different workout types — easy runs, tempo, intervals, long runs.
2. The Riegel Formula for Race Prediction
Pete Riegel published the formula in 1977 after analyzing race results from 1935 onward. It models the relationship between distance and time as a power-law curve:
Where T is finish time and D is distance. The exponent 1.06 captures the empirical observation that running speed drops slightly as distance increases — not just because of fatigue, but because of the disproportionate energy cost of sustaining faster paces over longer durations.
Accuracy: Riegel predicts within ~2-3% for trained runners across similar conditions. Marathon predictions from a 5K time tend to be optimistic by 5-10% because marathon pace is more affected by fueling, heat, and pacing strategy than shorter races. Reverse predictions (5K from a marathon time) are usually more accurate.
3. Why Riegel Works (and When It Doesn't)
The 1.06 exponent captures three physiological realities:
- Glycogen depletion — fast paces burn glycogen quickly; sustained fast pace is impossible past ~90 minutes for most runners
- Form economy — biomechanics change at slower paces. Higher cadence is metabolically cheaper but harder to maintain
- VO₂ max vs lactate threshold — short races are VO₂ max-limited, long races are lactate threshold-limited. Different physiological ceilings
Riegel fails when these conditions change dramatically — for example, predicting a 5K time for an ultramarathon-trained runner (they will be undertrained for short-distance speed) or vice versa. It also fails across very different conditions (heat vs cool, hilly vs flat). Use predictions within ±5% for sanity-checking, ±10% as a stretch goal.
4. Training Zones by Pace
Zone 1 — Recovery
Very easy, conversational pace. 65-70% of max pace. Use for warm-up, cool-down, and recovery days between hard sessions.
Zone 2 — Easy / Long Run
Aerobic base pace. 70-78% of max pace. Builds mitochondrial density, fat oxidation, capillary networks. 70-80% of weekly mileage should be here.
Zone 3 — Marathon / Tempo
Sustained race pace. 80-88% of max pace. Lactate threshold work improves the body's ability to clear lactate.
Zone 4 — Threshold
Comfortably hard, ~25-40 minute effort. 88-92% of max pace. Tempo runs, cruise intervals.
Zone 5 — VO2 Max Intervals
Hard interval pace, ~3-8 minute repeats. 95-105% of max pace. Builds aerobic ceiling.
Zone 6 — Anaerobic / Sprint
Short, fast efforts (200m-400m). Track workouts, hill sprints. Develops neuromuscular speed and form.
The 80/20 rule applies: 80% of weekly mileage should be easy (Zones 1-2), 20% hard (Zones 3-5). Most amateur runners run too much at moderate intensity and not enough truly easy. Easy days should feel embarrassingly slow — that's how they should feel.
5. Pacing Strategies for Race Day
- Negative splits: run the second half faster than the first. The gold standard. Target 1-3% negative split. Conservative opening, finish strong
- Even splits: hold the same pace throughout. Easier to execute than negative splits. Works well for shorter races (5K-10K) and even-paced courses
- Positive splits: run the second half slower. Almost always a sign of going out too fast. Avoid at all costs
- Surge tactics: in races with tactical positioning, surges on hills or at mile markers can break competitors. Risky; requires fitness buffer
- Banking time: deliberately running faster than goal pace early to "save" time for later. This is a myth — you cannot bank time, you only burn glycogen faster
For your first race at a distance, target 5-10 seconds per mile slower than goal pace for the first mile, then settle into goal pace. The opening mile adrenaline always feels easier than it is; resist it.
6. Tapering for Peak Performance
A taper reduces training stress to allow fitness to express itself. The body needs 2-3 weeks to fully recover from accumulated training load:
- Marathon taper: 3 weeks. Volume drops 40% (week 1), 60% (week 2), 70-80% (week 3). Keep 1-2 short intensity sessions (e.g. 6×1km at marathon pace) to stay sharp
- Half marathon taper: 2 weeks. Volume drops 30% (week 1), 50-60% (week 2). Keep one threshold session mid-taper
- 5K/10K taper: 5-7 days. Volume drops 30% (first half), 50% (final 3 days). Keep one short VO2 max session 5-6 days out
Taper madness is real — runners feel sluggish, slow, heavy, and convinced they have lost fitness. They have not. Fitness gains from the taper are stored in muscle glycogen, enzyme activity, and CNS recovery. Trust the taper. The race will reveal the result.
7. Elevation and Course Profile
Hills slow runners. The standard rule of thumb for races:
- Net uphill: add 12-15 seconds per mile per 100 ft of climb (or +12 sec per km per 100m)
- Net downhill: faster in real time, but eccentric muscle damage accumulates. Often a wash on race day
- Rolling hills: nearly equivalent to flat for trained runners at moderate paces. Becomes significant at faster paces
- Boston-qualifying hills: the Newton hills at Boston are net negative overall, but the timing comes from the descent into the city. The ToolWise elevation field uses a +12 sec per 100m penalty as a conservative default
8. Goal Setting and Progression
Realistic race time goals follow the principle of incremental improvement. Annual PR targets:
- Beginner (first year running): 15-25% improvement over starting fitness
- Intermediate (2-3 years): 5-10% improvement
- Advanced (5+ years): 2-4% improvement
- Elite: 1-2% improvement, sometimes less
To achieve these gains, build weekly mileage gradually (max 10% increase per week, with a down-week every 4th week). Include two quality sessions per week (intervals and tempo). Long run should be 25-35% of weekly mileage. Sleep 8+ hours. Eat enough to support the training load — most amateur runners under-fuel.
9. Hydration and Fueling for Long Runs
Under 60 minutes
Water only. Body has enough glycogen for ~60-90 minutes of moderate-intensity running.
60-90 minutes
30-60g carbs per hour. Sports drink or one gel every 30-45 minutes.
90+ minutes
60-90g carbs per hour from multiple sources (glucose + fructose for max absorption). Practice on training runs.
Marathon
60-90g carbs per hour starting in the first hour. Sip water at every aid station. Electrolytes (sodium especially) for hot conditions.
Under-fueling is the #1 cause of the late-race wall. The body holds 400-500g of glycogen, enough for ~90-120 minutes of hard running. Beyond that, exogenous carbs become essential. Most runners underestimate their needs by 30-50%. Practice fueling strategy on long training runs — never try anything new on race day.
10. Privacy for Training Data
Browser-Only Computation
ToolWise's Pace Calculator runs entirely in your browser. Your distance, time, pace, elevation, splits, and race predictions never touch our servers or get logged by analytics. Running data reveals patterns about location, schedule, and personal performance — keep it private.
Conclusion
Pace is the universal currency of running. The ToolWise Pace Calculator computes your pace per mile or kilometer from any distance+time combination (or reverse-calculates time from pace+distance), predicts race times across 5K through marathon using the Riegel formula, accounts for elevation, and produces split times. Pair it with consistent easy mileage, two quality sessions per week, and a proper taper — your PRs will follow.