Learn more
Estimate average 5K running pace from finish time to guide training and race targets.
Use this 5K pace calculator to turn a total 5K finish time into a pace-per-kilometer benchmark for training or race review. The calculator is designed to give a fast answer, but the quality of the answer still depends on accurate inputs and a clear idea of what decision you are trying to support.
- Enter 5K distance, Hours, and Minutes using the same units you plan to compare or report.
- Add Seconds and review the inputs before calculating.
- Read the main pace per km first, then use the supporting outputs to understand the trade-offs behind that result.
- Compare your numbers with the worked examples below if you want a quick reasonableness check.
The displayed pace gives you a practical training number per kilometer and per mile, while average speed offers a broader intensity view. On this page, the primary output is pace per km.
Scenario 1: 5 km in 22 minutes and 45 seconds. Inputs used: distance: 5, hours: 0, minutes: 22, seconds: 45. Example result: 4:33 /km. This 5K finish time produces an average pace of 4:33 /km. Scenario 2: 5 km in 28 minutes and 10 seconds. Inputs used: distance: 5, hours: 0, minutes: 28, seconds: 10. Example result: 5:38 /km. For this steadier 5K effort, the pace works out to 5:38 /km.
Core formula: pace = total time / distance; speed = distance / total hours. The calculator converts your full session time into average pace per kilometer and per mile, then derives average speed in kilometers per hour.
- This is average pace across the whole activity, not split-by-split pacing.
- Short pauses inside the total time will slow the displayed pace unless you remove them first.
Use this calculator after a workout or race when you want to understand the average pace implied by your distance and finish time. Related paths for follow-up analysis include pace calculator, 10k pace calculator, running pace calculator, and marathon pace calculator.
Most bad outputs come from a few repeated input errors or interpretation mistakes. Use this short checklist before relying on the result.
- Including stop time when you actually want moving pace.
- Mixing miles and kilometers without checking the distance input carefully.
- Comparing pace across routes with very different elevation or terrain demands.
