What this running pace calculator does
The calculator solves either direction of the same relationship: time divided by distance equals pace, while pace multiplied by distance equals finish time. It then converts the result between kilometers and miles, builds cumulative splits, and estimates equivalent performances at common race distances.
Pace arithmetic is exact for the inputs you provide. The race-time predictions and training anchors are not. Those sections use models and assumptions that cannot know your endurance, course, weather, pacing, fueling, health, or preparation for a different distance.
Worked example: pace from finish time
Suppose you run 5 kilometers in 25:00. Convert the time to 1,500 seconds and divide by 5. The result is 300 seconds per kilometer, or 5:00/km. Convert that pace to miles by multiplying by 1.609344: about 483 seconds, or 8:03/mi.
The cumulative kilometer splits are 5:00, 10:00, 15:00, 20:00, and 25:00. The calculator carries full-precision seconds internally and rounds the displayed totals once, which prevents a long split table from drifting away from the entered finish time.
Worked example: finish time from target pace
A half marathon is 21.0975 kilometers. At 5:30 per kilometer, the calculation is 330 seconds × 21.0975 = 6,962 seconds, which rounds to 1:56:02. Real races rarely follow perfectly even splits: hills, wind, congestion, aid stations, and turns all change short-term pace. Treat the average as a planning target rather than an instruction to fight the course every kilometer.
How the Riegel race-time estimate works
The prediction table uses Peter Riegel's power model:T₂ = T₁ × (D₂ ÷ D₁)^1.06. T₁ and D₁ are the known time and distance; T₂ and D₂ are the target. The exponent above 1 represents the average slowing that occurs as distance increases. Riegel derived the relationship from competitive performance records, so 1.06 is a fitted population value—not a physiological constant unique to you.
A nearby prediction, such as 5K to 10K, asks less of the model than a 1-mile result projected to a marathon. The calculator labels each target as a closer, wider, or very wide extrapolation based only on distance ratio. That label describes how far the formula is stretching; it is not a confidence interval or promised accuracy.
Why predictions miss
- Specific preparation: a fast 5K does not prove marathon durability or fueling practice.
- Input effort: a tempo run entered as if it were a race understates current ability.
- Course and conditions: heat, wind, elevation, surface, and turns change the cost.
- Pacing: starting too fast can make the same fitness produce a slower result.
- Distance error: GPS, track lane, and poor tangent choices can change measured distance.
Use a recent, near-maximal result on a measured course. Prefer a source distance close to the target and use the estimate as a starting point for race-specific training. If your long-run and threshold sessions cannot support the predicted pace, believe the training evidence.
What the training pace anchors mean
The four pace rows are illustrative anchors derived from the same race-equivalency model. Threshold is modeled as an approximately one-hour race pace, interval pace from an equivalent 3K, and the easy range as 20–40% slower than modeled threshold pace. They are not lactate-test results, ventilatory thresholds, or individualized coaching.
For easy running, conversation should stay comfortable. Compare that cue with the Zone 2 heart-rate calculator rather than forcing a number when heat or fatigue raises effort. To track aerobic capacity with a repeatable protocol, see the VO₂ max field-test calculator.
Using splits on race day
Cumulative splits are usually easier to audit than isolated lap pace. If the 10K cumulative target is 50:00 and your watch reads 50:20, you know the total gap without adding ten noisy kilometers. For an officially measured road race, use the course markers as the primary distance reference; a watch often records long because of GPS error and imperfect tangents.
The Copy, Download, and Print/PDF controls package the active inputs, pace, predicted times, cumulative splits, and method caveat into a portable report. The downloaded file is plain text and contains no account data.
