Running Pace and Race-Time Prediction Explained

Pace calculation and race prediction are different

Pace calculation rearranges known time and distance values. If the inputs are fixed, the arithmetic has one answer. Race prediction begins with a known performance and applies an empirical model to estimate what an equivalent performance at another distance might be. That estimate is not a guaranteed result.

Difference between pace calculation, finish-time calculation, and race prediction

Task	Inputs	Output	Meaning
Pace calculation	Elapsed time and distance	Time per unit distance	Exact arithmetic for the entered values
Finish-time calculation	Pace and distance	Total elapsed time	Constant-average-pace arithmetic
Race prediction	Known race result and target distance	Estimated target time	Empirical comparison, with uncertainty

Pace basics: time, distance, pace, and speed

Elapsed time is the total duration. Distance is the length covered. Pace states how much time is used per unit of distance, such as minutes per kilometre or minutes per mile. Speed states how much distance is covered per unit of time, such as kilometres per hour.

Pace and speed describe the same average movement in reciprocal forms after the units are aligned. A lower time-per-distance pace is faster, while a higher distance-per-time speed is faster.

The pace formula

Pace = elapsed time / distance

Keep the time unit consistent through the division. Calzivo accepts a complete elapsed time and reports pace in minutes and seconds per kilometre or per mile.

Worked example: pace for 5 kilometres

Elapsed time = 25 minutes = 1,500 seconds
Distance = 5 km
Pace = 1,500 / 5 = 300 seconds per km
300 seconds = 5:00 per km

The result describes the average pace over the full distance. It does not say that every kilometre was completed in exactly five minutes.

Finish-time and distance calculations

When average pace and distance are known, multiply them to find a constant-pace finish time:

Finish time = pace x distance

Worked example: 10 kilometres at 5:00 per kilometre

Pace = 5 minutes per km
Distance = 10 km
Finish time = 5 x 10 = 50 minutes = 00:50:00

The same relationship can be rearranged to solve for distance:

Distance = elapsed time / pace

These calculations assume one constant average pace. They do not model stops, hills, changing speed, or fatigue.

Converting pace and speed

With pace expressed in minutes per unit and speed expressed in the same distance unit per hour, the reciprocal relationships are:

Speed per hour = 60 / pace in minutes per unit
Pace in minutes per unit = 60 / speed per hour

For example, 5:00 per kilometre is 5 minutes per kilometre, so the corresponding average speed is 60 / 5 = 12 kilometres per hour.

Distance units must also be converted. NIST lists one international mile as exactly 1.609344 kilometres. Therefore 5:00 per kilometre is about 8:03 per mile after conversion. Rounding can cause a one-second difference when a displayed pace is reused.

The Riegel-style race prediction used by Calzivo

The Race Predictor uses this fixed equation:

T2 = T1 x (D2 / D1)^1.06

• T1 is the known race time.
• D1 is the known race distance.
• D2 is the target race distance.
• T2 is the predicted target time.
• 1.06 is the exponent fixed by the Calzivo implementation.

The calculator converts mile and kilometre inputs to a common distance unit before applying the ratio, keeps full precision through the calculation, and rounds the final predicted time to the nearest second.

Worked example: 5K to 10K

Known time T1 = 25:00 = 1,500 seconds
Known distance D1 = 5 km
Target distance D2 = 10 km
T2 = 1,500 x (10 / 5)^1.06
T2 = 3,127.397... seconds
Rounded prediction = 00:52:07

This is slower than simply doubling 25 minutes. Because the exponent is greater than 1, predicted time grows slightly faster than distance as the target becomes longer. That is a property of the model, not a complete physiological explanation.

What the research supports

Peter S. Riegel's 1981 article described endurance performance with a power relationship of the form t = a x^b, where time changes with distance and the fitted constants depend on the activity or athlete group. The paper reported different fitted exponents rather than one universal value for every runner and distance. Calzivo uses 1.06 as a transparent, fixed Riegel-style exponent; the source should not be read as proving that 1.06 is exact for every athlete.

A 2016 study by Vickers and Vertosick analysed survey data from 2,303 recreational endurance runners. In their data, a commonly used Riegel comparison was reasonably calibrated through 10K and half marathon but performed poorly for marathon prediction. Their primary comparison used an exponent of 1.07, so it is evidence about the model family and its limitations rather than a direct validation of Calzivo's exact 1.06 setting. The study reported that predicted marathon times were at least 10 minutes too fast for about half of runners.

Why race predictions can differ from actual results

A race-time prediction holds many real conditions outside the equation. Uncertainty generally grows when the target distance is much longer or shorter than the known performance.

• Training and endurance may not transfer evenly to the target distance.
• Course profile, surface, elevation, weather, wind, and temperature may differ.
• Pacing, fatigue, fueling, hydration, injury, health, and recovery can affect an actual result.
• A short race can produce an optimistic marathon estimate for many recreational runners.
• The known result may not represent current fitness or comparable race conditions.

The output is a mathematical estimate for comparison and planning. It is not a training prescription, medical assessment, qualification guarantee, or promise that a target time is achievable.

When to use the Pace Calculator

Use the Pace Calculator when two of pace, elapsed time, and distance are known and you want the third. It is also useful for converting the result between per-kilometre and per-mile units. The finish-time mode assumes the selected average pace remains constant over the full distance.

When to use the Race Predictor

Use the Race Predictor when you have a completed race time and want one Riegel-style estimate at another distance. A recent source performance, similar conditions, and a target distance near the known distance may make the comparison more relevant, but none removes uncertainty.

Frequently asked questions