Calculate your running pace and predict race finish times for other distances.
Fill in the fields on the left with your information, then press Calculate to see your result instantly. No sign-up required, and no data is sent anywhere — everything is calculated right in your browser.
Your running pace is simply your time divided by distance, but predicting how that pace translates to a different race distance isn't linear — fatigue scales non-linearly with distance. This calculator uses Riegel's formula, a well-established method among coaches and runners for predicting race times across distances based on a recent performance. Pace, speed, and finish time are three expressions of the same distance-time relationship, so knowing any two always lets you calculate the third. This calculator also predicts finish times for common race distances using established running formulas (like Riegel's) that account for pace naturally slowing over longer distances due to cumulative fatigue — an effect every runner experiences but that simple linear math would miss. Because race-time predictions assume reasonably specific training for the target distance, a runner who has only trained for shorter distances will likely find the predicted longer-distance time overly optimistic — the formula captures the general pace-fatigue relationship well, but it can't account for whether the underlying endurance has actually been built.
Pace, speed, and finish time are simply three ways of expressing the same underlying relationship between distance and time, which is why knowing any two of the three variables always lets you calculate the third. Runners typically think in "pace" (minutes per mile or per kilometer) rather than raw speed (miles or kilometers per hour) because pace maps more intuitively onto how training and racing actually feel — "I need to hold 8-minute miles" is more directly useful for pacing a run than "I need to average 7.5 mph."
Race pacing strategy is one of the main practical uses for this kind of calculator, since even pacing — running each mile or kilometer at roughly the same pace throughout a race — is generally considered more efficient than an uneven pace, even when the average speed is identical. This is because physiological research on fatigue and energy substrate use shows that starting too fast burns through glycogen stores and builds excess lactate earlier than necessary, making it harder to sustain pace in the race's second half — commonly referred to among runners as "hitting the wall," most often around the 20-mile mark in marathons specifically because glycogen depletion tends to occur around that distance for most runners.
Training pace calculations serve a different purpose: structured training plans typically prescribe different paces for different workout types — easy runs at a conversational, low-intensity pace to build aerobic base without excessive fatigue, tempo runs at a comfortably hard, sustained pace to improve lactate threshold, and interval work at faster-than-race pace to improve VO2 max and running economy — and calculating these training zones accurately from a recent race time or time trial is a standard part of most evidence-based training methodologies, rather than guessing paces by feel alone.
Because endurance and fatigue don't scale linearly — running twice as far takes more than twice the time for most runners.
It gives a rough estimate, but accuracy drops for large distance jumps — predicting a marathon from just a 5K assumes endurance that hasn't actually been tested yet at that much longer distance.
It's quite reliable for similar distances (e.g., 5K to 10K) but less precise for very different distances like 5K to marathon.