FREE MARATHON PACE CALCULATOR: 26.2 MILE SPLITS & FINISH TIME PREDICTOR

Marathon pace is the average speed you need to maintain consistently across all 26.2188 miles to hit your goal finish time. For example, a 4:00 marathon requires a pace of approximately 9:09 per mile (5:41 per km). Your marathon pace sits between your easy/long run pace (slower) and your tempo/threshold pace (faster) — it is a sustained, moderately hard effort you can hold for the full race distance. Most runners describe it as feeling “controlled hard” — you could speak a sentence or two but wouldn’t hold a relaxed conversation.

Divide your goal finish time (in seconds) by 26.2188 to get your required seconds per mile, then convert back to minutes and seconds. For a 4:00:00 goal: 14,400 seconds ÷ 26.2188 = 549.6 seconds per mile = 9 minutes 10 seconds per mile. Alternatively, use this calculator’s Goal Finish Time → Pace mode above to get your per-mile and per-km pace instantly, along with a full 26-mile split table.

Average marathon finish times by age group (all genders combined, based on global race data): Age 18–24: ~4:30. Age 25–34: ~4:25. Age 35–44: ~4:30. Age 45–54: ~4:45. Age 55–64: ~5:10. Age 65+: ~5:45. These are averages across all ability levels — a well-trained runner in any age group will be faster. Physiological peak marathon performance is typically between ages 27–35, with a gradual decline of roughly 1% per year after 40. Age grading calculators (available from World Athletics) let you compare your time against the world record for your specific age and gender.

The global average marathon finish time across all runners is approximately 4:29–4:32. Breaking 4:00 (sub-4) is a widely recognised recreational benchmark — roughly the top 40–45% of all finishers at major marathons. Breaking 3:30 puts you in approximately the top 20%. Sub-3:00 is elite recreational territory — top 5% or less. Sub-2:30 is national-class level. The current world records are 2:00:35 (men, Kelvin Kiptum, Chicago 2023) and 2:09:56 (women, Ruth Chepngetich, Chicago 2024).

Pace is time per unit of distance (e.g., 9:00 per mile or 5:36 per km) — it tells you how long it takes to cover a set distance. Speed is distance per unit of time (e.g., 6.7 mph or 10.8 km/h) — it tells you how far you travel in a set time. Runners and coaching tools almost universally use pace because it directly maps to race split targets. To convert pace to speed: divide 60 by your pace in minutes. A 9:00/mile pace = 60 ÷ 9 = 6.67 mph.

Divide your min/mile pace by 1.60934 to get min/km. For example, a 9:00/mile pace ÷ 1.60934 = 5:35/km. To go the other direction — min/km to min/mile — multiply by 1.60934. So a 5:00/km pace × 1.60934 = 8:03/mile. This calculator automatically shows both units simultaneously in the quick stats row after every calculation, so you never need to convert manually.

Your long run pace should be 60–90 seconds per mile slower than your goal marathon pace — comfortably conversational at all times. If your marathon goal pace is 9:00/mile, your long runs should sit around 10:00–10:30/mile. For beginners and runners doing their first marathon, slowing down by a full minute or more per mile is appropriate. Runner’s World recommends long-run heart rate in the 75–83% of max HR range. Running long runs too fast is one of the most common errors in marathon training — it accumulates fatigue without additional aerobic benefit, and risks injury and overtraining.

Yes — but only in specific workouts, not daily. Marathon pace (MP) runs are best incorporated as marathon-specific tempo efforts: 10–16 mile runs where miles 5–12 are held at goal marathon pace, typically 3–5 weeks before race day. These build neuromuscular familiarity with race pace and confirm your goal is realistic. They are not easy runs — MP during a 15-mile training run on tired legs will feel harder than MP will on race day after a proper taper. If you cannot sustain your goal MP for 8–10 miles in training, consider revising your goal time.

Marathon pace during a mid-training MP workout should feel “moderately hard” — an RPE (Rate of Perceived Exertion) of roughly 6–7 out of 10. You can say a short sentence but not hold a full conversation. Breathing is controlled but noticeably elevated. Crucially, MP will feel harder during training than on race day because: (1) you are not tapered, (2) you are running it after miles of warm-up effort, and (3) race-day adrenaline, crowd energy, and cooler morning temperatures all improve performance. Do not panic if MP feels hard at mile 10 of a long run during peak training week.

The 10/10/10 method, popularised by Runner’s World, divides the marathon into three phases of roughly 10 miles each. Miles 1–10 (“Run with your head”): hold back, run 10–15 seconds per mile slower than goal pace — consciously resist the crowd and adrenaline. Miles 11–20 (“Run with your training”): settle into goal marathon pace, running the race you prepared for. Miles 20–26.2 (“Run with your heart”): if you have executed the first 20 miles correctly, this is where you can push — grinding through the final 10K on willpower and banked glycogen. The strategy is designed specifically to prevent the catastrophic blow-up that comes from going out too fast.

Standard marathon training plans run 16–20 weeks. 16 weeks is a minimum for runners with a solid base (20+ miles/week consistently). 18–20 weeks is recommended for first-timers or runners building from low mileage. The final 3 weeks are taper — you are not gaining significant fitness then, you are recovering. For significant time goals (e.g., sub-3:30 or sub-3:00), many coaches recommend 20–24 week build cycles or sequential back-to-back training blocks over multiple years. Running pace is a product of cumulative training load over months, not weeks.

Marathon pace (MP) is the pace you sustain for 26.2 miles on race day. Threshold pace (also called lactate threshold or tempo pace) is approximately 20–30 seconds per mile faster than marathon pace — roughly equivalent to 10K race pace. Threshold pace is the maximum effort you can sustain for 20–40 minutes before blood lactate accumulates faster than it can be cleared. Training at threshold pace raises this lactate clearance rate, which in turn allows you to run faster at marathon pace for longer. The two paces serve different training purposes and should not be confused.

For recreational runners, even splits or a slight negative split are the most reliable strategies. A negative split means running the second half faster than the first — used by Eliud Kipchoge and virtually every world record marathon. An even split means identical pace per mile throughout. A positive split (faster first half) is the most common cause of a blow-up and hitting the wall. The data is clear: runners who go out 30–60 seconds too fast in the first half almost universally run the second half significantly slower, producing a worse overall time than a conservative even start would have generated.

A target negative split of 1–3 minutes is optimal for most recreational runners. For a 4:00 goal (half split = 1:57:35), target 1:59–2:02 for the first half, then run 1:57–1:58 for the second. This does not mean running dramatically faster in the second half — it means running conservatively in miles 1–10 (slightly under goal pace), settling into exact goal pace in miles 11–20, then pushing in miles 20–26 if you have the reserves. Even a half marathon split that is 60–90 seconds slower than your target half split is not a disaster — it is deliberate insurance against the wall.

A pace band is a small strip (paper, card, or silicone wristband) listing your cumulative time at each mile marker. Print the Mile Splits table from this calculator’s Mile Splits tab, cut it to wrist size, and wrap it in clear tape to waterproof it. On race day, glance at your pace band at every mile marker and note whether your cumulative time is ahead or behind the printed time. Key checkpoints to monitor: Mile 5 (early pacing check), Mile 10 (glycogen management zone), Mile 13.1 (half split confirmation), Mile 20 (the wall zone). If you are more than 90 seconds ahead of pace at mile 10, you are going out too fast — ease back immediately.

Yes — and this is one of the most dangerous effects a marathon runner faces. Race-day adrenaline, crowd noise, taper-fresh legs, and cool morning temperatures can make your goal marathon pace feel significantly easier than it does during hard training weeks. This is not a signal to run faster — it is a trap. Your glycogen stores are the same regardless of how good you feel in mile 1. Running 20 seconds per mile faster than planned in the first 10 miles is an almost guaranteed predictor of a catastrophic slowdown at miles 20–22. Stick rigidly to your pace band in the first 10 miles no matter how good you feel.

Both — but with a clear hierarchy. Use your GPS watch as a primary pacing tool for the first 15 miles to ensure you are not overcooking the early stages. After mile 15, shift to running by effort as the pace naturally becomes harder to maintain. GPS watches can drift by 0.1–0.2 miles over a full marathon course due to tangent running, tunnel shadows, and building interference — this is normal and why you check your cumulative time at official mile marker signs rather than relying solely on your watch’s distance. Pace alerts set to beep if you go more than 10 seconds per mile faster than goal pace are useful insurance in the first 10 miles.

The wall (also called “bonking”) is the sudden, severe physical and mental deterioration that occurs when the body’s glycogen stores are fully depleted — typically around miles 18–22. When glycogen runs out, the body must switch to burning fat for fuel, which produces energy 30–40% less efficiently. This physiological shift causes an abrupt drop in pace, extreme fatigue, heavy legs, and in severe cases confusion or disorientation. It is not a willpower failure — it is a genuine metabolic event that cannot be overridden by mental toughness alone. Prevention requires three simultaneous strategies working together: correct pacing, consistent fueling, and adequate long-run training.

The average runner’s body stores approximately 1,800–2,000 calories of glycogen in muscles and the liver — enough to fuel roughly 18–20 miles at marathon pace. Mile 20 is roughly where this glycogen reserve is exhausted for a runner who has not fueled adequately during the race. The exact mile varies by runner, pacing, temperature, and fueling: runners who start too fast deplete glycogen faster (may hit the wall at mile 16–18), while runners who fuel consistently with 30–60g of carbohydrates per hour can push the depletion point closer to mile 22–24 or avoid it entirely.

Three strategies must work simultaneously: (1) Pacing: Run the first 5 miles at 10–15 seconds per mile slower than goal pace. Every second you run too fast early translates to multiple lost seconds late in the race. (2) Fueling: Begin taking carbohydrates at mile 4–5 (not when you feel tired). Target 30–60g of carbohydrates per hour via gels, chews, or sports drink. Practice your exact race-day fueling strategy on every long run — never try anything new on race day. (3) Training: Complete 2–3 runs of 20+ miles at proper long run pace during your training cycle. These long efforts improve your body’s fat oxidation efficiency at marathon pace, sparing glycogen.

If you hit the wall mid-race: (1) Slow your pace immediately — trying to power through at goal pace after bonking accelerates the deterioration and increases collapse risk. Drop 30–60 seconds per mile and switch to effort-based running. (2) Take in carbohydrates immediately — grab a gel, sports drink, or banana from the next aid station. Carbohydrate absorption takes 15–20 minutes to improve blood glucose, so act early. (3) Take a brief walk break — even 60–90 seconds of walking at a brisk pace allows partial glycogen recovery and heart rate reduction. (4) Stay hydrated — dehydration compounds glycogen depletion significantly. Finishing the race at a reduced pace is always better than a DNS.

The most common rule of thumb is: Marathon time ≈ Half marathon time × 2.1. The 0.1 multiplier accounts for the physiological cost of the second half of a marathon — glycogen depletion, accumulated fatigue, and pace fade. Examples: 1:45 half → 3:41 marathon. 2:00 half → 4:12. 2:15 half → 4:44. The multiplier varies by training volume: runners at 50+ miles per week often run closer to 2.05×, while lower-mileage runners (25–35 mpw) typically run 2.15–2.20×. The Riegel formula used in this calculator’s Race Predictions tab gives a more precise estimate. Always base your marathon goal on a recent race, not a training run — training runs underestimate race-day performance.

Use the Riegel formula: Marathon time = 5K time × (42.195 ÷ 5)^1.06. However, predictions become less accurate as the ratio between input and target distance increases. A 5K → marathon prediction carries ±8–12% error because the limiting factors for a 5K (VO₂ max, anaerobic capacity) are completely different from a marathon (glycogen endurance, fat oxidation efficiency). A half marathon input gives a far more reliable marathon prediction than a 5K. For 5K-based predictions, add a conservative buffer of 5–10 minutes to the raw prediction, especially if you have never raced a marathon before.

The Riegel formula, published by Pete Riegel in American Scientist (1981), predicts race time across distances: T2 = T1 × (D2 ÷ D1)^1.06. T1 = your known race time, D1 = that race’s distance, D2 = your target distance, T2 = predicted time. The exponent 1.06 encodes the progressive physiological cost of longer distances — if effort scaled perfectly linearly, the exponent would be 1.0, but fatigue, glycogen depletion, and aerobic drift add roughly 6% per doubling of distance. It is the most widely used race equivalency formula globally, used by Runner’s World, VDOT calculators, and most pace prediction tools.

Training runs significantly underestimate race performance and should not be used as direct predictors. The reason: training runs are done without taper, without race-day adrenaline, often in higher heat, and frequently with fatigue from previous days. Race conditions (full taper, cool morning temperatures, crowd energy, competition) typically improve performance by 5–15% compared to equivalent training efforts. For the most accurate marathon time prediction, use a recent tune-up race — a 10K or half marathon run 6–8 weeks before your marathon at full race effort — as your Riegel formula input.

Boston Athletic Association (BAA) sets BQ standards by age and gender. Examples for 2026: Men 18–34: sub-3:00 (6:52/mile). Men 35–39: sub-3:05. Men 40–44: sub-3:10. Women 18–34: sub-3:30 (8:00/mile). Women 35–39: sub-3:35. Women 40–44: sub-3:40. Note: qualifying time is not sufficient — the Boston Marathon is oversubscribed, so runners typically need to beat their BQ standard by 2–5 minutes to secure a field entry. Enter your age-group BQ standard into this calculator to find your required per-mile pace.

Heat has a significant and well-documented negative effect on marathon performance. General pace adjustment guidelines: 60–65°F (15–18°C): adjust goal pace by +20–30 sec/mile. 65–70°F (18–21°C): +30–45 sec/mile. 70–75°F (21–24°C): +45–60 sec/mile. 75–80°F (24–27°C): +60–90 sec/mile or switch entirely to an effort-based rather than pace-based strategy. Above 80°F (27°C), finishing safely becomes the priority over time goals. Heat forces the cardiovascular system to divert blood to the skin for cooling, reducing oxygen delivery to working muscles — this is a physiological ceiling that cannot be overcome with willpower or fitness alone.

High humidity (above 60%) severely impairs the body’s primary cooling mechanism — sweat evaporation. In humid conditions, sweat stays on the skin rather than evaporating, dramatically reducing cooling efficiency and forcing core temperature higher. In 75°F with 80% humidity, the effective physiological stress equals approximately 85°F dry heat. As a rule of thumb, add the temperature (°F) and humidity percentage: if the sum exceeds 130, consider abandoning your time goal and racing for safe completion. At 150+, elite runners often slow by 5–8 minutes in a full marathon compared to ideal conditions.

Hills add time in two ways: (1) uphill running requires significantly more energy at the same pace, and (2) aggressive downhill running damages quadriceps muscles via eccentric loading, contributing to late-race fatigue and the wall. A general rule for hilly courses: add 1 minute to your finish time for every 100 feet (30m) of net elevation gain per mile. For heavily hilly courses (Boston, Big Sur, NYC), subtract 5–15 minutes from a flat-course goal before entering your target time into a pace calculator. Practice hill running in training if racing a hilly course — and on downhills especially, practice controlled form to protect your quads.

Cool conditions (35–55°F / 2–13°C) are optimal for marathon performance and typically require no pace adjustment — this is the ideal racing window. Very cold conditions (below 32°F / 0°C) require a brief additional warm-up and may mean your first mile is slightly slower before muscles reach full working temperature, but performance is generally not impaired. Strong headwinds are the greater concern in cold-weather races — a 10 mph headwind adds approximately 30 seconds per mile compared to calm conditions. If you encounter a sustained headwind section, draft behind another runner and treat that section as effort-based rather than strictly pace-based.

Trail marathon paces are not directly comparable to road marathon paces and should not be calculated the same way. Pace calculators designed for road running are not appropriate for trail events — use effort (heart rate or RPE) as your primary metric instead. General conversion: expect trail marathon times to be 10–30% slower than your road marathon time, depending on terrain, elevation gain, and technical difficulty. For a light, well-groomed trail, add 30–45 sec/mile. For technical, hilly terrain, add 60–120+ sec/mile. Most experienced trail runners target heart rate (65–75% of max on flat/downhill, up to 85% on climbs) rather than pace.

For a first marathon, your primary goal should be to finish without hitting the wall — not to hit a specific time. A conservative approach: set your pace based on your recent half marathon × 2.2 (not 2.1). This extra conservatism accounts for first-marathon inexperience, race-day adrenaline overcooking, potential fueling mistakes, and the unknown of miles 20–26 which most first-timers have never experienced in training. Typical first-marathon finish times range from 4:30–5:30. Running a comfortable, controlled race and finishing strong is worth far more strategically than blowing up chasing a time you aren’t ready for.

Three practical tests: (1) The long run test: If you cannot sustain your goal marathon pace (MP) for at least 8–10 continuous miles in a mid-training long run (after a 5-mile warm-up), your goal may be too aggressive. (2) The half marathon test: Race a tune-up half marathon 6–8 weeks out and plug the result into this calculator’s Race Predictions tab. If the Riegel prediction for your marathon is slower than your goal, revise downward. (3) The weekly mileage test: If your average weekly mileage is below 35 miles over the 12 weeks before the race, a time goal at the aggressive end of your ability range is higher risk. A goal that requires you to run faster than your Riegel prediction is almost always a recipe for a blow-up.

Recommended GPS watch setup for marathon day: (1) Custom pace alert: Set a beep/vibrate if pace drops more than 10 sec/mile below goal pace (warning you are slowing) or exceeds 10 sec/mile faster than goal pace (warning you are going too fast — the more dangerous alert). (2) Auto-lap at 1 mile: This gives you a split at every mile so you can compare to your pace band. (3) Data fields: Display current pace, average pace, and total time simultaneously — not just current pace, which fluctuates second-to-second. (4) Set course distance to 26.2188 miles: Some watches allow manual target distance, which prevents premature “race complete” alerts if GPS drift measures a slightly short course.

Miles 20–26 are where the race is truly won or lost. If you have paced correctly in miles 1–20, you should still have enough glycogen for a strong finish. Key strategies: (1) Switch to effort, not pace: Your GPS pace will fluctuate as fatigue sets in — run by feel at the maximum effort you can sustain for the remaining miles. (2) Break it into landmarks: “Just get to mile 22” then “Just get to mile 24” — never think about the full remaining distance. (3) Use run-walk if needed: A