Running Heart Rate
Understanding Your Physiological Response to the Run
Heart rate is one of the most useful physiological signals in running.
Pace tells you how fast you are moving.
Distance tells you how far you have gone.
Heart rate tells you something different:
How your cardiovascular system is responding to the effort.
This distinction matters because the same running pace can place very different demands on the body depending on fitness, fatigue, terrain, temperature, hydration, altitude, and recovery.
In simple terms:
Pace tells you what you are doing.
Heart rate helps tell you what it is costing your body.
That is why heart rate is such an important companion to pace when analyzing running performance.
What Is Heart Rate?
Heart rate is the number of times your heart beats each minute.
It is measured in:
beats per minute (bpm)
For example:
150 bpm
means your heart is beating approximately 150 times each minute.
At rest, your body's energy and oxygen demands are relatively low, so heart rate is lower.
As running intensity increases, your muscles need more oxygen and energy.
Your cardiovascular system responds by increasing blood flow.
One of the main ways it does this is by increasing heart rate.
Why Does Heart Rate Rise During Running?
Running muscles need energy.
During sustained running, much of that energy is produced aerobically.
Aerobic metabolism depends on oxygen.
Oxygen enters through the lungs, passes into the blood, and is transported to working muscles.
The amount of blood the heart pumps each minute is called cardiac output.
A simplified relationship is:
Cardiac Output = Heart Rate × Stroke Volume
where:
Heart Rate = beats per minute
Stroke Volume = amount of blood pumped with each heartbeat
As running intensity rises, the body needs greater blood flow.
Heart rate increases as part of that response.
Heart Rate Is an Internal Load Metric
One of the most useful concepts in endurance training is the difference between:
external workload
and:
internal physiological response
For running, external workload might be represented by:
- pace
- speed
- running power
- distance
Heart rate represents part of the body's internal response.
For example:
5:00 min/km
tells you the speed of the run.
But:
5:00 min/km at 145 bpm
provides much more context.
The pace tells you what the runner produced.
The heart rate tells you how the cardiovascular system responded.
Why Pace and Heart Rate Work Well Together
The relationship between pace and heart rate is often more useful than either metric alone.
Consider:
Run A
5:00 min/km → 145 bpm
Run B
5:00 min/km → 158 bpm
The pace is identical.
The cardiovascular demand is not.
Possible reasons include:
- heat
- fatigue
- dehydration
- poor sleep
- illness
- stress
- altitude
- accumulated Load
This is why heart rate helps explain how difficult a pace actually was for the athlete on that day.
Heart Rate Responds More Slowly Than Pace
Pace changes immediately.
Heart rate does not.
If you accelerate from:
6:00 min/km
to:
4:15 min/km
your pace changes within seconds.
Your heart rate rises more gradually.
The same thing happens when you slow down.
Pace drops immediately, but heart rate can remain elevated for some time.
This is called heart-rate lag.
It is one of the most important things to understand when using heart rate during running.
Why Heart-Rate Lag Matters
Heart-rate lag is particularly important during intervals.
Imagine:
10 × 1 minute hard / 1 minute easy
During each hard repetition, your pace rises immediately.
Heart rate may still be climbing when the interval ends.
During recovery, heart rate remains high even though pace has dropped.
This means heart rate is often better for understanding the physiological response to intervals than for controlling every second of the effort.
For short intervals, pace, running power, and perceived effort may be more responsive.
For longer steady efforts, heart rate becomes much more useful.
Heart Rate and Easy Running
Heart rate can be particularly valuable during easy and endurance runs.
The goal of an easy run is usually to accumulate aerobic work without creating excessive fatigue.
Suppose your normal easy run looks like:
5:45 min/km at 138 bpm
On another day:
5:45 min/km at 151 bpm
The pace is unchanged, but the physiological cost is higher.
If the purpose of the workout is easy aerobic training, it may be better to slow down.
For example:
6:05 min/km at 140 bpm
The slower pace may better match the intended training intensity.
Heart Rate and Threshold Running
As running intensity increases toward threshold, heart rate also rises toward the athlete's threshold range.
This is often represented by Lactate Threshold Heart Rate, or LTHR.
For example:
Running LTHR = 170 bpm
During a sustained threshold effort, heart rate may eventually approach values around that level.
But because of heart-rate lag, it may take several minutes to get there.
This is why pace and heart rate complement each other.
Pace controls the external workload.
Heart rate shows the internal response.
Maximum Heart Rate
Maximum heart rate, or HRmax, represents the highest heart rate an athlete can reach during maximal effort.
For example:
Maximum HR = 192 bpm
Maximum heart rate is highly individual.
A runner with a maximum heart rate of 205 bpm is not automatically fitter than one with a maximum of 180 bpm.
Maximum heart rate is influenced by age and individual physiology.
Its value is primarily as a personal reference point.
Estimated vs. Observed Maximum Heart Rate
Simple formulas such as:
220 − age
are commonly used to estimate maximum heart rate.
For a 40-year-old:
220 − 40 = 180 bpm
But individual variation can be substantial.
The actual maximum might be:
165 bpm
or:
195 bpm
For an individual athlete, credible observed data is generally more useful than a generic age-based estimate.
The distinction is important:
Lactate Threshold Heart Rate
LTHR is another important reference point.
It represents heart rate associated with sustained threshold-level exercise.
For example:
Running LTHR = 168 bpm
This value can be used to define heart-rate zones that are more specific to the athlete.
Threshold-based zones can sometimes be more useful than zones based only on maximum heart rate because they are anchored to a sustainable performance threshold.
Heart-Rate Zones
Heart-rate zones divide running intensity into ranges.
A simplified progression might include:
Recovery
Easy aerobic
Endurance
Tempo
Threshold
High intensity
The exact boundaries depend on the model being used.
Zones may be derived from:
- maximum heart rate
- lactate threshold heart rate
- heart-rate reserve
- laboratory testing
This means two platforms may assign different zones to the same heart-rate value.
The important question is:
How were the zones derived?
Why Accurate Zones Matter
If maximum heart rate or LTHR is wrong, the zones built from those values will also be wrong.
Suppose a runner's true LTHR is:
172 bpm
but the system uses:
160 bpm
A heart rate of:
165 bpm
may be classified as above threshold even though it is actually below the athlete's true threshold.
This can distort:
- zone guidance
- time-in-zone analysis
- Load
- workout interpretation
Derived metrics depend on accurate physiological reference values.
Heart Rate and Hills
Hills change the relationship between pace and effort.
A runner might move at:
5:00 min/km at 145 bpm
on flat terrain.
On a climb:
6:00 min/km at 160 bpm
The pace is slower, but the physiological demand is much higher.
This is why heart rate is particularly useful on hilly routes.
Raw pace can suggest the runner slowed down.
Heart rate helps reveal that the effort actually increased.
Heart Rate and Heat
Heat can significantly increase running heart rate.
As body temperature rises, more blood is directed toward the skin to help dissipate heat.
Sweating can also reduce plasma volume.
Heart rate may therefore rise even when pace remains unchanged.
For example:
Cool day
5:20 min/km → 140 bpm
Hot day
5:20 min/km → 154 bpm
The higher heart rate does not automatically indicate lower fitness.
It may reflect environmental stress.
Heart Rate and Dehydration
Dehydration can increase cardiovascular strain.
As fluid loss progresses, the heart may need to beat faster to maintain adequate blood flow.
For example:
Early in a long run:
5:30 min/km → 138 bpm
Later:
5:30 min/km → 151 bpm
If pace remains stable, this rising heart rate may contribute to cardiovascular drift.
Hydration is therefore important context when analyzing long-run heart-rate data.
Cardiovascular Drift
During prolonged exercise, heart rate often rises gradually even when workload remains similar.
This is called cardiovascular drift.
For example:
Early
5:15 min/km → 140 bpm
Later
5:15 min/km → 152 bpm
The runner is maintaining the same pace.
But the cardiovascular cost has increased.
Possible contributors include:
- heat
- dehydration
- reduced stroke volume
- prolonged exercise
- fatigue
- glycogen depletion
Some drift can be normal.
The amount and context are what matter.
Heart Rate and Aerobic Decoupling
Heart rate can be combined with running speed or pace to examine aerobic decoupling.
The basic question is:
For example:
First half
12 km/h at 145 bpm
Second half
12 km/h at 157 bpm
If the effort is sufficiently steady, the runner is requiring more cardiovascular effort to produce the same external output.
That suggests a deterioration in efficiency over the duration of the run.
However, decoupling should only be calculated from a suitable sustained effort.
Stops, hills, intervals, warm-up, cool-down, and noisy GPS data can distort the result.
Heart Rate and Fatigue
Fatigue can alter heart-rate response.
Sometimes heart rate is higher than normal at a familiar pace.
For example:
Normal:
5:30 min/km → 140 bpm
Fatigued:
5:30 min/km → 151 bpm
But fatigue can also produce the opposite pattern.
A heavily fatigued athlete may struggle to raise heart rate even when trying to run hard.
This means:
Heart rate must be interpreted alongside:
- pace
- perceived effort
- recent training
- sleep
- environment
- recovery
Heart Rate and Stress
Psychological stress can influence heart-rate response.
Poor sleep, work stress, travel, anxiety, and other non-training factors can change cardiovascular behavior.
This means the same run may produce a different heart-rate response even if the pace is identical.
Heart rate reflects the athlete's total physiological state, not exercise alone.
Heart Rate and Altitude
At altitude, oxygen availability is reduced.
Running at the same pace can therefore create greater physiological stress.
A runner who normally produces:
5:00 min/km at 148 bpm
at sea level might need to slow to:
5:20 min/km at 148 bpm
at altitude.
The slower pace does not necessarily represent reduced fitness.
It reflects the environmental demand.
Heart Rate and Running Economy
Running economy describes how much energy or oxygen is required to sustain a given running speed.
Heart rate does not directly measure running economy, but the relationship between pace and heart rate can provide useful practical information.
For example:
Earlier in training
5:00 min/km → 155 bpm
Later
5:00 min/km → 145 bpm
If conditions are comparable, the runner is producing the same pace with lower cardiovascular demand.
This may reflect improved aerobic fitness, improved running economy, or both.
Heart rate alone cannot identify the exact mechanism.
Heart Rate and VO₂ Max
Heart rate is often used in VO₂ max estimation.
A laboratory measures oxygen consumption directly through respiratory gases.
A running watch or training platform usually estimates VO₂ max from relationships involving:
- heart rate
- speed
- duration
- athlete characteristics
- maximal heart rate
- exercise intensity
If a runner can sustain faster speed at a similar heart rate over time, this may provide evidence of improved aerobic fitness.
But heart rate itself does not directly measure VO₂ max.
Heart Rate and Load
Heart rate can also be used to estimate Load.
A system might consider:
- workout duration
- relative heart-rate intensity
- time in heart-rate zones
- threshold heart rate
Higher-intensity periods may receive greater weighting.
This can be useful when running power is unavailable.
However, heart-rate-based Load also inherits heart rate's limitations.
Heat, dehydration, lag, fatigue, and sensor errors can all influence the estimate.
Average Heart Rate
Average Heart Rate summarizes the heart-rate values recorded across a run.
For example:
Average HR = 148 bpm
This can be useful, but it can hide workout structure.
Consider two runs.
Run A
Most of the session around: 148 bpm
Run B
Repeatedly alternates between: 120 bpm
- and: 176 bpm
Both may produce a similar average.
But the physiological structure is completely different.
Average HR should therefore be interpreted as a summary, not a complete description of the session.
Maximum Heart Rate During a Run
Activity summaries often show the highest recorded heart rate.
This can be useful, but it requires validation.
A one-second spike to:
225 bpm
should not automatically become the athlete's new maximum heart rate.
It could be caused by:
- sensor error
- poor contact
- optical artifact
- cadence lock
A credible maximum should be supported by the surrounding activity data.
Time in Heart-Rate Zones
Time in zones provides a more detailed picture of intensity distribution.
For example:
Zone 1: 12 min
Zone 2: 48 min
Zone 3: 20 min
Zone 4: 14 min
Zone 5: 4 min
This can help runners understand whether the session matched its intended intensity.
Across weeks and months, it can also help describe training distribution.
But again, accurate zones are essential.
How Is Running Heart Rate Measured?
Running heart rate is commonly measured using:
Chest straps
or:
Wrist-based optical sensors
Both approaches can provide useful data.
They behave differently.
Chest-Strap Heart Rate
Chest straps detect electrical activity associated with each heartbeat.
They are generally responsive and reliable during exercise.
They are often preferred when accurate heart-rate timing matters, especially for:
- threshold testing
- intervals
- high-intensity running
- physiological analysis
However, they can still suffer from poor contact, battery issues, or signal dropouts.
Wrist-Based Optical Heart Rate
Optical sensors use light to detect changes in blood volume beneath the skin.
They are convenient because they are built into many watches.
They often perform well during steady running.
But accuracy can be affected by:
- watch fit
- arm movement
- temperature
- vibration
- skin contact
- sensor placement
Rapid changes in intensity can also be more difficult to capture accurately.
Cadence Lock
One common optical-sensor problem is cadence lock.
The device may mistakenly detect running cadence as heart rate.
For example:
Actual HR:
148 bpm
Running cadence:
174 steps/min
The watch may incorrectly report:
174 bpm
The number can look realistic even though it is wrong.
This is why heart-rate data quality matters when the signal is used to calculate physiological metrics.
Missing and Invalid Heart-Rate Data
Running files can contain:
- missing samples
- zero values
- sudden spikes
- sudden drops
- repeated values
- sensor disconnections
- delayed acquisition
These should not automatically be treated as valid physiology.
A missing value is not the same thing as:
0 bpm
And an isolated extreme value does not necessarily represent a true heartbeat response.
A robust analysis system should validate the signal before using it downstream.
Why Data Quality Matters
Heart rate can influence many other metrics.
Poor data can distort:
- Maximum HR
- LTHR
- heart-rate zones
- aerobic decoupling
- VO₂ max estimates
- Load
- intensity analysis
One bad input can affect multiple derived outputs.
That is why credible physiological analysis begins with credible heart-rate data.
Heart Rate During Intervals
Heart rate should be interpreted carefully during interval workouts.
Imagine:
5 × 4 minutes hard
The first repetition may start with a relatively low heart rate.
By the later repetitions, heart rate may begin from an already elevated level.
The same pace can therefore produce different heart-rate patterns across the session.
This is not necessarily a problem.
It reflects:
- accumulated cardiovascular strain
- incomplete recovery
- rising body temperature
- fatigue
During intervals, heart rate is often more useful for understanding response than for controlling every second of the effort.
Heart Rate During Long Runs
Long runs provide useful opportunities to examine heart-rate behavior.
Questions worth asking include:
Does heart rate remain stable at a steady pace?
Does it drift substantially later in the run?
Can I maintain the intended aerobic intensity?
How does heat affect my response?
Does fueling reduce late-run drift?
These patterns can reveal useful information about endurance and durability.
Heart Rate During Races
Race heart rate can help explain how effort developed over time.
For example, a half marathon may show:
- controlled heart rate early
- gradual increase through the middle
- sustained high values late
- a final rise during the finishing effort
However, heart rate should not necessarily be used to force a fixed race number.
Competition, adrenaline, heat, hills, and fatigue all influence the response.
Race heart rate is best interpreted alongside pace and context.
Is Lower Heart Rate Always Better?
No.
A lower heart rate at the same pace can sometimes indicate improved efficiency.
But lower heart rate can also occur because:
- the athlete is fatigued
- the sensor is under-reading
- the effort is too easy
- medication affects heart rate
- conditions are different
Likewise, a higher heart rate is not automatically bad.
It may simply mean:
- the runner is going faster
- the course is harder
- the day is hotter
- the workout is intentionally intense
Heart rate only becomes meaningful when interpreted with context.
What Is a Good Running Heart Rate?
There is no universal good heart rate.
A value of:
160 bpm
might be:
- easy for one runner
- tempo for another
- threshold for another
- near maximal for someone else
The meaningful reference is the runner's own physiology.
Instead of asking:
“Is 160 bpm high?”
ask:
“What does 160 bpm represent for this runner, at this pace, during this type of run?”
Trends Matter More Than Single Values
One run provides limited information.
Repeated patterns are much more useful.
For example:
January
5:15 min/km → 150 bpm
March
5:15 min/km → 145 bpm
May
5:15 min/km → 139 bpm
Under comparable conditions, this may indicate meaningful improvement.
Another way to view the same progression is:
January
145 bpm → 5:25 min/km
May
145 bpm → 4:58 min/km
The runner can now produce more speed at the same cardiovascular response.
That relationship is often more useful than heart rate alone.
The Most Useful Comparison Is With Yourself
Heart-rate values vary enormously between athletes.
Comparing your heart rate with another runner's can therefore be misleading.
One athlete may race a 10K at:
178 bpm
while another races at:
162 bpm
That does not tell you who is fitter.
Their maximum and threshold heart rates may simply be different.
The most useful comparison is usually:
your heart rate relative to your own pace, thresholds, zones, and historical data.
How Should Runners Use Heart Rate?
Heart rate is most useful when it helps answer specific questions.
For example:
Is this run physiologically as easy as intended?
How does my heart rate respond at my normal endurance pace?
Is today's cardiovascular response unusual for this workload?
Does heart rate drift significantly during long runs?
Can I run faster at the same heart rate than before?
Am I spending the intended amount of time in each zone?
Does today's response fit my recent training and recovery state?
These questions turn heart rate from a display number into a meaningful training signal.
The Most Important Relationships
Running heart rate becomes more informative when combined with other metrics.
Heart Rate + Pace
Shows the cardiovascular cost of running speed.
Heart Rate + Duration
Shows how physiological strain changes over time.
Heart Rate + Threshold
Provides context for exercise intensity.
Heart Rate + Terrain
Explains why slower pace can still require greater effort.
Heart Rate + Temperature
Provides context for heat-related cardiovascular strain.
Heart Rate + Perceived Effort
Combines measured and subjective response.
Heart Rate + Historical Data
Shows how the athlete's response changes over time.
No single relationship explains everything.
The Most Important Thing to Remember
Running heart rate is a measure of physiological response.
It is not a direct measurement of:
- pace
- fitness
- fatigue
- recovery
- performance
It tells you how your cardiovascular system is responding within the context of the run.
Its meaning depends on:
pace + duration + terrain + threshold + environment + fatigue + sensor quality
Without context, 150 bpm is simply a number.
With context, it becomes a valuable signal of how your body is handling the workload.
Conclusion
Heart rate provides one of the clearest windows into the physiological response to running.
Pace tells you how fast you are moving.
Heart rate helps show how much cardiovascular effort your body is using to sustain that pace.
By examining heart rate alongside pace, duration, terrain, threshold, environmental conditions, and historical performance, runners can gain useful insight into:
- Intensity
- aerobic fitness
- cardiovascular drift
- endurance
- fatigue
- environmental stress
- adaptation over time
The most useful question is therefore not:
“What was my heart rate?”
It is:
“At this pace, for this duration, under these conditions, how did my cardiovascular system respond—and how does that compare with what is normal for me?”
That is where heart rate becomes a meaningful measure of the physiological response to the run.
KEY TAKEAWAY
- Heart rate helps tell you what it is costing your body.
- Estimated maximum heart rate is not the same as observed maximum heart rate.
- Higher heart rate does not always mean more fatigue.
- Credible physiological analysis begins with credible heart-rate data.