Resting Heart Rate for Athletes: What RHR Means, What's Normal and When a Rise Matters

16 November 2026 · Myles Bruggeling

Resting heart rate for athletes: what RHR means and when a rise matters. Apple Watch measures it while you're awake; Garmin, WHOOP and Oura usually measure it while you sleep. A rise that lasts several days matters more than a single high morning

Resting heart rate is the simplest number your watch gives you. It’s also one of the easiest to misread.

RHR is how many times your heart beats per minute when you’re fully at rest. That part is simple. The tricky parts are that every device defines “rest” a bit differently, that a low number isn’t automatically a good one, and that a high morning is usually a hot room or a couple of beers rather than a training problem.

I’m in my fifties and I train for HYROX and the half marathon, and resting heart rate is one of the few numbers I look at most days. Here’s what it actually tells you, what “normal” means for an athlete, and when I think a rise is worth acting on.

Short answers

What does RHR mean? RHR stands for resting heart rate: beats per minute when you’re calm and still. In wearables it usually means the lowest stable heart rate the device sees during a quiet period, either while you’re awake or while you sleep, depending on the brand.

What’s a normal resting heart rate? The American Heart Association puts a normal adult resting heart rate at 60 to 100 beats per minute, measured sitting or lying down while calm and well. It also says a rate below 60 is common in athletes, and doesn’t always signal a problem.

What’s a good resting heart rate for an athlete? There isn’t one number. Endurance training tends to bring it down over months, so many trained athletes sit below 60. But the useful comparison is with your own usual range, measured the same way, not with a chart or a training partner.

Is resting heart rate the same as sleeping heart rate? No, and this is where most of the confusion comes from. Your heart rate is usually lowest while you sleep. Apple Watch deliberately leaves sleep out of its resting heart rate. WHOOP and Oura base theirs on your sleep, and Garmin’s usually lands there too. More on that below.

Four devices, four different “resting” heart rates

Here’s how each company describes its own number:

Four devices, four resting heart rates. Apple Watch: an estimate of your lowest heart rate at rest while awake, leaving out readings during sleep, Sleep Focus or scheduled Bedtime; one value a day. Garmin: the lowest 30-minute average in a 24-hour period. WHOOP: measured during your last period of slow-wave sleep. Oura: average and lowest resting heart rate during the night, from readings every 10 minutes
From each company's published documentation, checked November 2026. Methods can change with software updates.

So an Apple Watch resting heart rate will usually sit higher than a sleep-based one from the same person. Oura’s own member data shows how big that gap can be. In its 2026 summary of six million members, the median lowest heart rate during sleep was 55 bpm for men and 59 for women, while the median awake resting heart rate was 70.6 and 73.4. Same company, same members, roughly 15 beats apart, purely because of when it’s measured.

None of these is wrong. They’re answering slightly different questions. The mistake is comparing them with each other, which is the same trap I wrote about with HRV in SDNN vs RMSSD.

One practical tip if you wear more than one device: Apple Health can hold resting heart rate from several sources. It’s worth checking which one is feeding the number you look at (in the Health app, under the data type’s Data Sources & Access), so you’re not reading a watch on Monday and a ring on Tuesday.

And if you want a hands-on version that doesn’t depend on any algorithm, I wrote about taking your own morning resting heart rate in the first 60 seconds after you wake.

Is a lower resting heart rate always better?

Mostly, over the long run, a falling resting heart rate alongside consistent aerobic training is a sign your fitness is heading the right way. But “lower is better” has limits.

International guidelines for reading athletes’ ECGs, published in 2017, treat sinus bradycardia of 30 bpm or more as a normal, training-related finding in asymptomatic, highly trained athletes. The important word there is asymptomatic. A low heart rate with dizziness, fainting or unusual breathlessness is a reason to see a doctor, not a badge.

Two other things worth knowing:

When a rise actually matters

This is the bit that matters for training. A single high reading tells you very little. A rise that holds for several days, especially with other signs, tells you a lot more.

One high day vs several high days. An illustrative three-week resting heart rate chart with a shaded usual range. A single-day spike above the range returns to normal the next day, labelled one hot night, late meal or a couple of drinks. Later, three to four days in a row sit above the range, labelled worth a look: check HRV, sleep, how sessions feel and whether you're coming down with something
Illustrative example with made-up numbers. Your own usual range comes from weeks of readings from one device.

Things that commonly push resting heart rate up for a night or two:

That last point is worth slowing down on, because “my resting heart rate is up, I must be overtrained” is one of the most common conclusions athletes jump to. A 2008 meta-analysis by Laurent Bosquet and colleagues found that short periods of overload training (two weeks or less) produced a moderate rise in resting heart rate in competitive athletes, while longer overload periods didn’t change resting values at all. Their conclusion was blunt: the changes are small enough that they can fall within normal day-to-day variation, so heart rate only means something when you read it alongside other signs and symptoms.

In other words, resting heart rate can flag that something is going on. It can’t tell you what. I covered the HRV side of this in HRV and overtraining.

How I use resting heart rate

1. One device, compared only with itself. I don’t compare my watch with my ring, or my number with anyone else’s. If I change device, I treat it as a fresh start and give it a few weeks.

2. I watch the trend, not the morning. One high reading after a late dinner or a hot night gets ignored. Several days above my usual range gets my attention.

3. I read it with other signals. A higher resting heart rate with lower HRV, worse sleep and sessions that feel harder than they should is a pattern. Resting heart rate on its own is just a number. If you’re new to HRV, there’s a short glossary entry on HRV and why the trend matters more than today’s number.

4. A rise with symptoms is an illness question first. Sore throat, feeling flat, heart rate up for a few days: I swap intensity for easy work or rest, and if it doesn’t settle or I feel unwell, I’d rather ask a doctor than push through.

5. I keep it in its lane. Resting heart rate also feeds into heart rate zone methods that use heart rate reserve, alongside your max heart rate. For that job I want a stable, typical value, not this morning’s reading.

For the short definition, see the resting heart rate glossary entry.

Where P247 fits

P247 reads your health data from Apple Health, plus your workouts from Strava if you choose to connect it. So the resting heart rate it sees is whatever is in Apple Health, which for most people is Apple Watch’s awake-only estimate.

For heart rate calculations, P247 uses a rolling 30-day median of your morning readings, so one odd morning doesn’t move it much. Resting heart rate is also one input to P247’s daily recovery score, which is built on fixed rules rather than AI. To be upfront about a limitation: in that score it’s currently rated against a fixed reference value, not against your own baseline, which is the approach I’ve argued for in this post. The weekly report does look at HRV and resting heart rate together when judging whether recovery kept up with training.

I’m still building P247 and writing up what I learn along the way. If that’s useful, you can read more at p247.io.

This is general information, not medical advice. Consumer wearables aren’t diagnostic devices. If your heart rate is unusually high or low for you, especially with symptoms such as chest pain, dizziness, fainting or shortness of breath, see a doctor.