Resting Heart Rate

The most cardiovascular-fitness-correlated daily metric - lower typically indicates better trained aerobic capacity.

What Resting Heart Rate Measures

Resting heart rate (RHR) is the number of times your heart beats per minute at rest. It's inversely correlated with aerobic fitness - endurance training lowers it over months to years. RHR in the 50s and low 60s is common in well-trained individuals. RHR persistently over 70 warrants attention, and over 80 is meaningfully elevated.

Like HRV, the individual trend matters more than absolute values. A 5–10 bpm rise from your personal baseline for multiple days is a reliable signal for something wrong - most commonly illness incubation, overtraining, acute stress, or alcohol the prior evening.

Oura and Apple Watch both deliver reliable RHR during sleep. Fitness bands like Fitbit and Garmin also work. Manual measurement first thing in the morning (before standing up) is a free option.

What Affects This Biomarker

RHR is influenced by: aerobic fitness level (primary driver - lower = better-trained), acute illness (rises 5–15 bpm), sleep debt, alcohol, caffeine, stress hormones, hydration status, and pharmacologic agents - beta-blockers lower it; stimulants raise it. Pregnancy and thyroid dysfunction also shift RHR.

In the Context of Peptide Protocols

On GH peptides, RHR sometimes rises slightly (2–5 bpm) as metabolic rate increases - not concerning. On GLP-1s, RHR typically drops as weight and insulin resistance improve. On retatrutide specifically, a 4–6 bpm RHR elevation has been observed in trials and warrants monitoring in cardiovascular patients. Acute RHR spikes of 10+ bpm from baseline usually signal illness.

Deep Dive

Why resting heart rate is the cleanest single fitness marker

Resting heart rate (RHR) is the simplest measurable proxy for aerobic fitness. Every time the heart beats, it pumps a fixed stroke volume of blood per contraction. As aerobic capacity improves with training - the heart's left ventricle adapts to pump MORE blood per beat - the same total cardiac output can be achieved with fewer beats per minute. A trained endurance athlete's heart simply has to work less hard to circulate the same amount of blood, so the resting rate drops.

This is why elite endurance athletes commonly have RHRs in the 30s and 40s (Lance Armstrong reportedly 32, Miguel Indurain 28). For most adults, an RHR in the 50s-60s indicates good aerobic conditioning, 60-70 indicates average, 70-80 is below-average, and 80+ warrants attention.

The Framingham Heart Study (Kannel et al., 1987) established that elevated resting heart rate is independently associated with cardiovascular mortality, even after adjusting for blood pressure, smoking, cholesterol, and diabetes. Each 10 bpm increase in RHR was associated with a 16-22% increase in all-cause mortality risk over decades of follow-up. This makes RHR one of the more powerful single-number prognostic markers in clinical medicine.

What changes RHR (and what doesn't)

**Lowers RHR reliably:** - Aerobic training (most reliable - 5-10 bpm reduction over 6-12 months of consistent training) - Weight loss - Sleep optimization - Stress reduction - Beta-blockers (often 10-15 bpm reduction - but this is artificial, not fitness-driven) - Calcium channel blockers (non-dihydropyridines like verapamil) - Some SSRIs

**Raises RHR (acutely or chronically):** - Illness incubation (often the first sign, 24-48 hours before symptoms) - Sleep deprivation - Alcohol the prior evening (one drink = 3-5 bpm rise the next morning; heavy drinking = 10-15+ bpm rise) - Caffeine - Dehydration - Acute stress / anxiety - Stimulants - Thyroid hormone (T4/T3) - Anemia - Pregnancy (15-20 bpm rise by third trimester) - Overtraining syndrome - Fever (10 bpm per °F above 98.6)

The "rises before symptoms" early-warning property

One of RHR's most useful properties is that it rises 24-72 hours before most people consciously feel sick. Your immune system mounting a response to a viral or bacterial infection creates a low-grade inflammatory state that elevates heart rate while the host still feels "fine." Oura, Whoop, and similar wearables exploit this property explicitly - "your readiness is low today" notifications often catch the pre-symptomatic phase.

This is also why a sudden 8-12 bpm rise from personal baseline, without explanation, is a reliable signal to back off training, hydrate, sleep, and prepare for illness. Pushing through that signal frequently turns a 3-day cold into a 10-day one.

The personal-baseline rule

Unlike HRV (where absolute values are highly individual), RHR has population norms that are useful. But for protocol tracking, the personal-baseline rule still dominates: - Most useful daily metric: deviation from your personal 14-day rolling average - Useful weekly metric: rolling 7-day average vs prior 7-day average - Useful monthly metric: trend line over 3-6 months

A 5+ bpm rise vs personal baseline lasting more than 3 days = something is wrong. A gradual downward trend over weeks = training adaptation is happening. A gradual upward trend = something chronic is shifting (overtraining, weight gain, stress, sleep debt, hidden inflammation).

Device methodology and accuracy

Different wearables measure RHR slightly differently:

**Oura Ring**: Measures continuously through the night using PPG (photoplethysmography) and reports the lowest 5-minute average during sleep. This "minimum nighttime HR" is the most consistent measure across people and the most useful for trending. Highly accurate against ECG comparison (~98% in adult studies).

**Apple Watch**: Reports a "resting heart rate" calculated from periodic measurements throughout the day. Slightly higher and noisier than Oura's nighttime minimum because it's not measuring during true rest.

**Whoop**: Similar to Oura - measures during sleep, reports the average minimum. Slightly higher than Oura by 1-3 bpm in head-to-head comparisons.

**Polar / Garmin chest straps**: Most accurate (ECG-based), but typically only worn during workouts, so not used for resting baseline.

**Manual measurement**: First thing in the morning before standing up, count beats for 60 seconds (not 15 × 4 - too imprecise). Reliable if done consistently.

For protocol tracking, pick ONE device and use it consistently. Switching from Oura to Apple Watch will introduce a 2-4 bpm artifact that looks like a real change but isn't.

Peptide and pharmacologic protocol context

**GLP-1 receptor agonists (semaglutide, tirzepatide)**: Mild RHR reduction over months as weight drops, insulin sensitivity improves, and inflammation decreases. Typically 2-5 bpm reduction over 6-12 months at maintenance dose. This is the expected direction.

**Retatrutide (triple agonist)**: Notable exception. Phase 2 trials showed a small but measurable 4-6 bpm RHR ELEVATION on retatrutide vs placebo, observed across the dose range (Jastreboff et al., NEJM 2023). The mechanism appears related to glucagon receptor activation increasing resting metabolic rate. Not dangerous in trial participants but worth knowing about - if you're on retatrutide and see RHR up by 4-7 bpm vs baseline, that's an expected drug effect, not illness.

**Tesamorelin / HGH / sermorelin / GH peptides**: Mild RHR rise (2-4 bpm) tied to increased metabolic rate. Not concerning at typical doses; warrants attention if RHR rises >8 bpm.

**MK-677 (ibutamoren)**: Often produces a modest RHR rise (3-5 bpm) from increased cortisol and GH counter-regulatory effects. Should normalize on cycle-off.

**BPC-157, TB-500, CJC/Ipa**: No reliable RHR effect at typical doses.

**Cardarine (GW-501516, research compound)**: Reported RHR effects vary. Not enough human data to predict.

**Anabolic-androgenic steroids (off-protocol but relevant context)**: Often raise RHR via increased red blood cell mass and cardiac remodeling. Sustained RHR elevation >75 in a previously-fit athlete on AAS warrants cardiology consultation.

When low RHR is pathological

A low RHR is usually a marker of fitness, but not always: - **Sick sinus syndrome / sinus node dysfunction**: Pathologically slow rates, often with dizziness or syncope - **Hypothyroidism**: Slow metabolic rate including slowed heart rate - **Eating disorders**: RHR in the 30s-40s in an underweight, sedentary person is NOT athletic - it's metabolic suppression - **Drug effects**: High-dose beta-blockers can push RHR into the 40s; not benign in non-athletes

For most readers of this guide, low RHR is the goal and is benign. But "low RHR with dizziness, fainting, exercise intolerance, or unexplained fatigue" warrants medical evaluation - the symptoms differentiate athletic from pathological bradycardia.

When to be alarmed by high RHR

- **RHR consistently >100 at rest**: Tachycardia. Investigate (thyroid, anemia, anxiety, deconditioning, illness) - **RHR rising 10+ bpm over weeks despite no behavior change**: Workup warranted (hidden inflammation, thyroid, cardiac, anemia, sleep apnea) - **New-onset RHR >85 in a previously-fit person**: Same - workup warranted

Tracking cadence

- **Daily**: Oura/Whoop/Apple Watch nightly RHR (automatic) - **Weekly**: 7-day rolling average review - **Monthly**: Trend chart review - is the line drifting? - **Quarterly**: Bigger-picture review against protocol changes, training load, life stress

RHR vs HRV: which one matters more

A frequent question among biohackers is whether to prioritize RHR or HRV as the daily recovery signal. The honest answer is both, because they capture different physiology and correlate imperfectly with each other.

RHR is a slower-moving marker that reflects cardiovascular adaptation over months to years. HRV is a faster-moving marker that reflects autonomic recovery state day-to-day. RHR is the better fitness gauge; HRV is the better readiness gauge. A trained endurance athlete with RHR of 48 might wake up after a poor night's sleep and a stressful work week with HRV 30% below baseline - the RHR is stable (it reflects long-term adaptation) but the HRV correctly flags that today is a recovery day, not a hard-training day.

In practice, the combination is more informative than either alone. RHR up 5+ bpm AND HRV down 15%+ from baseline = strong signal something is wrong (illness, deep sleep debt, overtraining, severe stress). RHR stable but HRV down moderately = acute recoverable stressor (alcohol, single bad night). RHR up but HRV stable = often a thermoregulatory or hydration issue, less concerning. RHR down and HRV up over weeks = the trajectory you want, meaning aerobic fitness is improving alongside autonomic recovery.

RHR during cardiac rehab and post-illness recovery

Post-COVID, post-surgery, post-cardiac-event, and post-major-illness recovery is one of the most legitimate clinical uses of consumer RHR tracking. Recovery trajectories follow predictable patterns: in the acute phase, RHR is elevated 10-25 bpm above pre-illness baseline due to inflammatory cytokine drive and deconditioning. Over weeks of careful return to activity, RHR drops 3-5 bpm per week back toward baseline.

Patients who do not see this expected decline often have lingering inflammation, undiagnosed myocarditis (notable for some viral illnesses), or have returned to high-intensity activity too aggressively. A 2022 JAMA Cardiology study of post-COVID athletes found that wearable RHR tracking detected the small subset with cardiac complications earlier than symptom-based screening alone, primarily by flagging the cases that failed to show the expected recovery curve [5].

For peptide protocol users recovering from any acute stressor, the rule of thumb: RHR should be within 3-5 bpm of pre-stressor baseline before resuming hard training or starting any new protocol. Pushing through a still-elevated RHR usually extends total recovery time, not shortens it.

*Educational reference only. Track and discuss with a qualified clinician. MyProtocolStack does not provide medical advice, diagnosis, or treatment recommendations.*

Peptides That Commonly Move Resting Heart Rate

Conditions That Track Resting Heart Rate

Upload any lab PDF and MyProtocolStack maps your values to Resting Heart Rate and 40+ other biomarkers. StackAI interprets the trend in context of your protocol.