Running Pace Calculator

One run in every common pace format

Enter a distance and elapsed time. The calculator shows minutes per kilometer, minutes per mile, kilometers per hour and miles per hour together, then extends that exact pace over standard race distances.

Everything is direct distance-and-time arithmetic. No fitness level, age or personal data is required.

Pace and speed are inverses

Pace answers “how long does one kilometer or mile take?”

pace = elapsed time ÷ distance

Speed answers “how much distance is covered in one hour?”

speed = distance ÷ elapsed time

A 25-minute 5K is exactly 5:00 per kilometer and 12 km/h. Converted with one mile equal to 1.609344 kilometers, the same run is about 8:03 per mile and 7.46 mph.

Elapsed time versus moving time

For a race, use the official elapsed time from start to finish. It includes every slow section and stop because the clock did not stop.

For a training run, a watch may report moving time after removing traffic lights or other pauses. That can be useful for examining pace while running, but it is not comparable with an elapsed race result unless the distinction is kept clear.

What the race table means

The table multiplies the calculated seconds per kilometer by 5K, 10K, half-marathon and marathon distance. It answers questions such as “what finish time is 6:00 per kilometer over 10K?”

It does not answer “if I ran this 5K, what marathon can I run?” Holding one pace over a much longer distance requires different endurance, fueling and training. A realistic race predictor needs a performance model and recent results, not simple pace multiplication.

Why devices disagree

A pace calculation can only be as accurate as its distance and time. GPS tracks can cut corners, wander beside a route, or lose accuracy near buildings and trees. A measured race course and chip time provide better inputs than a casual phone trace.

Instantaneous GPS pace is especially noisy because it divides a short, uncertain distance by a short time. Average pace over a complete lap or run is much more stable.

Pace is not effort

Two runs at the same pace can demand different effort because of hills, wind, heat, altitude, surface, fatigue and carried load. The calculator makes no grade or weather adjustment.

Use pace as one description of what happened, alongside effort and conditions. Stop exercise and seek appropriate care for chest pain, faintness or other concerning symptoms rather than trying to maintain a calculated number.

Frequently asked questions

How is running pace calculated?

Elapsed time is divided by distance. A 25-minute 5K is 5:00 per kilometer. The same pace converts to about 8:03 per mile.

What is the difference between pace and speed?

Pace is time required per unit of distance, such as 5:00 per kilometer. Speed is distance covered per unit of time, such as 12 km/h. Faster running means a lower pace number and a higher speed number.

How are kilometers converted to miles?

One mile is exactly 1.609344 kilometers. The calculator converts the completed distance before dividing the time, so both pace forms describe the same run.

Are the race-time projections predictions?

No. They simply extend the same pace over another distance. A pace sustainable for 5K is normally too fast for a marathon, so the table is useful arithmetic rather than a performance forecast.

Why did my GPS pace differ from the calculator?

GPS distance can drift through turns, tree cover, buildings and sampling error. Auto-pause, elapsed versus moving time, and a non-certified route can also change the inputs.

Should I use elapsed time or moving time?

Use elapsed time for a race result and moving time when analyzing pace only while in motion. State which one you used when comparing runs.

Does elevation affect equivalent pace?

Yes, but this calculator does not adjust for it. Hills, surface, wind, heat and altitude all change the effort required for the same displayed pace.