Running Pace Calculator

Quick Tips for Getting the Most Out of This Calculator

Features

Three Numbers, One Relationship

Distance, time and pace are locked together by a single relationship — know any two and the third follows automatically, which is exactly why this calculator lets you solve for whichever one you're actually missing instead of forcing you to always enter the same two. Runners tend to ask three different questions depending on where they are in training: "if I run this pace, how long will it take?", "I have a time goal, what pace do I need to hold?", and occasionally "I ran for this long at this pace, how far did I actually go?" All three are the same equation rearranged, and switching between them here takes one click rather than reaching for a separate calculator or doing the division by hand mid-run.

How the Race Time Predictor Actually Works

Enter one known result — a recent 10K time, say — and turning on race predictions estimates what that same fitness would likely produce over 5K, the half marathon and the full marathon. The math behind it is Pete Riegel's formula, published in 1977 and still the most widely used race-time prediction method in recreational and competitive running alike: T2 = T1 × (D2/D1)^1.06. The exponent matters more than it looks — it reflects the simple fact that pace naturally slows over longer distances, so a straight-line scale-up from a 5K time would predict an unrealistically fast marathon. Riegel's 1.06 exponent, derived from analysing a large set of real race results across distances, captures that realistic slowdown reasonably well for most trained runners.

Why Splits Matter More Than the Finish Time Alone

A single average pace number hides a lot of useful detail, which is exactly why the split table below the calculator breaks the whole distance into individual kilometre or mile segments. Even pacing — running each split at close to the same time rather than starting fast and slowing down — is one of the most consistently repeated pieces of advice from experienced coaches and one of the most consistently ignored by runners caught up in race-day adrenaline. Having the actual target time for kilometre 8 or mile 15 written down in advance, rather than trying to do pace math mentally while tired, is a small planning step that measurably helps hold a smarter race.

Two Scenarios Worth Comparing

Someone with a goal marathon time of 4 hours needs to average 5:41 per kilometre, or 9:09 per mile, for the full 42.195 km — a number that sounds abstract until it's broken into 42 individual one-kilometre targets, each one checkable against a watch in real time rather than trusted to memory alone.

Someone who just ran a 10K in 48 minutes and wants to know if a sub-2-hour half marathon is realistic can enter that result and turn on race predictions: Riegel's formula suggests a half marathon finish around 1:47, comfortably inside the 2-hour goal, assuming training and conditions carry over reasonably well between the two efforts.

A third case: someone training on a treadmill set to 10 km/h wants to know what that actually means for an outdoor 10K. Solving for time at that pace over the 10K distance gives a direct answer — 1 hour flat — turning an abstract speed number into the same finish-time language used for every outdoor race, which is a far easier comparison than converting speed to pace mentally mid-workout.

Beyond Race Day: Using Pace for Training Too

A single race pace number is also a useful anchor for the training that leads up to it, even though this calculator doesn't hand out a full training-zone chart. Easy runs — the bulk of most training plans — are generally meant to sit noticeably slower than race pace, often by a minute or more per kilometre, specifically so they build aerobic fitness without adding fatigue that compromises the harder sessions. Tempo or threshold efforts sit closer to race pace, and short interval work is often run a little faster than it. Solving for pace against a goal race time first, then deliberately running most training slower than that number, is a simple mental model that avoids one of the most common beginner mistakes: running every training run at roughly the same, moderately hard effort, which tends to produce mediocre results in both directions rather than genuine improvement in either.

Who Actually Uses a Running Pace Calculator

• Anyone training for a specific goal time — the actual pace to hold, not a vague sense of "faster than last time."
• Runners deciding if a stretch goal is realistic — before committing months of training toward it.
• Coaches and training partners — planning group runs around a shared target pace.
• Treadmill runners — translating a speed setting into a pace and distance they can actually picture.

Once a pace target is set here, tracking the training load behind it pairs naturally with our Calorie Burn by Activity calculator for the energy cost of the sessions building toward it.

What Riegel's Formula Can't Predict

Race predictions assume your training, pacing strategy and race-day conditions transfer cleanly between distances, and that assumption gets weaker the further apart the two distances sit — a strong 5K result predicts a 10K reasonably well, but predicting a marathon from a 5K alone stretches the formula past where it was ever validated most reliably, since marathon performance depends heavily on long-run endurance and fuelling that a short, fast effort simply doesn't test. Weather, course terrain, altitude, and how well-rested you are on race day can all shift a real result well away from any formula's estimate in either direction. Treat every prediction here as a reasonable planning target to train toward, not a number your body owes you on race day regardless of preparation.

Frequently Asked Questions