How Much Running Is Too Much? A Paradigm Shift in Running Injury Risks

How Much Running Is Too Much? What a 5,200-Runner Study Reveals About Injury Risk

For decades, runners have been taught that overuse injuries are a slow burn. The body breaks down little by little, the story goes, until one day your Achilles flares or your IT band revolts. But what if that story is wrong?

A study out of Aarhus University is poking a hole in the old narrative, and it's a big one. With over 5,200 runners and more than half a million logged runs, this is the largest study of its kind. The headline? It may not be your gradual weekly mileage increases that break you. It might just be that one run you weren’t ready for.

The Study

Titled "How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study" and published in the British Journal of Sports Medicine, this research tracked runners for 18 months using Garmin devices. It looked at three types of training spikes:

• Single-session spike: A run that was significantly longer than anything else you’d done in the past 30 days.

• Week-to-week spike: A jump in mileage from one week to the next.

• Acute Chronic Workload Ratio (ACWR): Comparing one week's load to the average of the last three weeks.

The result? Only one of these was reliably predictive of injury: single-session spikes.

Injury Risk Goes Up Fast—Like, Really Fast

If you went just 10-30% beyond your longest recent run, your injury risk jumped by 64%. A run that was double your longest? Risk more than doubled. The scariest part: injury risk increased with as little as a 1% jump.

Read that again.

This isn't just about new runners ramping up too fast. Even experienced runners in the study were more likely to get hurt after a big single-day spike. The old assumption that consistent weekly mileage growth is the big risk? Not so much. In fact, weekly spikes and ACWR didn’t show any consistent link to injury.

Instead, injuries happened during or right after one-off runs that pushed well past what the runner had been doing.

Are Our Training Rules... Wrong?

This research challenges one of running's most beloved commandments: the 10% rule.

The 10% rule says: Don’t increase your mileage by more than 10% each week.

This study says: That might not matter as much as what your biggest run looks like compared to your recent history.

It makes sense when you think about it. You can increase your weekly mileage by 5% but still throw in a Sunday long run that blows past your previous longest run. And boom—that’s the run that breaks you.

Rasmus Nielsen, the lead researcher, has been blunt: "Many injuries occur because runners make training errors in a single session."

So the idea that injury is a long fuse? That might be part of the story. But the actual injury? That’s the match. And more often than not, it gets lit by one ill-advised run.

What About ACWR and Training Load?

Now, if you're someone who watches your ACWR like a hawk or has a Garmin watch yelling at you about overreaching, this next part might sting.

The study found that ACWR, the ratio of your current weekly load to your past three weeks, wasn't a good predictor of injury. In fact, higher ratios were sometimes linked to lower injury risk. Yep. Lower.

How does that happen? Well, more experienced runners can usually handle a bigger spike because their baseline capacity is higher. But even for them, a massive one-day effort could be risky.

And this brings us to an important point for the data-minded among us:

Is This Just About Distance?

Nope.

While this study focused on running distance, the principle likely applies to any kind of training load. That includes TRIMP (Training Impulse), heart rate stress, intensity, terrain, surface, and even shoes.

• Crushing a new tempo run when you haven’t done speed in weeks? Spike.

• Going from treadmill to hilly trail without building in adaptation? Spike.

• Jumping into new shoes that alter your biomechanics and doing a long run? Spike.

So it’s not just how far you go. It’s how far out of your current capacity you go, in any direction.

What Should Runners Do Instead?

Alright, here’s where we put this into practice. What does this mean for how you structure your training?

1. Watch the Long Run Like a Hawk

That weekend long run isn’t just another session. It’s the one most likely to trigger injury if you get greedy. Aim to increase your long run by no more than 5%, not 10-20% like many plans suggest. If you’re jumping from 10 to 14 miles in a week? That’s a red flag.

2. Flatten the Spikes

Look at your training log. Are there any single runs that are way longer or harder than the rest? That’s your injury risk. Flatten those out. Consistency beats drama.

3. Rethink How You Measure Load

Instead of just counting miles, consider how stressful a run was. Track your rate of perceived exertion (RPE), use heart rate-based load metrics like TRIMP, and note when things feel significantly harder or different than usual.

4. Ease Into New Stressors

Want to add hills, trails, new shoes, speedwork? Great. Do it slowly. And don’t stack all those changes at once. Respect the load each of those puts on your body.

5. Don’t Trust the Watch Alone

Your sports watch might say you’re "in the green." But it doesn’t know you just did a run that was 50% longer than anything else in a month. Tech is useful—but it’s not that smart.

6. If It Hurts, Don’t Ignore It

If pain crops up right after a big run, don’t push through. That’s your body waving a flag. Early intervention matters more than perfect weekly progression.

Final Thought: It's Not Always the Mileage

Injuries don’t always come from obvious overtraining. Sometimes, it’s just that one run that your body wasn’t ready for. And that might mean it's time we rethink how we talk about training errors, overuse, and "doing too much."

Because if your plan says it’s time to go long, but your body says, "Hey, we’ve never done this before," you might want to listen.

Not to fearmonger. But to stay in the game.

So no, everything we thought about running injuries isn’t wrong. But it’s incomplete. And thanks to this study, we just got a whole lot closer to the full picture.