NUMBERS IN THE NEWS / Sports & running
NYC Marathon winner averaged 4:48 per mile
4:48 per mile, or 2:59 per kilometre, for a full marathon. Put Andreas Almgren’s New York win beside your own pace and finish time.
THE TAKEAWAY
Try holding a 2:59 kilometre, then imagine averaging it for a marathon. That is the scale of Almgren’s winning run. Your finish time turns the comparison into a personal gap, without treating a champion’s performance as your training target.
A whole marathon at a short-run pace
Andreas Almgren won the men’s race at the New York City Marathon on November 1, 2026, in 2:06:01, according to World Athletics. It was his marathon debut.
To put that observed result into a distance you can picture, divide the finish time by the standard marathon distance of 42.195 km. The result is just under three minutes per kilometre. At the same average, five kilometres would take 14:56, rounded to the nearest second. In miles, the same 26 miles 385 yards works out to about 4:48 per mile.
Those are modeled averages across the entire distance. They describe the scale of the performance, not his actual kilometre-by-kilometre splits. A runner can cover faster and slower sections and still finish with that average.
WORK THE NUMBER
How much of a head start would you need?
Modeled example: you finish the same marathon distance in four hours. Compare elapsed times, with no claim about anyone’s future performance.
| Input or result | Amount |
|---|---|
| Marathon distance | 42.195 km |
| Observed winning time | 2:06:01 |
| Modeled average per mile | 4:48 /mi |
| Modeled average per kilometre | 2:59 /km |
| Modeled 5 km at that average | 14:56 |
| Your assumed finish time | 4:00:00 |
| Head start to finish together | 1:53:59 |
2:06:01 = 7,561 seconds. Average pace = 7,561 ÷ 42.195 = 179.1918 seconds/km, or 7,561 ÷ 26.2188 miles = 288.38 seconds/mile. Multiply the unrounded pace by 5 for 14:55.9592. Head start = 4:00:00 − 2:06:01 = 1:53:59. Displayed pace and modeled splits round to the nearest second; they are not recorded race splits.
Compare your running paceYour own finish time makes the gap real
Suppose your marathon takes four hours. That is a chosen example, not an average runner or a recommended goal. You would be on the course 1:53:59 longer than Almgren’s winning elapsed time. In a simple same-distance thought experiment, that is the head start you would need for both of you to finish together.
Change the assumed finish time and the gap changes second for second. For a finish longer than 2:06:01, subtract the winning time from yours. At exactly 2:06:01, the gap is zero. A shorter finish time puts you on the faster side of this arithmetic comparison; it does not establish a race result.
Use elapsed finish times on the same distance. Comparing a watch’s moving time with an official finish time can remove stops from one side of the calculation. Terrain, weather and race conditions also matter when comparing separate events. This is a time comparison, not a performance prediction.
Recreate the pace, then enter your own run
In the Running Pace Calculator, leave Solve for set to Pace, select km, and choose the Marathon race preset. Check that Distance reads 42.195. Enter 2 in Hours, 6 in Minutes and 1 in Seconds. Pace / km should show 2:59 /km, and Pace / mile 4:48 /mi.
Then replace those time fields with your own finish time. For a shorter run, use the 5K preset or Custom and enter its distance. The result shows the pace you actually averaged over that distance. It does not predict how long you could maintain it.
Keep full precision until the final display. Multiplying the rounded 2:59 pace by the marathon distance loses the fraction of a second in every kilometre; it will not reconstruct the original finish time exactly.
Make it your number
Use the Running Pace Calculator to put your own distance and elapsed time beside the winning average. Start with the Marathon preset in km to reproduce this example, then enter your own run. For the head-start gap, the Time Duration Calculator can subtract 2:06:01 from a longer finish time entered as a clock time. It treats an equal time as a full day and a faster time as running past midnight, so use it only when your finish is slower than 2:06:01.
Keep calculating: Running Pace Calculator · Time Duration Calculator · Speed Calculator
Compare your running paceSources & context
Data period: November 1, 2026 New York City Marathon; men’s winning elapsed time, as reported November 1. Source checked November 2, 2026. This article preserves the release vintage; later estimates may differ.
- World Athletics — New York marathon race report and leading results
Released November 1, 2026. Exact men’s results row: “Andreas Almgren (SWE) 2:06:01”. The report is dated “01 Nov 2026” and describes a marathon debut. Basis: observed men’s race winner, New York, November 1; elapsed h:mm:ss, not a pace or a split. NumberBench converts that to 7,561 seconds. Modeled average: 7,561 / 42.195 = 179.1918 seconds/km; modeled 5 km = 895.9592 seconds. Display rounds to 2:59/km and 14:56. The four-hour comparison is an explicit invented example, not a population statistic: 14,400 − 7,561 = 6,839 seconds, or 1:53:59.
- World Athletics — Marathon distance definition
Source accessed November 2, 2026. Exact distance clause: “athletes run a distance of 26 miles and 385 yards (42.195km).” Basis: standard marathon course distance, 42.195 kilometres; not rounded 26.2 miles, a GPS track or a runner’s individual line. Undated reference page, accessed November 2. All intermediate pace arithmetic uses 42.195 km and unrounded seconds. Mile pace: 26 miles 385 yards = 26.21875 miles; 7,561 / 26.21875 = 288.3814 seconds/mile, displayed as 4:48 per mile (modeled average).
Examples and graphics are NumberBench calculations or illustrations, labeled above. How we calculate · Report a correction