Running pace, explained
Pace is minutes per kilometer. Everything in running, from easy runs to race predictions, hangs off that one number.
Runners talk in pace, not speed. Nobody at a start line says, "I run at 12 kilometers per hour." They say "I run at 5:00 per km." Pace is simply how many minutes it takes you to cover one kilometer, and almost everything in training hangs off that one number.
The basic conversion
Pace and speed are the same fact stated differently. 5:00 per km is 12 km/h. 6:00 per km is 10 km/h. 4:00 per km is 15 km/h. The formula is 60 divided by your pace in minutes. But pace is what runners use because races are measured in kilometers, and your watch shows pace live while you run.
Two paces worth memorizing. A 3:30 marathon needs 4:58 per km. A 4:00 marathon needs 5:41 per km. A 5:00 marathon needs 7:06 per km. If you know your goal time, you know your required pace. If you know your pace, you know your finish time. That is the whole calculator.
Easy, tempo, and race pace are different gears
Most running injuries and most bad races come from running every run at the same effort. Training has gears, and pace is how you tell them apart.
Easy pace is the gear you spend most of your week in. You can talk in full sentences. It feels almost too slow, and that is the point. Easy runs build the base that makes everything else possible. A common mistake is running easy days too fast, which leaves nothing for the hard days. My own plan caps easy runs at a heart rate of 150, and the runs where I ignored that cap are the ones that felt worst the next day.
Tempo pace is comfortably hard. You can speak in short phrases, not sentences. It is roughly the pace you could hold for an hour in a race. Tempo runs teach your body to clear lactate while still running, which is what lets you hold pace late in a race.
Race pace is the pace of your target event. A marathon pace session is not a test of fitness. It is practise at the exact effort you will hold for hours, including your fueling at that effort.
Interval pace is faster than race pace, in short bursts with rest between. It builds speed and running economy. It is also where most beginners get hurt, because they run intervals far too fast. Interval pace should feel controlled, not desperate.
How to find your easy pace
Forget formulas for a minute. Go for a run and talk. If you can chat comfortably, you are at easy pace. If you are gasping out single words, you are too fast. That talk test is more useful than any chart, because it adjusts to heat, hills, sleep, and how yesterday went.
As a rough starting point, easy pace is usually 60 to 90 seconds per km slower than your 10K race pace. If you race 10K at 5:00 per km, your easy runs probably live around 6:00 to 6:30 per km. If that feels embarrassingly slow, it is working.
Predicting a race time from another race
This is where pace gets fun. If you ran 10K in 55 minutes, what would you run for a half marathon? The most used method is the Riegel formula, which assumes your pace slows predictably as distance grows predicted time equals your known time multiplied by the distance ratio raised to 1.06.
Worked out: 55 minutes times (21.1 divided by 10) to the power of 1.06. That ratio is 2.11, raised to 1.06 is about 2.23, and 55 times 2.23 is about 123 minutes. So a 55-minute 10K predicts roughly a 2:03 half marathon, assuming similar training and conditions.
It is an estimate, not a promise. Heat, hills, a bad night of sleep, or a fitness change since your reference race will move it. Treat predictions as a planning tool: they tell you what pace to train at, and what to aim for on the day. They do not guarantee anything.
Pace in Indian conditions
One honest note. Pace targets written for cool weather do not transfer directly to a humid Indian morning. Heat slows everyone down, sometimes by 20 to 30 seconds per km on a bad day. If your plan says 5:00 per km and it is 28 degrees with humidity, the same effort might produce 5:20. That is not lost fitness. That is weather. Adjust the pace, keep the effort, and judge the run by heart rate and feel, not by the number on the watch.
How to use this
Three things to do with pace from here. One, find your easy pace with the talk test and protect it. Two, use the pace calculator to turn any goal time into a required pace, and check that pace against your recent training. Three, use the race time predictor to set a realistic target from a race you have actually run, not from a race you wish you had run.
Pace feels abstract until you tie it to a race. Once you do, it becomes the simplest tool in running: one number that tells you how to train, what to aim for, and whether you are ready.
Plan Your Training with Runner Calculators
Calculate training paces, custom negative split strategy, and benchmark finish times with RunRadar's free, client-side tools: