Your average pace for a run hides critical information. A runner who ran 5K in 25 minutes at a steady 5 min/km and a runner who started at 4 min/km and crashed to 6 min/km both show the same average. Their fitness levels are very different.
The basic pace formula
Pace (min/km) = Total minutes / Distance (km)
Pace (min/mile) = Total minutes / Distance (miles)
Time = Pace * Distance
Distance = Time / Pace
These are simple division problems, but the time format requires care:
function calculatePace(totalSeconds, distanceKm) {
const paceSeconds = totalSeconds / distanceKm;
const minutes = Math.floor(paceSeconds / 60);
const seconds = Math.round(paceSeconds % 60);
return { minutes, seconds, display: `${minutes}:${String(seconds).padStart(2, '0')}` };
}
// 25 minutes for 5K
calculatePace(25 * 60, 5); // { minutes: 5, seconds: 0, display: "5:00" }
Negative splits
A negative split means running the second half faster than the first. This is the pacing strategy used by most elite marathon runners because it indicates good energy management.
Marathon world record pace:
First half: ~61:30
Second half: ~60:00
The negative split strategy works because starting conservatively preserves glycogen stores for the later kilometers when fatigue sets in.
Race pace equivalents
Your pace at different distances follows a predictable relationship. A common model is the Riegel formula:
T2 = T1 * (D2/D1)^1.06
If you run 5K in 25:00:
10K prediction: 25 * (10/5)^1.06 = 52:00
Half marathon: 25 * (21.1/5)^1.06 = 1:55:00
Marathon: 25 * (42.2/5)^1.06 = 4:02:00
The exponent 1.06 accounts for the fact that you slow down as distance increases. It is an empirical approximation, not a physical law.
For calculating pace, predicting race times, and planning split strategies, I built a calculator at zovo.one/free-tools/pace-calculator. It handles min/km and min/mile conversions and includes race time predictions.
I'm Michael Lip. I build free developer tools at zovo.one. 500+ tools, all private, all free.
Top comments (0)