Plenty of triathletes set one zone 2 heart rate and use it everywhere: same number on the bike, same number on the run, same number for every easy session in between. Then the ride feels suspiciously comfortable while the legs burn out before the watch says anything, or the recovery run somehow drifts ten beats past where it should be. Neither of those is a fitness problem. It’s what happens when zone 2 running vs cycling gets treated as one number instead of two.
TL;DR: Zone 2 on the bike and zone 2 on the run aren’t the same heart rate, and using one number for both is a common way triathletes end up either riding too hard or running too easy. The size of the gap depends on physiology more than fitness, and it’s worth knowing before it quietly wrecks a training block.
Key Takeaways
- Cycling zone 2 heart rate usually sits several beats below running zone 2, often by 5 to 15+ beats depending on the person
- The gap comes from how much muscle mass is working and how the body handles blood flow in each position, not from being unfit on the bike
- A flat “subtract 10 beats for cycling” rule is a reasonable starting point, not a substitute for testing
- Using running zones on the bike usually means overcooking every ride; using bike zones on the run usually means underloading every easy run
- Testing running and cycling separately is the only reliable way to know actual numbers for each
Why the Same Zone 2 Feels Different on Two Machines
The short version: running and cycling put different demands on the body at the same heart rate, so zone 2 running vs cycling was never going to line up perfectly. Running is a full-body, weight-bearing effort. Arms, core, and stabilizing muscles are all working alongside the legs, and every stride involves an impact the body has to absorb and recover from. Cycling is seated and far more localized to the quads and glutes, which means less total muscle mass is recruited for the same relative effort.
A 2009 review of triathlete physiology found that fitness built through running tends to carry over to cycling better than the other way around, which is part of why athletes who came up as runners often see the biggest bike/run heart rate gap until they build cycling-specific strength (Millet, 2009). Sitting down also reduces how hard the body has to work to return blood to the heart, and airflow on the bike generally cools better than the heat a runner generates pounding pavement. Put together, those factors let most people hold a given effort on the bike at a lower heart rate than the equivalent effort running.
What the Actual Numbers Usually Look Like
Most reference sources put running lactate threshold heart rate somewhere around 5 to 10 beats above cycling threshold heart rate, but that range is a rough average, not a rule. It also isn’t fixed. A study comparing lactate threshold heart rates across dedicated cyclists, runners, and triathletes found the treadmill-vs-bike gap was small and not statistically significant for cyclists, but real and significant for runners and triathletes.
In other words, the athletes who train the bike the least tend to show the biggest gap, and the ones with real cycling strength close it. That’s consistent with what shows up anecdotally in triathlon forums: the mismatch is at its worst for run-background athletes who haven’t put in bike-specific work (UW-Madison, lactate threshold study).
Here’s what that looks like as a worked example, using a hypothetical runner with a tested running threshold heart rate of 165 bpm and a cycling threshold roughly 10 beats lower. This is an illustration of the pattern, not a formula to apply to your own numbers:
| Zone | Running | Cycling |
|---|---|---|
| Zone 1 | Under 140 bpm | Under 128 bpm |
| Zone 2 | 140-155 bpm | 128-143 bpm |
| Threshold | ~165 bpm | ~155 bpm |
Note: illustrative example only, based on a hypothetical 165 bpm running threshold.
Should You Just Use Power Instead of Heart Rate on the Bike?
There’s a second reason cycling and running numbers don’t line up cleanly, separate from the physiology above: heart rate itself behaves differently as a signal on the bike. It lags a few seconds behind a change in effort, and on longer steady rides it drifts upward even when power output stays flat, a well-documented effect called cardiac drift. That makes heart rate a slightly noisy way to stay in zone 2 on the bike specifically.
Power doesn’t have that problem. 150 watts is 150 watts in minute one or minute three, regardless of heat, fatigue, or how long the ride has gone. That’s why a lot of coaches treat power as the primary number for staying in zone 2 on the bike and use heart rate as a secondary check on how that output is landing physiologically that day. Running doesn’t have as clean an equivalent yet. Foot pods and running power meters exist, but the underlying standard is nowhere near as settled as it is for cycling, so pace and heart rate remain the more trusted combination for run zone 2. If a power meter is on the shopping list and the bike vs. run split matters, the bike is where it earns its keep. The Favero Assioma PRO RL review covers what a mid-range power meter actually adds once it’s on the bike.
Where Triathletes Get This Wrong
The most common mistake is carrying one number across both sports. Apply a running zone 2 heart rate to the bike and most people end up riding at what is actually zone 3 or 4 effort for cycling, which turns an aerobic base ride into a session that needs a full recovery day. Flip it around and apply a cycling zone 2 number to running, and most runs end up well below actual aerobic capability, which wastes training time without building anything. Both mistakes get covered from the running side in Easy Runs Too Fast, and the broader “one zone fits all” assumption is one of the ones taken apart in Zone 2 Training Myths.
The Gap Isn’t Fixed, Retest as Cycling Fitness Changes
The running/cycling gap shrinks as bike-specific fitness builds, and it can move faster than most triathletes expect. An athlete coming off a winter with barely any bike volume might see a 15+ beat gap in February, then find it’s down to 5 to 8 beats by peak season, with running fitness barely changed in between. That’s not a bad test or a fluke. It’s the bike catching up to the level of strength and efficiency the legs already have from running.
The practical takeaway is to retest cycling zones a couple of times a season, especially after a block with real bike volume in it, rather than setting a number in the winter and assuming it holds. The same logic that applies to periodic threshold retesting generally applies here, just bike-specific: Threshold Testing for Triathletes walks through when and how often that’s worth doing.
Finding the Real Numbers for Each Sport
The only way to know the actual gap is to test running and cycling separately rather than testing one and estimating the other. The field test process is the same either way: it’s covered step by step in How to Find Your Zone 2. Measurement accuracy matters more at this end of the intensity range too, since easy efforts are exactly where wrist-based optical sensors tend to drift the most. Wrist HR vs. Chest Strap has the data on where that gap shows up.
Find Your Real Zone 2
Stop guessing at a flat number for both disciplines. Our HR Zone Finder Calculator works out sport-specific zones from your own numbers.
FAQ
Q: Do I need a different zone 2 number for swimming too?
A: Probably, and it complicates things further since swimming is horizontal and tends to produce lower heart rates for the same relative effort. Treat swim zones as their own case rather than assuming either running or cycling numbers carry over.
Q: Is the “subtract 10 beats” rule ever accurate enough to just use?
A: As a placeholder when testing isn’t possible, it’s fine. As a permanent substitute for testing, no. The real gap ranges from a few beats to 20 or more depending on training background, and the only way to know an individual number is to test.
Sources / References
