What I Learned Tracking My Resting Heart Rate for a Year

365 days of resting heart rate data from an Apple Watch and a Garmin watch running in parallel. Five things the data showed that I wouldn't have noticed otherwise — and three I'd ignore.

I started tracking resting heart rate seriously after a doctor mentioned that RHR is one of the few wearable metrics with real clinical signal. The catch is that single-day readings are noisy. The actual signal lives in trends, weekly averages, and deviations from your personal baseline. Here's what a year of paying attention surfaced.

Who actually benefits from RHR tracking

The honest list. Anyone in their 30s or older who wants an early-warning system for cardiovascular health changes. Anyone training seriously who wants to detect overtraining before it shows up as injury. Anyone in stress-heavy work who wants objective data on whether they're truly recovering on weekends.

People who already work out, eat reasonably well, and want one extra signal. RHR tracking is most useful for adjusting the inputs you already control — it's not magic for someone who isn't doing the underlying work.

Who can skip it. People without a wearable already on their wrist — buying a $300+ device just for RHR tracking is overkill if you're not using the other features. Casual exercisers whose baseline isn't going to change much. People who'll obsess over daily fluctuations rather than trends.

What the year of data actually showed

Sleep is the strongest single driver. My baseline RHR sat around 58 bpm on nights I got 7.5+ hours. On nights below 6 hours, the next-day RHR rose to 64-68 bpm. Consistent finding across the whole year, no exceptions. The wearable just made the link visible — the underlying biology has been there all along.

Alcohol has a measurable, persistent effect. Two drinks at dinner raised the following night's RHR by 4-6 bpm. The effect lasted 36-48 hours. Heavy drinking nights (rare) raised it 8-12 bpm for three days. I drink less now than I did when I started tracking, mostly because the data is hard to argue with.

Stress shows up before I notice it. During the busiest two weeks of my work year, my RHR climbed 5-7 bpm a full week before I consciously felt stressed. The wearable caught the pattern earlier than my own perception.

Training adaptation is visible. Six weeks of consistent zone-2 cardio dropped my baseline RHR from 60 to 55 bpm. When I missed two weeks of training over the holidays, it climbed back to 60. The granularity of seeing this in 7-day rolling averages is something I wouldn't have noticed without the tracker.

One unexpected pattern. Daylight savings time disrupted my baseline by 3-4 bpm for about a week each way. Real biological effect that I'd previously dismissed as folklore.

What I'd ignore

Daily fluctuations. Day-to-day RHR can swing 5-8 bpm based on caffeine timing, hydration, room temperature, the sleep position you woke up in. Looking at individual days is noise; looking at 7-day or 14-day averages is signal.

Comparing to "normal" ranges from the internet. The 60-100 bpm "normal" range is way too wide to be useful. Your personal baseline is what matters. Establish it across 30+ days, then track deviations from it.

Heart rate variability (HRV) for general fitness tracking. HRV has real research signal but the day-to-day numbers are so noisy that most users overreact. RHR is a cleaner signal for the same kinds of questions.

The gear that actually matters

A wearable you'll actually wear nightly. Sleep-tracking and resting-heart-rate measurement requires the device be on at night. The Apple Watch is excellent but battery-light for overnight tracking — you have to charge during the day. The Garmin watch line has multi-day battery life that makes nightly wear effortless.

If you want to optimize for sleep tracking specifically, an Oura Ring avoids the wrist-band issue entirely. More expensive over time (subscription) but the form factor wins for some users.

A real bedside Stanley tumbler of water. The first measurement of every morning is influenced by hydration; consistent water intake stabilizes the baseline.

A smart scale that talks to the same app as your watch. Weight and RHR are loosely correlated; seeing both in one dashboard surfaces patterns either alone would miss.

How to actually use the data

Establish a 30-day baseline before drawing conclusions. Wear the device, capture data, don't intervene for the first month.

Look at 7-day rolling averages, not individual days. Most wearable apps default to daily; the trend view is usually buried but more useful.

Connect deviations to actual life events. When RHR climbs 5+ bpm above baseline for 3+ days, ask what changed — sleep, alcohol, stress, illness, training load. The connection is almost always findable.

Talk to a doctor about persistent unexplained elevations. RHR climbing 10+ bpm above your baseline for more than two weeks with no obvious cause is worth a check-in. Don't diagnose yourself from internet content.

Common mistakes

Buying a wearable, wearing it for two weeks, then drawing conclusions. The signal you want lives in months of data, not weeks.

Overreacting to single-night spikes. One bad night doesn't change the trend.

Trying to optimize RHR as a goal in itself. RHR is downstream of sleep, training, stress, and alcohol. Optimize the inputs; the RHR follows.

Ignoring data that contradicts beliefs. The week I most wanted to believe I was getting good rest was the week the data showed I wasn't. The wearable was right; I was lying to myself.

For the broader frame on building daily habits that compound across years, my notes on sustained energy apply the same principles to a related metric. Sleep is the foundation; everything else follows.