Marathon Pace Calculator Per Mile: Exact Paces, MPH and the 26.2188 Rule
Convert any marathon goal into exact per-mile pace, mph and km/h — plus the divisor test, the watch-overrun rule, and the six checkpoints worth printing.
Kristian Hoffmann
SaaS founder and operator
Divide your goal time by 26.2188 miles — not 26.2, and definitely not 26. A four-hour marathon is 9:09.2 per mile: 6.55 mph, or 5:41 per kilometre. That is the entire calculation, and it is also where most pacing plans collect their first ten to a hundred and twenty seconds of error, before the runner has even laced a shoe.
Every marathon pace calculator per mile performs the same division: goal time in seconds ÷ 26.218757. What separates a useful one from a decorative one is the distance constant it uses, whether it shows fractional seconds, and whether it does anything at all with the course you are actually going to run.
Test your calculator in fifteen seconds
Enter a 4:00:00 marathon and read the per-mile output. The number tells you which distance the tool assumed.
| It shows | Distance it used | If you hold that pace to the real finish |
|---|---|---|
| 9:09 | 26.2188 mi (42.195 km) | 3:59:54 |
| 9:10 | 26.2 mi | 4:00:20 |
| 9:13 or 9:14 | 26.0 mi | 4:02:05 |
The 26.2 shortcut is the common one and it is nearly harmless — ten to twenty seconds at a four-hour goal, less at faster ones. The 26.0 version is not harmless. It hands you a pace that feels correct for twenty-six miles and then bills you two minutes for the last 385 yards, which is exactly the stretch where you have no capacity left to argue.
Worth knowing in its own right: at four-hour pace, the 0.2188 miles past the mile-26 marker takes two minutes. Runners who plan in whole miles are budgeting for a race that is two minutes shorter than the one they entered.
Per-mile pace for every common goal time
Paces below are computed from the full 42.195 km, carried to a tenth of a second, then converted. The mph column is 3600 ÷ seconds per mile; the km column is the same pace ÷ 1.609344.
| Goal time | Per mile | mph | Per km |
|---|---|---|---|
| 3:00:00 | 6:51.9 | 8.74 | 4:16.0 |
| 3:15:00 | 7:26.2 | 8.07 | 4:37.3 |
| 3:30:00 | 8:00.6 | 7.49 | 4:58.6 |
| 3:45:00 | 8:34.9 | 6.99 | 5:19.9 |
| 4:00:00 | 9:09.2 | 6.55 | 5:41.3 |
| 4:15:00 | 9:43.6 | 6.17 | 6:02.6 |
| 4:30:00 | 10:17.9 | 5.83 | 6:23.9 |
| 4:45:00 | 10:52.2 | 5.52 | 6:45.3 |
| 5:00:00 | 11:26.5 | 5.24 | 7:06.6 |
| 5:30:00 | 12:35.2 | 4.77 | 7:49.2 |
| 6:00:00 | 13:43.8 | 4.37 | 8:31.9 |
Notice how tight the tenths are. Between a 3:30:00 and a 3:29:30 sits roughly one second per mile. That is smaller than your reaction time at a mile marker, which is the real argument for pacing off cumulative time rather than off individual mile splits.
The mph conversion matters more than it looks
Four anchor points are exact and worth memorising, because they let you sanity-check any tool or treadmill without arithmetic: 6.0 mph = 10:00/mi, 7.5 mph = 8:00/mi, 8.0 mph = 7:30/mi, 10.0 mph = 6:00/mi.
The reason this is not trivia: most treadmills move in 0.1 mph steps, and near four-hour marathon pace one step is 8.4 seconds per mile. Run the whole distance on 6.5 mph and you finish in 4:02:01. Bump it to 6.6 mph and you finish in 3:58:21. A single button press is worth 3:40 of finish time, and 6.55 mph — the pace you actually want — is not a setting the machine offers.
So if you are rehearsing goal pace indoors, decide in advance which side of the gap you train on, and treat the treadmill number as an approximation of your target rather than the target itself. For metric conversion in your head: minutes per kilometre ≈ minutes per mile × 0.62.
Why your watch reads long, and what it costs
In most road-race GPS files, the recorded distance finishes longer than the certified one. Tangents get cut imperfectly, aid stations pull you sideways, tall buildings scatter the signal — the errors add distance far more often than they remove it.
The consequence is a clean one-to-one rule: whatever percentage your watch runs long, that same percentage lands on your finish time if you pace off watch laps. One percent long costs 1% of your goal — 2:24 on a four-hour marathon, 1:48 on a three-hour.
| Watch reads at the finish | Overrun | Cost on a 3:30 goal | Cost on a 4:00 goal |
|---|---|---|---|
| 26.32 mi | +0.4% | +0:50 | +0:58 |
| 26.43 mi | +0.8% | +1:41 | +1:55 |
| 26.53 mi | +1.2% | +2:31 | +2:53 |
Do not guess your figure. Open your two most recent race files, read the final distance, and divide by 26.2188 — that percentage is *your* overrun, and it is fairly stable per runner and per course type. Then pace off the painted mile markers for cumulative time and demote lap pace to a within-mile guardrail: useful for noticing you have drifted 20 seconds fast, useless as a source of truth.
Print six checkpoints, not twenty-six
Two rounding rules, both cheap to follow:
- Round the cumulative times, never the pace you multiply by. At a four-hour goal, printing 9:09 flat brings you in about six seconds early; printing 9:10 puts you 20 seconds late. Compute from 549.2 seconds and round only the output.
- Print six checkpoints. Nobody performs 26 subtractions at 8:00/mi effort, and every marker you read carries a couple of seconds of reaction error, so more checkpoints means more noise, not more control.
A workable set for a four-hour goal:
| Checkpoint | Cumulative |
|---|---|
| Mile 3 | 27:28 |
| Mile 8 | 1:13:14 |
| Halfway (13.11 mi) | 2:00:00 |
| Mile 18 | 2:44:46 |
| Mile 22 | 3:21:23 |
| Finish (26.22 mi) | 4:00:00 |
Mile 3 is the honesty check, mile 18 is the decision point, mile 22 is where you find out whether the plan was real. If you want the full mile-by-mile version, the mechanics are laid out in Running Splits by Mile Calculator: Formulas and Split Tables, and the printing side in Marathon Pace Band Calculator: Build Accurate Race Splits.
When an even per-mile split is the wrong target
An even split is a default, not a strategy. It stops being appropriate the moment the course stops being flat, cool and still.
As a working threshold: if any single mile of the course holds more than about 30 m (100 ft) of climbing, price that mile slower deliberately and plan to recover the time on the matching descent, rather than defending 9:09 uphill and paying for it three miles later. Courses with a few hundred metres of cumulative gain will misprice at least four or five miles on a flat band — that is the sort of mismatch grade-adjusted pace exists to solve.
Heat and humidity work differently. They do not change what your legs can do over one mile; they change what your legs can do over the last ten. Any heat adjustment you apply is a model, so check which inputs yours actually uses — temperature alone, or temperature plus humidity plus acclimatisation — before you trust its number. This is the layer TrainingFlow computes deterministically from course elevation, altitude and a race climate baseline, with the narrative written on top of the numbers rather than in place of them.
Wind is the one runners forget on out-and-backs. A tailwind out and a headwind home is not a neutral trade; the return leg is run on tired legs at the same wattage cost.
Three ways per-mile pacing fails after halfway
Banking time. The most common failure, and it happens in the first fifteen minutes. If you reach mile 3 more than 10 seconds per mile ahead of plan, correct on the next mile — not "later", because later is mile 20 and you will not have the means. Thirty seconds banked early is not thirty seconds saved; it is a loan at a bad rate.
Aid-station arithmetic. Six twelve-second walk-throughs cost 72 seconds. Spread across the full distance, that is 2.75 seconds per mile you have to find somewhere else. Either budget the stops into your checkpoint times, or practise drinking on the move — but pick one before race morning.
Chasing the marker. You arrive at a marker four seconds down and spend the next half mile at 20 seconds per mile faster to erase it. Four seconds is inside the noise of your own lap-button timing. Correct trends across three miles, not single readings.
Before you build the band
The pace table is downstream of one question the calculator cannot answer: whether the goal time is supported by a recent race result or only by preference. Run that check first — Marathon goal pace calculator: find your target pace covers how a recent 10K or half converts into a marathon target and where those conversions get optimistic. A per-mile plan built on a goal you cannot hold for two hours is a very precise map to the wrong place.
Common questions
What pace is a 4-hour marathon per mile? 9:09.2 per mile over 26.2188 miles. Printing 9:09 flat brings you in around 3:59:54; 9:10 puts you at roughly 4:00:20. In other units, 6.55 mph or 5:41 per kilometre.
How many miles is a marathon, exactly? 42.195 km, which is 26.218757 miles. The 0.218757 beyond mile 26 takes about two minutes at four-hour pace and about 90 seconds at three-hour pace.
What mph is a 3-hour marathon? 8.74 mph, equal to 6:51.9 per mile or 4:16.0 per kilometre.
Should I pace off mile markers or my watch? Markers for cumulative time, watch for within-mile drift. The markers are on the measured course; your watch is measuring the line you personally ran, which in most files is the longer of the two.
Per mile or per kilometre? Use whichever unit the course marks. Running metric splits past imperial markers means converting under fatigue, which is where arithmetic errors turn into pacing errors.