跑步配速

Running pace as average speed inverted

Pace is how long it takes to cover a unit of distance—commonly minutes and seconds per kilometer. It is the reciprocal view of speed: slower pace numbers mean faster running. Race plans, interval workouts, and post-run analysis almost always speak in pace rather than kilometers per hour because split targets are easier to feel on the road.

Compute a completed session’s average with pace from time and distance. Project a finish clock from a known per-kilometer pace with predict finish time.

Core relationship

With distance in kilometers and time in seconds:

pace_seconds_per_km = total_time_seconds ÷ distance_km

finish_seconds = pace_seconds_per_km × distance_km

The two tools are inverses under constant-pace assumptions. Formats use mm:ss for pace and mm:ss or hh:mm:ss for longer totals.

Family of calculators

• Pace from time and distance — enter distance (km) and elapsed time; receive average pace per kilometer.
• Predict finish time — enter distance (km) and pace per kilometer; receive predicted finish as hh:mm:ss.

Example: 10 km in 50:00 → 5:00/km. Holding 5:00/km for a half marathon (21.0975 km) predicts roughly 1:45:29 if pace never changes.

Why average pace is not the whole story

GPS watches report moving time, elapsed time, and auto-pauses differently. Hills, wind, traffic lights, and aid-station stops inflate average pace relative to true running effort. Short calibration loops amplify GPS noise; long ultras hide huge pace variation behind one mean.

Use average pace for:

• Summarizing a completed flat road effort
• Setting treadmill belt targets
• Translating a goal finish into a round per-km number

Prefer split analysis, grade-adjusted pace, or power when terrain or strategy dominates.

Planning a race from a goal time

1. Choose a goal finish and race distance.
2. Divide to get even-pace targets (predict-finish inverted by hand, or use pace-from-time on the goal).
3. Decide whether you will negative-split, bank time, or run even.
4. Adjust the early kilometers if heat or hills make even pace unrealistic.

Constant-pace math is a sketch. Weather, nutrition, and packing errors still decide outcomes.

Units and formatting pitfalls

• Distance must be kilometers in these tools, not miles—convert first (1 mile ≈ 1.60934 km).
• 5:30 means five minutes thirty seconds, not 5.30 decimal minutes.
• Leading hours matter for marathons: 3:30:00 is not the same field as 30:00.
• Zero or negative distance/time is rejected; extremely short distances make tiny timing errors look huge in pace.

Training uses

Easy runs often sit at a conversational pace well slower than race pace. Threshold and interval sessions use faster targets for limited durations. Calculating average pace after a workout checks whether the session matched the plan; predicting finish time from a recent tempo pace is a rough forecasting exercise, not a guarantee.

Pair pace literacy with heart-rate or perceived-exertion education so athletes do not chase an aggressive number on a hot day.

Health disclaimer

Pace targets must match fitness, terrain, and health status. Increase volume and intensity gradually. Consult a sports-medicine or medical professional if you have cardiovascular risk factors, injuries, or abnormal symptoms during or after exercise. These calculators do not assess readiness to race.

Worked intuition

Doubling distance at the same pace doubles time. Speeding from 6:00/km to 5:00/km is a 16.7% pace improvement and cuts finish time by the same fraction under constant effort—harder than the percentage suggests because energy cost rises nonlinearly with speed. That is why small pace gains at the elite end require large training investments.

Limits of prediction

Predict-finish assumes you can hold the entered pace for the entire distance. Fatigue, glycogen, heat, and hills violate that assumption. A 5K pace rarely scales linearly to a marathon. Use recent race performances at similar distances, or established equivalent-performance tables, when forecasting seriously.

Summary

This hub covers two sides of constant-pace arithmetic: derive per-kilometer pace from distance and time, or project finish time from pace and distance. Master the inverse relationship, respect unit and format conventions, and treat outputs as flat-course averages—then layer physiology, course profile, and health judgment on top.