🏃 Pace Calculator

Solve for pace, time or distance, compute checkpoint-to-checkpoint splits, convert between 8 pace/speed units, or project your finish time mid-race — four tools in one, metric and imperial.

🏃 Pace Calculator
hhmmss
📈 Results
Pace
Distance
Total Time
Pace /km
Pace /mi
Speed

Splits

KmSplitCumulative

🔮 Predicted Race Times

Km Splits
Predicted Race Times
This result is for informational purposes only and is not a medical diagnosis. Pace, split, and finish-time projections are mathematical estimates based on your inputs, not a guarantee of race-day performance — actual results vary with fitness, terrain, weather, and pacing strategy.
🏃

Enter your details to calculate pace

Guide

About the Pace Calculator

Last updated: July 2026 · Reviewed by the NeftCal editorial team

This pace calculator is a four-in-one running toolkit that doubles as a running pace calculator, race pace calculator, marathon pace calculator, and 5K pace calculator all in one place: solve for pace, time, or distance from the other two; break a race into checkpoint splits with the multipoint pace calculator tab; convert a pace or speed value between 8 different units with the built-in pace converter; and project a finish time mid-run with the finish time calculator. It's built for runners planning race strategy, tracking training paces, or converting a treadmill speed into a familiar min per km or min per mile pace.

What It Measures

Pace is the time it takes to cover a fixed distance — usually expressed in minutes and seconds per kilometer or per mile — while speed measures how far you travel in a fixed time (km/h or mph). This calculator's core engine applies pace = time ÷ distance and its algebraic rearrangements to solve for whichever value you're missing, then layers on splits, unit conversions, and race-time predictions built from that same core relationship.

Who Should Use This Calculator

This tool is designed for recreational and competitive runners, run coaches, and anyone training for a 5K, 10K, half marathon, or marathon. It's equally useful for a beginner converting a treadmill's mph display into a familiar pace, and for an experienced racer planning even splits and a target finish time ahead of race day.

Why It Matters

Pacing well is one of the biggest controllable factors in race performance — starting too fast is one of the most common ways runners fade late. Splits and finish-time projections let you check whether you're on pace mid-race, while the pace converter and Riegel predictions help translate a known performance (say, a 5K time) into a pacing plan for a different distance or a different unit system.

Real-World Applications

  • Planning even splits for an upcoming 5K, 10K, half marathon, or marathon
  • Converting a treadmill speed display (mph or km/h) into a familiar race pace
  • Checking your progress against goal pace using the Finish Time tool mid-run
  • Analyzing checkpoint splits from a GPS watch or race timing mats with the Multipoint tool
  • Pairing with NeftCal's Target Heart Rate Calculator and TDEE Calculator to round out a training and fueling plan

Tips for Accurate Results

  • Even splits (holding a constant pace) are generally the most efficient race strategy — use the splits table to plan checkpoints in advance
  • Enter elapsed and checkpoint times as precisely as you can (hh:mm:ss) since small timing errors compound over a full split table
  • Riegel-formula predictions are most reliable for distances reasonably close to your input — treat marathon predictions from a 1-mile time with caution
  • Use the distance presets (5K, 10K, Half, Marathon, etc.) to avoid manual unit-conversion mistakes on standard race distances
  • If you train in one unit system and race in another, use the Pace Converter to check your min/km and min/mile readings match before race day
Formula

The Pace and Race-Prediction Formulas Explained

How each of this calculator's four tools computes its results

Core Pace Formulas
Pace (sec/km) = Total Time (sec) ÷ Distance (km)
Time (sec) = Pace (sec/km) × Distance (km)
Distance (km) = Total Time (sec) ÷ Pace (sec/km)
Speed (km/h) = 3600 ÷ Pace (sec/km)

Riegel Race-Time Prediction Formula
T2 = T1 × (D2 ÷ D1)1.06

Finish Time Formula (linear projection)
Current Pace = Elapsed Time ÷ Distance Covered So Far
Predicted Finish Time = Current Pace × Full Race Distance

Internally, every distance is converted to kilometers (1 mile = 1.60934 km, 1 yard = 0.0009144 km) and every pace/speed unit is converted to seconds-per-kilometer before any math happens, so the same core formulas power the Main, Multipoint, Converter, and Finish Time tools consistently.

🏃

Pace vs Speed

Pace is how long it takes to cover a fixed distance (minutes per km/mile) — lower is faster. Speed is how far you travel in a fixed time (km/h or mph) — higher is faster. Runners typically think in pace; cyclists and drivers typically think in speed.

📊

Even Splits

Running each km or mile at the same pace ("even splits") is generally the most efficient race strategy — it avoids the energy cost of surging early and fading late. The splits table assumes a constant pace throughout the entered distance.

🔮

Riegel Race Time Predictions

Predicted times at 5K, 10K, 15K, Half Marathon, and Marathon use Riegel's formula: T2 = T1 × (D2 ÷ D1)^1.06. It estimates how your current fitness translates to other distances, assuming similar training and conditions. Accuracy drops for very different distances (e.g. predicting a marathon from a 1-mile time).

📍

Multipoint Segment Pace

The Multipoint tool subtracts each checkpoint's cumulative distance and time from the previous one (segment distance = current − previous) to isolate the pace of that specific segment, revealing exactly where you sped up or slowed down.

🔄

Pace-Speed Reciprocal Conversion

The Converter treats pace and speed as mathematical reciprocals: speed (km/h) = 3600 ÷ pace (sec/km), and pace (sec/km) = 3600 ÷ speed (km/h). Every one of the 8 units is derived from this single relationship after converting to a common unit.

🏁

Finish Time Linear Projection

Finish Time takes your pace so far (elapsed time ÷ distance covered) and multiplies it by the full race distance — a simple linear scaling with no fatigue adjustment, unlike the Riegel formula used for cross-distance predictions.

⚙️ Why These Formulas Work

Pace and speed are just two ways of expressing the same rate — distance over time — so every conversion in this calculator reduces to that single relationship once units are aligned. The Riegel formula adds a fatigue-adjustment exponent (1.06) on top of simple linear scaling, based on the observed pattern that runners can't hold their short-distance pace over a longer distance; the further you race, the more your average pace naturally slows.

🎯 When to Use It

  • Planning a target pace and splits ahead of a race
  • Checking mid-race whether you're on pace for a goal finish time
  • Converting between unit systems or estimating a new distance from a known time

📋 Assumptions

  • Flat terrain, constant effort, and stable weather conditions
  • The entered distance and time are accurate and measured consistently
  • Riegel predictions assume similar training and race-day conditions across distances

⚠️ Limitations of the Formulas

  • Finish Time assumes you hold your exact current pace for the rest of the race — it doesn't model fatigue or late-race slowdown
  • Riegel predictions get less reliable across very different distances (e.g. marathon from a 1-mile time)
  • None of the formulas account for hills, heat, wind, or surface
  • Multipoint results are only as accurate as the checkpoint distances and times you enter manually
Walkthrough

Step-by-Step: How to Use the Pace Calculator

From choosing a value to solve for, to reading your splits and predictions

Choose what to calculate

On the main tab, pick Pace, Time, or Distance from the Calculate dropdown depending on which value you want to solve for.

Enter your known values

Fill in the other two fields — for example, distance and time if you're solving for pace — choosing metric or imperial units as needed.

Click "Calculate"

The calculator applies pace = time ÷ distance (and its rearrangements) to compute your result instantly.

Review your pace, splits, and predictions

See your pace in multiple units, a per-km splits table and chart, and Riegel-formula predicted race times for other common distances.

Use the other tabs as needed

Switch to Multipoint for checkpoint-to-checkpoint splits, Converter to translate a pace or speed into 8 units at once, or Finish Time to project a mid-race finish.

Example

Worked Example

Using the Main tab's own default scenario — 5 km in 25:00

Scenario

Suppose you're solving for Pace, and you enter a distance of 5 km with a total time of 25 minutes (0:25:00).

Distance5 km
Total Time25:00 (1,500 sec)
ModePace
Step 1 — Pace per km: 1,500 sec ÷ 5 km = 300 sec/km = 5:00 /km.
Step 2 — Pace per mile: 300 sec/km × 1.60934 = 482.8 sec/mi ≈ 8:03 /mi.
Step 3 — Speed: 3600 ÷ 300 = 12.00 km/h (12.00 ÷ 1.60934 ≈ 7.46 mph).
Step 4 — Km splits (even pace): Km 1: 5:00 (cumulative 5:00) · Km 2: 5:00 (10:00) · Km 3: 5:00 (15:00) · Km 4: 5:00 (20:00) · Km 5: 5:00 (25:00). Since the distance is a whole number of km, there's no partial final split.
Step 5 — Riegel-predicted race times: 5K: 25:00 (entered) · 10K: 1,500 × (10/5)1.06 ≈ 3,127 sec ≈ 52:07 · Half Marathon: 1,500 × (21.0975/5)1.06 ≈ 6,900 sec ≈ 1:55:00 · Marathon: 1,500 × (42.195/5)1.06 ≈ 14,387 sec ≈ 3:59:47.
Pace
5:00 /km
Speed
12.00 km/h
Predicted Marathon
3:59:47

Explanation: A flat 5:00/km pace (8:03/mi, 12.00 km/h) over 5 km produces perfectly even 5:00 splits since the distance divides evenly into whole kilometers. Note how the Riegel formula's 1.06 exponent means predicted pace slows gradually at longer distances — the naive linear guess for a marathon would be 25:00 × 8.439 ≈ 3:31:00, but Riegel's fatigue adjustment predicts a more realistic 3:59:47, almost 29 minutes slower, which better matches how endurance performance actually degrades over distance.

Finish Time tool example (same 5:00/km pace): With 5 km covered in 25:00 and a full race distance of 10 km entered, current pace = 1,500 ÷ 5 = 300 sec/km, predicted finish = 300 × 10 = 3,000 sec = 50:00, and remaining distance/time = 5 km / 25:00 — this uses simple linear scaling rather than the Riegel fatigue adjustment, since it's projecting the same run rather than a different race distance.

Interpretation

Understanding Your Pace Result

General training-pace zones and what they're typically used for

Effort LevelTypical UseGeneral Guidance
Easy / conversational paceBase training, recovery runsShould feel comfortable enough to hold a conversation; makes up most weekly training volume
Marathon / steady paceLong runs, marathon race paceComfortably hard, sustainable for hours; a common target for the Finish Time and Riegel predictions
Threshold / tempo paceTempo runs, half marathon race paceSustainable for roughly 30-60 minutes; noticeably harder to hold a conversation
Interval / 5K-10K paceSpeed work, shorter race paceHard, sustainable only for several minutes at a time; used in structured interval sessions
Sprint / all-out paceSprint intervals onlyMaximal effort, sustainable for well under a minute; not representative of race pacing

If your calculated pace matches an easy or marathon-effort zone: it's likely sustainable for the training run or long race distance you're planning — this is the pace zone most training plans emphasize.

If your calculated pace falls in the threshold or interval zones: treat it as a shorter-duration target rather than something to hold for a full race, since these efforts aren't designed to be sustained for hours.

This result is for informational purposes only and is not a medical diagnosis. Pace and finish-time projections are mathematical estimates based on the numbers you enter, not a guarantee of race-day performance — actual results vary with fitness, training, terrain, weather, and pacing strategy.

ℹ️

This calculator provides educational estimates only and should not be used as a substitute for professional medical advice, diagnosis, or treatment. Results may vary depending on individual health conditions. Always consult a qualified healthcare professional regarding medical concerns.

⚠️

Safety note: Pushing to a new pace or distance too quickly raises the risk of overuse injury. Increase weekly mileage and race distance gradually, warm up before hard efforts, stay hydrated, and stop or slow down if you experience chest pain, dizziness, or unusual shortness of breath. If you're new to running or returning after injury, check with a healthcare professional before starting a race-pace training plan.

Use Cases

Practical Use Cases for the Pace Calculator

Where a fast, flexible running pace calculator is genuinely useful

🎯

Planning race-day pacing

Work out the exact pace needed to hit a goal finish time for a 5K, 10K, half, or full marathon.

📈

Predicting times across distances

Use a recent 5K or 10K result to estimate your half marathon or marathon time with the Riegel formula.

🏃

Mid-race finish time checks

Enter your progress so far to see a projected finish time and remaining pace requirement.

📍

Analyzing GPS watch splits

Feed checkpoint distances and times into the Multipoint tool to see exactly where your pace changed.

🏋️

Treadmill speed conversion

Convert a treadmill's mph or km/h display into a familiar outdoor race pace using the Converter tab.

🌍

Unit-flexible training abroad

Switch between metric and imperial when training or racing in a country that uses a different unit system.

👥

Coach-athlete pace planning

Coaches can quickly generate target splits and predicted times for multiple athletes at once.

📊

Even-split race strategy

Use the splits table to plan a steady, even-effort pace rather than starting too fast and fading.

🔁

Interval and tempo workout planning

Convert a target pace into per-km or per-mile split times for structured track and tempo sessions.

🏆

Comparing performances across races

Use the Converter and Riegel predictions to compare a 5K time fairly against a 10K or half marathon result.

📱

Cross-checking GPS watch pace

Verify your device's reported pace or speed against a manually calculated value from distance and time.

🚴

Cycling and multi-sport pacing

Use the Converter's mph/km/h units for cycling legs of a triathlon or general endurance training.

📚

Running education and coursework

Illustrate pace, speed, and Riegel-formula race prediction concepts for students or new runners.

Pros & Cons

Benefits and Limitations

What this pace calculator does well, and where it can't replace real-world testing

✅ Benefits

  • Four tools in one: pace/time/distance solver, multipoint splits, unit converter, and finish time projection
  • Free, instant, and requires no signup or personal information
  • Runs entirely in your browser — your training data is never sent to a server
  • Supports both metric and imperial units, plus 8 pace/speed units in the converter
  • Built-in distance presets from 800m to full Marathon avoid manual conversion mistakes
  • Generates a full per-km splits table and chart automatically
  • Riegel-formula predictions for 5K, 10K, 15K, Half, and Marathon distances
  • Multipoint tool supports up to 12 checkpoints for detailed segment analysis
  • Finish Time tool gives a quick mid-race progress check
  • Downloadable plain-text summary of your main-tab results
  • Fast-loading and mobile-friendly for use on race day
  • Repeatable tool for planning and reviewing multiple races or workouts
  • Based on the well-established Riegel race-prediction formula

⚠️ Limitations

  • Finish Time assumes a perfectly constant pace — it doesn't model late-race fatigue or slowdown
  • Riegel predictions get less reliable across very different distances
  • Doesn't account for hills, heat, wind, altitude, or race-day conditions
  • Multipoint results depend entirely on the accuracy of checkpoint data you enter manually
  • Doesn't personalize predictions to training history, injury status, or fitness trend
  • Splits table assumes even pacing, not a deliberate negative- or positive-split strategy
  • Not a substitute for a structured training plan or coaching guidance
  • No GPS or device import — all checkpoint data must be entered by hand
Reference

Pace-to-Speed Conversion Reference Table

Common training paces converted across all four core units

Pace (/km)Pace (/mi)Speed (km/h)Speed (mph)
4:00 /km6:26 /mi15.00 km/h9.32 mph
4:30 /km7:15 /mi13.33 km/h8.28 mph
5:00 /km8:03 /mi12.00 km/h7.46 mph
5:30 /km8:51 /mi10.91 km/h6.78 mph
6:00 /km9:39 /mi10.00 km/h6.21 mph
6:30 /km10:28 /mi9.23 km/h5.74 mph
7:00 /km11:16 /mi8.57 km/h5.33 mph

Common Mistakes and Expert Tips

❌ Common Mistakes

  • Starting a race significantly faster than goal pace, which usually costs more time later than it gains early
  • Entering elapsed or checkpoint times imprecisely, which compounds into meaningfully wrong splits
  • Treating a Riegel prediction from a very short distance (e.g. a mile) as reliable for a marathon
  • Ignoring hills, heat, or wind and expecting flat-course splits to hold exactly
  • Assuming Finish Time projections account for a fade — they assume your current pace holds steady
  • Mixing up which unit (pace vs speed) is selected in the Converter before reading the result

💡 Expert Tips & Best Practices

  • Use even splits as your default race strategy unless you have a specific reason for negative splits
  • Cross-check Riegel predictions against distances reasonably close to your known performance
  • Use the Multipoint tool after a race to see exactly which segment slowed you down the most
  • Recalculate Finish Time a few times during a long race to track whether you're fading or holding steady
  • Pair your pacing plan with NeftCal's Target Heart Rate Calculator to keep effort in the right training zone
📝

Summary: This pace calculator gives you an instant, free way to solve for pace, time, or distance, break a race into checkpoint splits, convert between 8 pace and speed units, and project a mid-race finish time — a practical running pace calculator for training and race day alike, not a substitute for a full training plan. Pair it with related tools like the Target Heart Rate Calculator and TDEE Calculator for a fuller picture of your training and energy needs.

FAQ

Frequently Asked Questions

Common questions about pace calculations

What can the Pace Calculator solve for?
It solves for any one of three values given the other two: Pace (from Distance & Time), Time (from Distance & Pace), or Distance (from Pace & Time) — just choose what you want to calculate from the Calculate dropdown.
What units does it support?
Both metric and imperial: distances in miles, meters, kilometers or yards, with distance presets from 800m up to a full Marathon, and pace/speed in 8 units including per mile, per kilometer, mph, km/h, meters per minute/second, and yards per minute/second.
What is the Multipoint tool for?
It computes your pace and split times between a series of race checkpoints you define, useful for analyzing per-km or per-mile splits across a race with multiple timing points.
What does the Converter tab do?
It converts a pace or speed value between the 8 supported units instantly, so you can translate a treadmill speed in mph into a min/km race pace, for example.
How does the Finish Time projection work?
The Finish Time tool linearly projects your expected finish time mid-race based on your pace so far and the remaining distance, giving a quick estimate of when you'll cross the line if you hold your current pace.
Does the calculator predict race times using the Riegel formula?
Yes, it can generate race time predictions using the Riegel formula, which estimates your expected time at other race distances based on a known performance at one distance.
What is the Riegel formula and how does it work?
The Riegel formula is T2 = T1 × (D2 ÷ D1)^1.06, where T1 and D1 are a known time and distance, and T2 is the predicted time at a new distance D2. The 1.06 exponent accounts for the extra fatigue of running farther — it's why predicted pace slows down slightly as distance increases, rather than staying flat.
How do I calculate my running pace manually?
Divide your total time by your total distance. For example, running 5 km in 25 minutes gives a pace of 25 ÷ 5 = 5 minutes per km. To convert to minutes per mile, multiply by 1.60934 (5 × 1.60934 ≈ 8.05 minutes, or about 8:03 per mile). This calculator automates that math and adds splits and predictions on top.
What is a good marathon pace for beginners?
There's no single "good" marathon pace — it depends entirely on your fitness and training history. Many first-time marathoners aim to finish comfortably rather than chase a specific pace, often somewhere in the 9-12 minute per mile range, but the more useful benchmark is a realistic pace based on your own training runs, checked against this calculator's Riegel predictions from a recent shorter race.
Does this calculator account for hills or terrain?
No. All calculations here — pace, splits, Riegel predictions, and finish time — assume flat, constant-effort running. Hills, trail terrain, heat, and wind all affect real-world pace but aren't modeled by this calculator. Treat results as a flat-course baseline and adjust your expectations for challenging terrain or conditions.
Can I use this pace calculator for cycling or swimming?
The core pace and speed math works for any steady-effort activity, and the Converter tab's mph/km/h units are commonly used for cycling. However, the Riegel race-time predictions and split structure are calibrated for running and are less reliable for swimming, where pacing dynamics differ substantially.
Is this pace calculator free to use?
Yes. This pace calculator is completely free, requires no signup or account creation, and runs entirely in your browser — your distance, time, and pace inputs are never transmitted to or stored on a server. Use any of the four tools as many times as you like.
How do I convert minutes per mile to km per hour?
First convert your pace to minutes per km by dividing by 1.60934 (since 1 mile ≈ 1.60934 km), then divide 60 by that number to get km/h. For example, an 8:00 per mile pace is about 4:58 per km, giving a speed of roughly 12.07 km/h. The Converter tab on this calculator does this instantly for all 8 supported units.
Why do my km and mile paces look so different?
A mile (1.60934 km) is longer than a km, so your per-mile pace number will always be larger than your per-km pace for the same running speed — e.g. 5:00/km is roughly 8:03/mi. Both describe the same speed; pick whichever unit matches how races are measured in your region.
Should I run even splits or negative splits?
Even splits (same pace throughout) are simplest and generally reliable. Negative splits (running the second half faster than the first) are used by many experienced racers because starting conservatively conserves glycogen and reduces the risk of a late-race fade. Avoid positive splits (starting too fast and slowing down) — they usually cost more time than they gain early on.
Learn More

Authoritative Resources on Running and Physical Activity

Official guidance to complement this calculator — not a substitute for licensed medical or coaching advice

Related Calculators

Explore other health and fitness tools