Use this time pace distance calculator to work out one missing value when you already know the other two. It is useful for running, cycling, walking, rowing, and other endurance activities where you want to estimate finish time, average pace, or distance covered.
The calculator also helps when you need to switch between pace and speed thinking. Some sports and training plans use min/km or min/mi, while others are tracked more naturally in km/h or mph. Use it for race planning, workouts, route estimates, and quick distance-time checks.
Input
Time Pace Distance Calculator FAQ
What does a time pace distance calculator do?
A time pace distance calculator solves one missing value from the other two. If you know time and distance, it can calculate pace. If you know time and pace, it can calculate distance. If you know distance and pace, it can estimate finish time.
Can I use this calculator for sports other than running?
Yes. It is useful for running, walking, cycling, rowing, and similar endurance activities. The key requirement is that you are working with average distance covered over time.
What is the difference between pace and speed?
Pace is usually expressed as time per unit of distance, such as min/km or min/mi. Speed is expressed as distance per unit of time, such as km/h or mph. They describe the same performance from two different angles.
How do you calculate pace from time and distance?
Average pace is calculated as time ÷ distance. For example, 1 hour over 12 km gives a pace of 5:00 per km. The same relationship can be rearranged to calculate distance or finish time.
Is this calculator suitable for race planning and training?
Yes. You can use it to estimate finish times, test target paces, compare route options, and check what a steady average effort means over a chosen distance. For structured training, it is most useful as a quick planning tool rather than a full workout prescription.
How accurate is the result?
The result is mathematically exact for the values entered, but real-world performance can differ because of terrain, wind, elevation, stops, drafting, fatigue, and pacing variation. Treat it as an average-performance estimate.
