Sub-four-hour marathon: pace, splits and the final kilometers

Calculate the four-hour boundary

Four hours is 14,400 seconds. Dividing by 42.195 km gives approximately 341.27 seconds per kilometer, or 5:41.27. Exactly four hours is the boundary; a sub-four-hour result must be quicker.

The example below uses 3:59:00 to illustrate a target with an explicit finish time. Its average is approximately 5:39.85 per kilometer. This choice is arithmetic, not a recommendation to use a particular margin or an assessment of whether the target suits your preparation.

Keep the finish in the checkpoint table

After 40 km, another 2.195 km remains. At the example's exact average, that section takes about 12 minutes 26 seconds. A sheet ending at 40 km leaves an important part of the target unstated.

Generate cumulative times from unrounded values

Rounding the pace to the nearest second and multiplying it by every kilometer can produce a final time different from the original target. Instead, calculate each cumulative checkpoint from the exact target divided by the complete distance, then round the displayed checkpoint.

The race-splits tool includes partial final segments and preserves the requested rounded finish time. If you print the sheet, label its units and target. Do not interpret a planned negative split as an outcome the arithmetic can ensure.

Check the kind of evidence behind the target

A recent shorter race can inform a prediction, while the volume history describes a different part of preparation. Neither a printed pace nor a volume score establishes that a particular marathon performance will occur. Keep route, timing and actual activity data available when reviewing the result afterward.

Runome separates race-related analysis from its volume-focused Marathon Shape. Work through the eight-week volume example and prediction sensitivity to understand what each contributes. Use the pace sheet to make a chosen target readable, rather than asking it to prove the target is appropriate.