My HRV Climbed 20 Points This Week. My Running Got Easier. Here's What Connected Them.

My HRV went from 31 to 51 in seven days. In the same window, my average heart rate on easy runs dropped by more than 25 beats per minute at the same pace. The wearable showed me both numbers. It never connected them.

I’m 52. I train six mornings a week, a mix of strength and conditioning plus running. I’m building towards Partner Hyrox in July and a half marathon in August. I track everything through an Apple Watch Ultra 3 and log it all to Strava.

This week’s data told a story I almost missed.

The HRV Climb

Here’s what my heart rate variability looked like over the past ten days:

Date	HRV (ms)	Deep Sleep (hrs)
Apr 15	27	0.61
Apr 17	35	0.46
Apr 18	34	0.34
Apr 19	36	0.61
Apr 20	32	0.50
Apr 21	32	0.77
Apr 22	38	0.47
Apr 24	51	0.85

That April 15 reading of 27ms was the lowest I’ve recorded in weeks. By Thursday morning it had nearly doubled. Not because I did anything dramatic. I just stopped digging a hole.

What Changed in the Runs

This is the part that actually matters. Two runs at virtually identical paces. Completely different cardiac cost.

April 15: 6km Easy Run Pace: 6:53/km. Average heart rate: 165. Max: 168.

April 22: 6km Easy Run Pace: 6:29/km. Average heart rate: 139. Max: 153.

Read that again. I ran 24 seconds per kilometre faster with a heart rate 26 beats lower. Same legs. Same route. Same time of day. The only thing that changed was my recovery state.

When your HRV is in the low 30s, your autonomic nervous system is under load. Your body compensates by driving heart rate higher to maintain the same cardiac output. Everything feels harder because it literally is. You’re doing the same work with less reserve.

When your HRV recovers, your parasympathetic nervous system has more headroom. Heart rate stays lower at the same effort level. Pace feels easier. Breathing is controlled. You’re not fighting your own physiology.

The Deep Sleep Connection

Look at the table again. The deep sleep column tells its own story.

April 18 was the worst deep sleep night of the week at 20 minutes. HRV the next few days stayed flat in the low 30s. Then deep sleep started creeping back up. By April 24 I logged 51 minutes of deep sleep and woke up to an HRV of 51.

Deep sleep is when your body does the bulk of its parasympathetic recovery. Growth hormone release peaks during slow wave sleep. Tissue repair happens here. Neural recovery happens here. If you’re not getting enough deep sleep, HRV stays suppressed regardless of what your training load looks like.

The chicken and egg question is real. Did better deep sleep drive the HRV recovery, or did the HRV recovery allow deeper sleep? Probably both. They feed each other in a virtuous cycle when things are going well, and drag each other down when they’re not.

What My Wearable Showed Me vs What It Told Me

My Apple Watch showed me all of these numbers. Every morning I could see HRV, deep sleep, resting heart rate. After every run I could see pace and average heart rate.

But it never said: “Your running heart rate dropped 26 bpm because your HRV recovered 20 points because your deep sleep improved by 31 minutes.”

It gave me the data points. The connection between them was invisible unless I went looking.

This is the gap in every wearable ecosystem I’ve used. The metrics exist in isolation. Sleep data lives in one screen. HRV in another. Run performance in a third. The synthesis between “your sleep improved, which improved your autonomic recovery, which made your run easier” never surfaces.

What I Actually Did Differently

Nothing heroic. Between April 18 and April 22 I:

1. Stopped running on the high HR days and stuck to gym sessions
2. Got to bed before 10pm on three of the five nights
3. Ate over 100g of protein on four of the five days (vs the 66g disaster on April 17)

That’s it. No supplements. No cold plunge. No biohacking protocol. Just the basics done consistently for five days.

The April 17 protein number stands out. 66g of protein on a training day is not enough for a 52 year old carrying 39kg of skeletal muscle. The next morning my HRV was 35 and my resting heart rate was 55, the highest of the week. Underfuelling has a direct, measurable cost. You can see it in the data within 12 hours.

The Takeaway for Anyone Tracking

If you’re wearing a device that measures HRV and you also track your run data, overlay them. When your HRV trends up over 3 to 5 days, check your running heart rate at the same pace. You’ll almost certainly see it drop.

This is the signal that tells you recovery is working. Not the recovery score (which is a black box calculation). Not the readiness ring (which you can’t audit). The actual cardiac data from your actual runs compared against your actual autonomic state.

When cardiac cost drops at the same pace, your body is ready. When it climbs, something is off. Sleep, nutrition, stress, training load. One of them is dragging you backwards.

The wearable can show you the numbers. Connecting them is still your job.

---

X Thread (5 tweets)

1/ My HRV went from 31 to 51 in seven days. My easy run heart rate dropped 26 bpm at the same pace. The connection between these two facts is the most useful thing my Apple Watch can tell me.

2/ April 15: 6km at 6:53/km pace, average HR 165. April 22: 6km at 6:29/km pace, average HR 139. Faster and easier. The only variable that changed was recovery state.

3/ Deep sleep went from 20 minutes to 51 minutes in the same window. Deep sleep drives parasympathetic recovery. HRV measures parasympathetic recovery. The numbers track almost perfectly.

4/ What I changed: nothing dramatic. Bed before 10pm. Over 100g protein most days. Skipped runs when HR was elevated and did gym work instead. Five days of basics.

5/ Every wearable shows you these numbers in separate screens. None of them connect “your sleep improved so your HRV recovered so your running got easier.” That synthesis is the whole point. @p247io