Does being on pace mean you will hit your goal?

This window includes runners just ahead of and just behind the target; it is narrower than the older core table’s time-budget definition. Results pool editions and are descriptive historical frequencies, not a validated personal forecast. Goals are inferred benchmarks, not runners’ declared intentions.

Use complete, strictly increasing elapsed checkpoints at 3.11, 6.21, 9.32, 12.43, 15.53, 18.64, 21.75, 24.85 and 26.22 mi. Clock strings must parse as H:MM:SS or M:SS. No missing splits are interpolated.

Remove exact duplicate race records, ignoring database IDs, ingestion timestamps and source URLs. Retain finishes from 90 minutes to 12 hours with every section between 3.22 and 32.19 minutes/mi. These quality filters can exclude genuine unusual performances; the analysis describes this eligible cohort, not every entrant.

Each observation is a race finish. The same person can appear in multiple races. No runner identities are linked across races. Public cells require at least 100 observations; matched comparisons additionally require at least 20 per group in each stratum.

Apply the reviewed source-quality edition exclusions for this exact export after the timing checks. Known invalid split grids, incomplete ingestion, unreconciled HOLD editions and a selected top-finisher field do not contribute to the analyses or prior benchmarks. Report source exclusions separately; an already invalid timing row is not counted twice. Missing age or recorded gender alone does not exclude an otherwise eligible finish from the overall cohort. Other sparse editions are not declared incomplete merely from their size.

Marathons, years and recorded data. Chart samples may be smaller than the eligible analysis cohort.