Tired but satisfied, a beginner finishes their first serious run. They stop the watch, and the dial lights up with "5:30". Anyone used to a car's speedometer or a bike computer instinctively looks for kilometers per hour — and doesn't find them. They start to wonder: is that a good result or a poor one, and why does the running world stubbornly count minutes per kilometer instead of ordinary speed? On top of that, the math seems upside down — a smaller number means a faster run, and the same seconds shaved off sometimes buy more speed, sometimes less.
The answer is not a coaches' whim. It follows from what a run actually is: the distance is fixed in advance — a loop in the park, five kilometers, a half marathon, the "royal" 42.195 km — so the only thing a runner really controls is the time needed to cover it. Pace, the time per unit of distance, states that directly, and it lets you ration your effort and estimate your finish on the fly. Speed answers the reverse question — which is why, in distance running, it fades into the background.
Time per distance, not distance per time
In physics, speed and pace are reciprocals. Speed is distance divided by time (V = d / t), usually expressed in kilometers per hour. Pace is time divided by distance (T = t / d), the running standard in minutes per kilometer. Because one is the inverse of the other, the higher the speed, the smaller the number describing the pace.
That is the whole apparent paradox. In the jargon, "dropping your pace" means speeding up, and chasing smaller numbers on the dial is the goal of every ambitious amateur. A run at 4:00 min/km is far faster and harder than one at 6:00 min/km, even though the "more means faster" intuition carried over from a speedometer suggests exactly the opposite. In the world of long distances, time is the currency and distance is the fixed matrix.
The rule of 60: converting pace to speed
The bridge between the two scales is surprisingly simple. Because in both cases the base is an hour of 60 minutes, and we measure distance in the same kilometers, one operation is enough:
V = 60 / T and T = 60 / V
Three round examples are worth memorizing as landmarks: a pace of 5:00 min/km is exactly 12 km/h, 6:00 min/km is an even 10 km/h, and 4:00 min/km is 15 km/h.
But a fractional trap lurks here, born of the base-60 way we write time. Seeing 5:30 min/km, a novice instinctively plugs 5.3 into the formula. That's wrong. Thirty seconds is half a minute — 0.5 in decimals — so the value is 5.5, not 5.3. The correct calculation is:
V = 60 / 5.5 ≈ 10.91 km/h
The reverse direction is just as tricky. A runner on a treadmill set to 11 km/h works out 60 / 11 ≈ 5.4545 minutes. The fractional part (0.4545 min) still has to be multiplied by 60 to get seconds: 0.4545 × 60 ≈ 27 s. So 11 km/h is a pace of 5:27 min/km — not some "5.45".
Why the conversion is nonlinear
Another myth holds that trimming your pace by a fixed amount always yields the same gain in speed. Not true — the relationship between pace and speed is a rational function, a hyperbola, so it is strongly nonlinear. Just compare two improvements of the same one minute per kilometer:
- A recreational runner drops from 6:00 to 5:00 min/km. Speed rises from 10 to 12 km/h — a gain of 2 km/h.
- An advanced athlete cuts from 4:00 to 3:00 min/km. Speed jumps from 15 all the way to 20 km/h — a gain of 5 km/h.
The same difference on the stopwatch (60 seconds per kilometer) therefore hides completely different mechanical work. It shows even on the finer steps that daily training is fought over. Going from 5:00 (12.00 km/h) to 4:30 min/km (13.33 km/h) requires adding 1.33 km/h. But the next 30 seconds, from 4:30 to 4:00 min/km (15.00 km/h), already means 1.67 km/h.
This nonlinearity has concrete physiological consequences. It explains why each additional second off a personal best costs more the faster the runner already is: every step toward a quicker pace means rising air resistance and greater oxygen demand — a steadily harder fight for running economy.
The mile nightmare
Things get more complicated racing abroad (New York, London) or reading foreign literature, where pace is given in minutes per mile. A statute mile is exactly 1609.344 meters, about 1.61 km. That is why a mile pace is numerically larger than a kilometer pace:
T(mile) = T(km) × 1.609344 and T(km) = T(mile) × 0.621371
Once again the trouble is mixing decimals with seconds. A pace of 5:00 min/km (5.0 in decimals) gives 5.0 × 1.609344 = 8.04672 min/mi; the fraction 0.04672 × 60 ≈ 2.8 s, so roughly 8:03 min/mi. A recreational 6:00 min/km is 6.0 × 1.609344 = 9.656 min/mi; 0.656 × 60 ≈ 39 s, so each mile in about 9:39. Without a watch or a ready-made table, doing this in your head on the course, with a tired marathoner's brain, can be a wall you cannot break through.
From a walk to the records
To tame these numbers, it helps to stretch them between the everyday and the limits of human ability. A brisk walk or race walk is usually around 10:00 min/km, i.e. 6 km/h — purely aerobic effort. A recreational runner most often moves near 6:00 min/km (10 km/h); this is the so-called conversational pace, at which you can talk freely and which, in most training schools, builds the aerobic base.
At the other end is the elite, for whom these values look beyond the reach of physiology. For years the symbol was Kelvin Kiptum's marathon world record — 2:00:35 from Chicago (2023), ratified by World Athletics; the runner died tragically in a car crash in February 2024. That time is an average speed of 20.99 km/h and a pace of 2:51 min/km. The mythical two-hour barrier, however, still resists in official, certified conditions — Eliud Kipchoge's famous 1:59:40 from the exhibition INEOS 1:59 run in Vienna (2019) does not count as a record, because it took place outside World Athletics rules: with a rotating team of pacemakers and a car projecting a laser line onto the road.
Among women, the fastest official time is 2:09:56 by Ruth Chepngetich from Chicago (13 October 2024) — the first woman in history to go under 2:10. That's an average of 19.48 km/h and a pace of 3:05 min/km.
At the opposite pole is the sprint. Usain Bolt's 100 m record from Berlin (2009) is 9.58 s, an average speed of 37.58 km/h and a pace of 1:36 min/km. Most fascinating, though, is that in the phase of maximum speed (between the 60th and 80th meters) biomechanical analyses showed an instantaneous value of 44.72 km/h — held for a whole kilometer, that would be a pace of 1:20.5 min/km. Of course it cannot be held: that is a speed sustained for a fraction of a race, not for hours.
The table below sets real running paces against speed, the mile conversion, and the marathon finish time at perfectly even pace.
| Pace (min/km) | Speed (km/h) | Pace (min/mi) | Marathon time (42.195 km) | Effort profile |
|---|---|---|---|---|
| 3:00 | 20.00 | 4:50 | 2:06:35 | World-record territory |
| 3:30 | 17.14 | 5:38 | 2:27:41 | Strong national elite |
| 4:00 | 15.00 | 6:26 | 2:48:47 | Very good amateur |
| 4:15 | 14.12 | 6:50 | 2:59:20 | The mythical 3-hour barrier |
| 4:30 | 13.33 | 7:15 | 3:09:53 | Well-trained amateur |
| 5:00 | 12.00 | 8:03 | 3:30:58 | Solid tempo run |
| 5:30 | 10.91 | 8:51 | 3:52:04 | Easy long run |
| 5:41 | 10.56 | 9:09 | 3:59:48 | The 4-hour marathon line |
| 6:00 | 10.00 | 9:39 | 4:13:10 | Typical recreational run |
| 7:00 | 8.57 | 11:16 | 4:55:22 | Slow recovery jog |
| 8:00 | 7.50 | 12:52 | 5:37:34 | Fast walk-run |
| 10:00 | 6.00 | 16:06 | 7:01:57 | Race walk / stroll |
Splits and the wall
The finish time follows directly from pace: time = pace × distance. Running an even 5:00 min/km through the whole marathon gives 5.0 × 42.195 = 210.975 minutes, i.e. 3:30:58. But how you distribute those minutes over the course decides between success and spectacular failure. Physiology distinguishes three strategies: the positive split (a slower second half), the even split, and the negative split (a faster second half).
Why do so many amateurs "hit the wall" in the second part of a marathon? It's muscle biochemistry. The main fuel at marathon intensity is glycogen stored in the muscles and liver, whose reserve in an average person is only about 1,800–2,000 kcal. At an aerobic, conversational pace the body burns fat and carbohydrate in a balanced way, sparing glycogen. But if the runner gets carried away and starts 5–10% too fast, the heart rate crosses the lactate threshold: carbohydrate use spikes, fat oxidation is blocked, and the rising concentration of lactate and hydrogen ions acidifies the muscles. The result is premature glycogen depletion around the 30th kilometer and a drastic slowdown.
That is why studies point to the negative split as the optimal strategy for long distances. Starting 5–10 seconds per kilometer slower than the target average gives the circulatory system a gentle warm-up, protects glycogen, and delays the buildup of metabolites. In the second half there's a psychological bonus: passing fading rivals lowers the perceived effort. Elite marathoners run exactly this way — controlling the first half, accelerating in the second.
Why your instantaneous GPS pace goes haywire
Many runners treat the watch as an oracle and panic when the "instantaneous pace" jumps by tens of seconds with no real change in their running. That is not a fault, but a limit of the technology itself. The watch does not measure speed directly (like a wheel-rotation sensor on a bike) — every second it tries to fix its position from satellite signals, and consumer-grade receivers have a natural margin of error (GPS drift) on the order of 3 meters.
Picture a runner at an even 5:00 min/km, covering 3.33 meters per second. If in one second the watch misplaces the position by 3 meters backward, and in the next by 3 meters forward, it will conclude the runner covered 9.33 meters in a second — and display a cosmic 33-plus km/h. To rein in this chaos, the software applies smoothing filters (e.g. a Kalman filter) and fusion with the accelerometer, but at the cost of a phase lag: after a sharp acceleration in intervals, the watch needs a dozen or so seconds before it shows the real pace. The situation is worsened by urban "canyons" bouncing the signal off glass facades, dense tree canopies damping the waves, and sparser sampling in power-saving modes, which cuts corners and falsifies the distance.
That is why experienced athletes don't watch instantaneous pace at all. Their key metric is lap pace, usually averaged over each full kilometer. Over a thousand meters the momentary positioning errors cancel out, and the reading becomes a precise navigational tool.
The 60-second rule
All this math comes down to a single trick, handy precisely when fatigue makes thinking hard. The product of speed (km/h) and the decimal value of pace (min/km) is always exactly 60. So just divide 60 by whatever you have: by the pace to get the speed, or by the speed to get the pace. By controlling lap pace, avoiding early acidosis, and remembering that in the world of long distances it's the smaller numbers that mean greater success, an amateur regains full control over training — and a safe road to steadily better personal bests.
Further reading
- Jack Daniels, Daniels' Running Formula (Human Kinetics) — the sport's worldwide "bible," with the author's VDOT system and training zones set by pace.
- Jerzy Skarżyński, Biegiem przez życie (6th ed., 2020) — the most complete Polish running compendium, emphasizing control of pace and heart rate.
- Timothy Noakes, Lore of Running (Human Kinetics) — a monumental scientific work: the biochemistry of fatigue, the central governor model, and the physiology of pacing.
- "Developing negative split pacing in endurance athletes" (Frontiers in Sports and Active Living) — a review of research and training models on pace distribution over long distances.