Heart Rate Too High While Running Slowly? Why Effort and the Number Don't Match

Impressionist-style painting of a group of people in colorful clothing along a grassy lakeshore, with blue water and green trees behind.
A heart rate of 170 beats per minute on a run that feels slow is almost always down to one of three things: your running-specific aerobic base (the endurance you have built specifically for running) hasn't caught up to your overall fitness, fatigue from other training is stacked onto the run, or your true maximum heart rate sits higher than the age-based formula estimates. Neither means something is wrong. Below: the three causes (running-specific deconditioning, stacked cross-training fatigue and a higher real maximum), a simple way to judge your own number, and the signs worth getting checked.

Slow down to chase a lower number and you risk losing the very running that would bring it down. I see this most with triathletes and gym-fit newcomers, who assume a high reading means they are unfit when it usually means they are early. Let's work out which cause is yours.

Cause 1: Running-Specific Aerobic Deconditioning (Even If You're Fit Elsewhere)

Two women in white tops running side by side across a grassy field with colorful mountains behind them.
Running typically produces a higher heart rate than cycling or swimming at a comparable perceived effort. You carry your full bodyweight upright and recruit more muscle, so your heart has more to supply: maximum heart rate is commonly 5-10 beats higher in running than in cycling.

That's why a triathlete, a cyclist, or someone who's genuinely gym-fit can still show a disproportionately high running heart rate. Your overall aerobic fitness is real. Your running-specific fitness just hasn't caught up yet, and that's not a red flag.

I regularly see triathletes and gym-fit athletes whose running heart rate runs 10-15bpm higher than someone of equivalent overall fitness, purely because their running-specific base hasn't caught up. It closes over 8-12 weeks of consistent easy running, not overnight.

The fix is simple to state, harder to accept: more easy running volume at a truly conversational pace, even if that means going slower than "slow" already feels. The run/walk method does exactly this. It just does it without the reason attached. Now you've got the reason.

Cause 2: Cross-Training and Multisport Load Stacks Fatigue Onto the Run

A run performed on residual fatigue from other sessions will show a higher heart rate at a given pace than a fresh run. This is especially true of a brick: a run stacked straight after a bike. Accumulated fatigue, mild dehydration, and a core temperature that's already elevated from the earlier session all push your heart rate up, independent of running effort.

Reader example: brick runs on a Half Ironman plan

Take a typical example: 7-9 workouts a week for a Half Ironman, running up to four miles on a fresh day but only a mile after a 16-mile bike ride. The pace is a steady 12-minute mile throughout, and heart rate only comes down to about 155 running downhill, three miles in. Two very different heart rates for the same pace, because one run started fresh and the other didn't.


Expect the brick mile to run meaningfully higher at the same pace than the fresh miles. That's expected, not a fitness failure. The practical adjustment: treat brick-run heart rate as its own, higher baseline rather than judging it against a fresh-legs number. Where your stacked training schedule allows it, sequence at least one pure, non-stacked easy run a week. That's the one that actually tells you where your running fitness stands.

Cause 3: Your Real Max Heart Rate May Be Higher Than the Formula Says

Woman in pink sports bra and black shorts running along a lakeshore with rocks, in bright teal and pink tones.
The standard 220-minus-age formula is a population average, and it comes with a wide error margin, often ±10-15bpm in practice. If your heart rate reliably reaches or exceeds the formula's estimate during easy, sub-maximal running, your true max is likely higher than the formula says. That's not evidence something's wrong.

Rather than chasing a formula-based number, use the conversational-pace test: if you can hold a conversation in short sentences, the effort is appropriate, regardless of what the number on your wrist reads. Simple. Reliable. And it doesn't need a calculator.

If you want certainty rather than an estimate, a professional max heart rate or maximal oxygen uptake (VO2) test is the only way to get a precise figure. For the calculation methods most of us use day to day, go find your real max heart rate.

Putting It Together: A Simple Way to Judge Your Own Number

Three causes, one simple way to work out which applies to you:

Situation Likely Explanation What to Do
Fresh easy run, heart rate still high Running-specific aerobic deconditioning More easy-pace running volume, even slower than feels necessary: see Cause 1 above
Run stacked after another session or a heavy training week Stacked fatigue (a brick effect) Judge it against its own baseline, not a fresh-legs number: see Cause 2 above
New to running, first 2-3 months Early-stage fitness, plus a formula that can be 10-15bpm off Use the conversational-pace test instead of the raw number: see Cause 3 above

When a High Heart Rate Is Actually Worth Checking Out

Everything above is normal and explainable. This isn't.

See a doctor or get a professional assessment if a high reading comes with chest pain, dizziness, or unusual breathlessness that's out of proportion to your effort, or if your heart rate simply doesn't come back down with rest. A sudden, large jump in your resting or easy-pace heart rate (as opposed to a gradual, explainable one) is also worth flagging. Better safe than sorry.

If what you're actually experiencing is a heart rate that climbs as the run goes on rather than being high from the very first minute, that's a different pattern: see heart rate climbing mid-run instead of at the start. And if the high numbers show up outside running too, that points elsewhere: see a high heart rate outside of running specifically.

Frequently Asked Questions

Why is my heart rate still high even though I'm running slowly?

Almost always running-specific aerobic deconditioning, stacked fatigue from other training, or a true max heart rate higher than the age-formula estimate: see the three-cause breakdown above.

I've only been running a few weeks and my heart rate reads in Zone 5 (170+): should I be worried?

Not usually. New runners often see a high formula-relative percentage early on, and the age-based max heart rate formula can be off by 10-15bpm in either direction. Use the conversational-pace test rather than the raw number, and get a professional test if it persists past a couple of months.

Does training for a triathlon (or heavy cross-training) make my running heart rate higher than it "should" be?

Yes, especially on a run stacked after cycling or another session. Treat that as its own, higher baseline rather than comparing it to a fresh-legs number.

How do I know if my real max heart rate is higher than the standard formula says?

If you reliably reach or exceed the formula's estimate during easy, sub-maximal running, your true max is probably higher: the formula has a wide margin of error. A professional test gives you a precise number.

When should I actually worry about a high heart rate and see a doctor?

If it comes with chest pain, dizziness, breathlessness out of proportion to effort, doesn't recover with rest, or jumps suddenly rather than gradually.


A high number on a slow run rattles you the first time you see it. But it's rarely the number that matters. It's whether it fits a pattern you can explain. Work out which of the three causes above is yours, apply the fix, and give it the 8-12 weeks it actually needs. Or head back to heart rate training basics if you'd rather start from the ground up. If your problem runs the other way, I've covered that too: heart rate seems too low instead?

Some Other Pages You May Like


Heart Rate Zones for More Experienced Runners Heart Rate So High When You Run? Here's Why (And When to Actually Worry) Why Is My Heart Rate Too Low When Running? Why Can't I Stay in My Heart Rate Zone? Warning Signs You're Returning Too Fast Training Harder But Racing Slower? Tired Legs After Running? 5k Running Tips


Home > Running Training > Heart Rate Training for Runners > Heart Rate Too High While Running Slowly?

About the author

Dominique de Rooij

Dominique de Rooij (Dom)

Advanced Running Coach certified by Athletics Australia with 20 years of writing about running and over a decade coaching runners, from first races to marathons. Dom created PlanMyRace, a training plan generator for any race from 1500m to the marathon. Now over 50, Dom still loves trail running, parkrun, and the coffee after.



Now Live · PlanMyRace by Best Running Tips

Stop Guessing.
Train for Your Best Race.

PlanMyRace builds a personalized, week-by-week training plan for any race from 1500m to the marathon, around your race date, your current fitness and the week you actually have.

Get My Free Plan →

No credit card needed. Your full first week is free.


What's New?

  1. Cut 90 Seconds Off Your 1.5 Mile Run for the Army Test

    Cutting 90 seconds off a 1.5 mile run in 3-4 weeks for the Army test: Dom breaks down realistic pacing to reduce 10:32 toward sub-9:00 for Paras selection.

    Read more

  2. Training for a 1.5 Mile Run - How to Qualify For Your Test

    Coach Dom's 3-step plan for 1.5 mile run training: build aerobic base, add strides, then tempo and pace work to hit your test time.

    Read more

  3. Improve Your 1.5 Mile Running Time to 10:30: Shin Splints

    From 12:59 to 10:30 for 1.5 miles: Coach Dom's shin-splint fix and training plan to improve your running time in 2-3 months.

    Read more


More New Posts →