How This Calculation Works
The pace calculator divides your total time by distance to find your pace (minutes per km or mile). It also calculates speed in km/h or mph.
Race projections assume you can maintain the same pace over any distance — they multiply your per-kilometre pace by each race distance. This gives a useful baseline, but real-world performance slows over longer distances because of fatigue, fuelling needs, and the specific endurance that longer races demand. Treat the projections as optimistic starting points, especially for distances much longer than the one you entered.
Common Mistakes to Avoid
- Assuming training pace equals race pace. Most training plans include easy runs at a slower pace than race effort. Running every session at race intensity increases injury risk and can leave you fatigued on race day.
- Starting too fast. Going out faster than your target pace can feel easy early on, but it often leads to a significant slowdown in the second half of a race. Many coaches recommend starting at or slightly slower than your goal pace.
- Not accounting for terrain and conditions. Hills, heat, wind, altitude, and trail surfaces all affect pace. A flat-road pace is not directly comparable to a hilly or off-road effort.
- Converting minutes:seconds incorrectly. A pace of 5:30/km is 5 minutes and 30 seconds, which is 5.5 minutes — not 5.3 minutes. This matters when calculating finish times: 5.3 × 10 = 53 min, but 5.5 × 10 = 55 min.
Worked Example
Scenario: You ran 5 km in 25 minutes and want to know your pace, speed, and projected race times.
Step 1 — Pace: 25 min ÷ 5 km = 5:00/km. To convert: 5.00 × 1.609 ≈ 8:03/mile.
Step 2 — Speed: 5 km ÷ (25/60) hours = 12.0 km/h (7.5 mph).
Step 3 — Projected 10K: 5:00/km × 10 km = 50:00.
Step 4 — Projected half marathon: 5:00/km × 21.0975 km = 1:45:29.
Step 5 — Projected marathon: 5:00/km × 42.195 km = 3:30:59.
These projections assume constant pace. In practice, most runners slow over longer distances, so actual times will likely be longer.