Race Time Calculator Predictor
A race time predictor takes a result from one distance and extrapolates your likely finish time at another. The math sounds simple, but there are two meaningfully different ways to do it, and the choice between them can shift your marathon goal by several minutes in ways that affect your entire pacing strategy.
The Two Main Formulas
Riegel’s Equation
Most online race time predictors still use the formula Peter Riegel published in 1981:
T2 = T1 × (D2/D1)^1.06
T1 is your known time, D1 is that distance, D2 is the target distance, and T2 is the predicted finish time. The exponent 1.06 captures the well-documented reality that pace slows as race distance increases, fitted to competitive race data from the 1970s.
The formula is fast to compute and works reasonably well for similar distances: 5K to 10K, or 10K to half marathon. The known weakness is at the marathon and beyond. The 1.06 exponent is a population average, and it tends to produce optimistic marathon predictions for recreational runners who haven’t done the specific training required to sustain that effort for multiple hours.
VDOT-Based Prediction
Jack Daniels’ VDOT system works from a different starting point. Rather than scaling time geometrically, it uses your race result to estimate your aerobic capacity expressed as a VO2 max equivalent. That VDOT value then maps to expected finish times at other distances using performance curves calibrated against real race data across a range of distances and ability levels.
The practical difference shows up most at longer distances. VDOT produces more conservative marathon predictions for the same input because the underlying model accounts for the increasing physiological demands of sustaining aerobic effort for multiple hours. For 5K to 10K, the two methods are close. Past the half marathon, VDOT tends to be the better-calibrated choice. The race time predictor overview goes deeper on the practical differences between the two formulas across all distances.
Pacesmith’s Race Time Predictor uses the VDOT formula rather than Riegel, which matters specifically when you’re using a 5K or 10K result to set a marathon goal.
What Makes a Prediction More or Less Reliable
The formula you use matters, but the quality of the input matters just as much.
Recency. A race from eight months ago won’t reflect your current fitness if you’ve had an injury since, or if you’ve added a meaningful training block. Most predictors assume the input time represents your current ceiling. If it doesn’t, the output won’t either.
Distance gap between input and target. Predicting a half marathon from a 10K is reliable because the physiological demands overlap significantly. Predicting a marathon from a 1-mile time compresses a huge amount of physiology into a single data point. The further the distance gap, the more room for error.
Conditions in the input race. A 10K PR on a flat certified course in cool weather is a cleaner fitness signal than a 10K run on a hilly loop in 80-degree heat. Calculators accept a time and a distance; they can’t see course profile or weather. If your input race was slower than your actual fitness due to conditions, the prediction will be conservative. If you ran a PR on unusually ideal terrain, the prediction might be slightly aggressive.
Training specificity. Two runners with identical VDOT scores can have very different marathon performances if one has been averaging 50-mile weeks with 20-mile long runs and the other has been focused on track distances. The formula captures aerobic capacity. It doesn’t capture fat oxidation efficiency or the metabolic adaptations that come from sustained marathon-paced long runs. The training pace calculator guide covers how to translate a VDOT score into the specific paces that build those adaptations.
Predictions by Distance
800m
At 800m, race prediction formulas are operating outside their calibration range. The 800m is roughly half aerobic and half anaerobic; both Riegel and VDOT are built for fully aerobic events. Predicting 800m performance from a 5K or 10K input tends to underestimate what a trained middle-distance runner can actually run. Use any 800m prediction as a rough reference point, not a race target.
Half Marathon
The half marathon is the most reliable distance for prediction tools. It’s long enough to be fully aerobic, short enough that glycogen depletion rarely becomes decisive, and the 10K is a close enough input distance to provide a clean fitness signal. A VDOT-based race time predictor for the half marathon, fed with a recent 10K result, typically lands within 1-2% of a well-executed race.
Marathon
More predictions go wrong here than anywhere else. Glycogen depletion after mile 20, fat oxidation capacity, and the specific adaptations built through sustained long runs all affect marathon performance in ways a single race result can’t fully capture. VDOT predictions are more conservative than Riegel at this distance, and that conservatism is appropriate. First-time marathoners who haven’t consistently trained above 18-20 miles should treat any prediction as an optimistic ceiling, not a forecast.
Garmin and Device-Based Predictions
Garmin’s race predictor estimates VO2 max continuously from heart rate and pace data during training runs, then maps that number to predicted finish times at standard distances. The concept is similar to VDOT: estimate aerobic capacity, translate it to performance. The execution differs because the input is aggregated training data rather than a race result.
The advantage is that the estimate updates without requiring you to race. The limitation is that training data is noisier than race data. A string of easy recovery runs in hot weather can drag the estimate down. A race result, where you were pushing close to your actual ceiling, is a harder and more reliable signal. The VO2 max race time predictor guide breaks down where watch-derived numbers go wrong and how lab and race-derived VO2 max compare.
A practical approach: use Garmin as a fitness trend indicator across a training cycle, then run a proper VDOT calculation after a real race to set a specific goal. The VDOT Calculator gives you your full score and training zone paces from any race result, which is a more concrete foundation than a watch-derived estimate.
When You Don’t Have a Recent Race Result
If your last race was months ago, a controlled time trial on a measured course gives a usable proxy. A 5K at genuine race effort, paced properly from the start rather than run as a hard tempo, will give you a reliable VDOT input. Some coaches use a 3K hard effort and convert it to an estimated 5K equivalent, but solo time trials are harder to pace than competitive races, so the signal is noisier.
The cleaner option: add a tuneup race four to six weeks before your goal event. Even a small local 5K or 10K gives you a data point that reflects current fitness and how your body responds to competition. The prediction you build from that result will be significantly more trustworthy than anything estimated from workouts.
Turning a Prediction Into a Race Strategy
A predicted finish time is only useful once it’s translated into per-mile splits for your specific course. A 1:52 half marathon goal means something different on a flat point-to-point than on a course with a 200-foot climb in miles eight through ten.
Even-pace running is a reasonable default on flat courses. On courses with significant elevation, even-effort pacing makes more practical sense: slower splits on the climbs, slightly faster on descents and flat sections. Either way, the strategy needs to be decided before the race, not invented after mile 3.
The Race Split Planner generates a complete mile-by-mile or km-by-km table from a goal time. You can print it and take it to the start line, which is the step that converts a predicted time from a number you know into a plan you can actually run.
Pacesmith’s Race Time Predictor runs the VDOT calculation and connects directly to the split planner, so you can go from a recent race result to a per-mile race plan in a few minutes, with no account or subscription required.