Marathon Pace Calculator

What do I need to know about Negative Splitting?

Running the second half of a race faster than the first — a 'negative split' — is the most efficient pacing strategy for almost all runners, and it's the strategy used by virtually every marathon world record. The reason is physiological: going out too fast in the early kilometres depletes muscle glycogen at an accelerated rate, builds up fatigue products, and causes a steep decline in the final third — the dreaded 'bonk' or 'hitting the wall' that ruins so many amateur marathons. By contrast, a controlled first half conserves glycogen, keeps you within aerobic limits, and leaves enough in reserve to lift the pace from halfway. A worked example for a 4-hour marathon (5:41/km average): a positive split might be running the first half in 1:55 (5:27/km) and crawling the second in 2:05 (5:55/km), which feels disastrous in the closing miles. An even-paced 4:00 holds 5:41 throughout. A negative split runs the first half in 2:01 (5:43/km) and lifts to 1:59 (5:38/km) — same final time but a much better-managed effort. For most runners, aiming to run the first half a few seconds per km slower than goal pace, then lifting at halfway, gives the best chance of hitting target. The discipline is in the early miles: with adrenaline and fresh legs, it feels easy to go faster than planned, but every second 'banked' early usually costs you ten seconds at the end. Practising race pacing on long training runs builds the discipline.

What do I need to know about Key Marathon Benchmarks?

Marathon goal times have well-known pace equivalents that let you calibrate your training and race plan. Sub-5 hours = 7:06/km — a popular first-marathon target, achievable for many recreational runners with a consistent training plan. Sub-4 hours = 5:41/km — a major milestone for amateur runners, often the goal of a serious training block. Sub-3:30 = 4:58/km — solidly under the elusive sub-5min/km barrier, requiring committed training. Sub-3 hours = 4:15/km — a benchmark that puts you in the upper few percent of marathoners, demanding consistent quality training and good genetics. Sub-2:30 = 3:33/km — competitive at club/elite-amateur level. Sub-2:15 ≈ 3:12/km — international elite. Sub-2 hours = 2:51/km — only Eliud Kipchoge has officially run faster in a course-record setting (his sub-2 Vienna run, 2019, was 1:59:40 in a special exhibition, not a record-eligible race; his current official world record is 2:00:35 from Berlin 2022, which equates to about 2:51.5/km). For most club runners, 3:30–4:00 is a realistic target with serious training; 4:00–5:00 covers a huge band of committed amateurs; 5:00+ is fine for first-timers focused on completion. Match your goal pace to your half-marathon time using the Riegel formula (marathon time ≈ 2.10 × half marathon time, give or take depending on endurance training). Many runners overestimate their marathon capability from shorter race results — being conservative in the first marathon avoids the wall and gives a positive experience to build on.

What's the difference between Training Pace and Race Pace?

A common training mistake is running everything at roughly the same effort — typically moderately hard, neither truly easy nor properly fast — which builds 'junk miles' that don't optimally develop fitness. Effective marathon training uses distinct paces for distinct purposes. Easy runs should be 60–90 seconds per km slower than target race pace — slow enough for comfortable conversation, designed to build aerobic capacity and capillary density without straining the body. These should account for 70–80% of total weekly mileage in most marathon plans. Long runs (the cornerstone of marathon training, typically up to 32–35 km in peak weeks) are run at about 45–75 seconds slower than race pace — comfortable but with enough distance to develop endurance. Tempo or threshold runs are 15–20 seconds faster than marathon race pace, sustained for 20–60 minutes — building lactate clearance and pacing skill. Marathon-pace runs (often 8–16 km segments within long runs) are exactly at goal race pace, training mind and body to execute the target pace under fatigue. Intervals at faster paces (5 km–10 km pace) are used sparingly but improve VO2max and running economy. The biggest mistake amateurs make is running too fast on easy days, which prevents recovery and degrades the quality of subsequent hard sessions. A pace calculator lets you set targets for each zone from your marathon goal pace, making the training plan concrete.

What's the key thing to understand about Progressive Overload and Recovery?

For sustained fitness improvements, progressive overload (gradually increasing training load over time) combined with adequate recovery is essential. The principle: the body adapts to a training stimulus, then requires a new stimulus to continue improving. Without progressive overload, fitness plateaus. Without adequate recovery, overtraining prevents adaptation and increases injury risk. Signs of overtraining: persistent fatigue, declining performance despite consistent training, increased resting heart rate, disturbed sleep, and mood changes such as irritability or loss of motivation. If these signs persist for more than a week or two, reduce training volume and intensity, prioritise sleep and nutrition, and consider a full rest week before resuming progressive overload.

Worked Example: Building a Negative-Split Pacing Plan

A runner targeting a 4-hour marathon (even pace would be 5:41/km) decides to run a deliberate negative split, starting the first half slightly conservative and finishing the second half slightly faster — a pattern strongly associated with better outcomes and reduced late-race collapse compared to starting fast and fading. A sensible plan: first 21.1km at 5:50/km (≈ 2:03:17 for the half), then aim to run the second 21.1km at 5:32/km (≈ 1:56:43), giving a total of 4:00:00 split almost evenly around a roughly 3-minute swing.

The key practical discipline is resisting the urge to bank time in the first 10km when legs feel fresh and crowd energy is high — the pace table above intentionally starts a touch slower than even pace, since the glycogen and muscular cost of running even 10-15 seconds per km too fast early is paid back several-fold in the final 10km, long after the early time 'saved' has been forgotten.

Why Even Pacing Charts Still Need Course Adjustment

A calculated even or negative-split pace chart assumes flat, still-air conditions, but real marathon courses rarely are — a net uphill final 10km (as on several well-known city courses) or a headwind section will cost real seconds per kilometre that a flat pace chart doesn't account for. Experienced racers typically adjust their planned splits around known course features in advance (slightly faster on a net downhill early section, slightly more conservative ahead of a known late climb) rather than trying to hold identical per-kilometre splits regardless of terrain, since effort, not pace, is what should stay consistent when gradient changes.

GPS Pace Accuracy and Why Splits Can Mislead

GPS watches can drift by small but accumulating margins, particularly in urban canyons, dense tree cover, or tunnels, meaning a watch's instant pace reading during a race can be noticeably less reliable than the distance markers on the course itself — pacing off the official course markers for overall split checks, while using GPS pace mainly as a smoothed guide between them rather than reacting to every momentary fluctuation, tends to produce steadier, more accurate pacing than chasing a jumpy real-time GPS number.

Converting Between Pace Units

Pace is commonly expressed as minutes per kilometre or minutes per mile, and converting between them requires multiplying or dividing by the 1.60934 km-per-mile conversion factor correctly: a pace of 5:00/km converts to roughly 8:03/mile (5:00 × 1.60934 ≈ 8:03), not simply by relabelling the unit, which is a common source of pacing confusion for runners used to one unit switching to a race or training plan quoted in the other.

Heart Rate and Perceived Effort as a Backup to Pace

GPS pace alone can be misleading on hilly or technical courses, which is why experienced marathoners often cross-check pace against heart rate or perceived effort, particularly on sections where terrain changes — maintaining a consistent effort level (and letting pace vary slightly with gradient) generally produces a more even overall performance than forcing an identical pace across terrain that genuinely isn't equal in physical demand from one section to the next.