Source notes

Could one unusually long run matter more than a weekly mileage total? Researchers followed 5,205 adult runners using device-recorded distances and weekly injury reports. A run more than 10% to 30% longer than the longest run in the previous 30 days was associated with a 64% higher overuse-injury hazard than the reference category. More than doubling that distance was associated with a 128% higher hazard. These are relative comparisons of injury rates, not the probability that a particular run causes injury. Week-to-week mileage changes did not show the same relationship in this cohort.

The comparison concerns one session against the longest recent session, not a weekly 10% progression rule. The study was observational, so it cannot prove that imposing a specific limit would prevent injuries. The authors also caution that increases below 10% are not necessarily safe. Several successive increases could create excessive demand even if each individual increase remained within that boundary.

How Does This Show Up in Real Life?

A runner could keep the weekly total fairly stable while concentrating much more of that distance into one long outing. This study suggests that the weekly total may then miss a relevant change. The authors recommend considering the single-session distance alongside recent running history. Their example explains why repeatedly adding 10% to successive runs is not a tested route to safety: recovery between sessions still matters. The useful application is to make the comparison explicit when interpreting training data. A watch's weekly workload score and the distance of a single run describe different things. Neither should be treated as an injury guarantee, and the paper does not provide personalized thresholds for different ages, fitness levels or previous injuries.

Injuries and their overuse or traumatic origin were self-reported. Participants were mostly men from Europe and North America and had to use a compatible running device. Distance did not capture every aspect of training stress. Although follow-up extended to 18 months, no intervention tested whether adopting the proposed session limit actually reduced injuries over that period.

Why We Cite It

Alpekin can use this paper to clarify the denominator hidden inside a progression claim. It provides a concrete basis for distinguishing a session comparison from a weekly comparison before interpreting a percentage. That helps ensure that a research result is not transformed into a different rule when translated for readers.

The finding is useful because it identifies a specific, measurable association in a large cohort. Its preventive value still needs testing. Read the proposed boundary as a research-informed consideration, with uncertainty and the broader training pattern kept visible rather than as a promise of safety.