London Marathon median times posted

Marathon times are weirdly hard to place. You know whether you suffered, and you know whether you hit your own goal, but you usually don’t know what “normal” looked like for everyone else out there. That’s why the new London Marathon median-time breakdown landed — it gives recreational runners a real benchmark from the biggest marathon field ever, not just another blast of elite-race superlatives. And this year’s race needed that grounding, because the top end was so absurd it risked making the whole event feel unreal. (runnersworld.com) ### Why did people care about median times? Because marathon coverage usually gets hijacked by the winners. London 2026 had plenty to hijack it — 59,226 finishers, a record field, plus Sabastian Sawe running 1:59:30 and Tigst Assefa winning in 2:15:41. Those are historic numbers, but they tell almost nobody what a typical day looked like(runnersworld.com)ases. (msn.com) ### So what was the actual middle? The overall median finish time was 4:15:41. Split out by sex, the median was 3:59:06 for men and 4:39:28 for women. That came from Strava uploads representing more than 60% of London finishers, which is a big enough slice to feel useful even if it is not literally every run(msn.com)han the female midpoint. (runnersworld.com) ### Why use the median, not the average? Because marathon finishing times are lopsided. A small number of very fast runners can drag an average down and make the whole field look quicker than it really was. The median avoids that. It is basically the cleanest answer to the question most runners actually ask after a race — “where did my t(runnersworld.com)to charity runners, first-timers, and people just trying to survive the last 10K. (runnersworld.com) ### Were runners faster than last year? Yes — a bit. The 2025 medians cited in the same analysis were 4:02:19 for men and 4:41:57 for women, versus 3:59:06 and 4:39:28 in 2026. So both groups nudged quicker this year. One likely reason was weather. The race was widely described as cooler than the hotter editions that have tripped runners up before, and cooler marathon conditions usually mean fewer blowups late in the race. (europesays.com) ### Did lots of people actually run well? Turns out, yes. Strava’s breakdown said 60% of runners on the platform logged a personal best at London. That is a huge share for a major marathon, especially one this large. It suggests the race was not just fast at the front — it was a good day deep into the mass field too. That helps explain why the median landed where it did. (europ([europesays.com)s Strava data good enough for this? Good enough, with a catch. More than 60% coverage is strong, but it is still self-selected. People who use Strava are not a perfect mirror of every marathon entrant, and upload behavior can skew younger, more tech-friendly, and more training-focused. So these numbers are best read as a very solid practical benchmark, not a census-grade official statistic. (msn.com) ### What should a regular runner take from this? Basically — recalibrate your expectations. A London Marathon time does not need to start with a 2 or 3 to be impressive. In the biggest marathon ever, the middle of the field was still well over 4 hours overall. That means plenty of runners who felt “slow” were actually sitting near the center of one of the deepest mass-participation races on the planet. (msn.com) ### Bottom line The useful news here is not that London was fast. You already knew that from the headlines. The useful news is what fast looked like for everyone else — and the answer was much more human. (runnersworld.com)