Your Watch Already Knows Why You Bonked — Here's How to Read the Signs

You crossed the finish line. Maybe you walked the last two miles. Maybe you were fine until mile 22 and then it all unravelled. Either way, the race is over, and you are staring at your Garmin or Apple Watch data wondering what happened.

Here is the thing most runners miss: your watch already recorded the answer. Buried in the heart rate graph, the pace splits, and the recovery metrics is a forensic trail that points directly at whether your nutrition plan worked — or quietly fell apart.

You just need to know what to look for.

Signal 1: Heart Rate Drift in the Final Third

Pull up your race heart rate graph. A well-fueled race looks like a steady climb or a plateau: your heart rate rises gradually as fatigue accumulates, but it tracks roughly with your effort.

A nutrition failure looks different. You will see heart rate suddenly spike in the final 8-10km — climbing 10-15 beats per minute above where it should be for your pace. This is cardiac drift, and while fitness and heat both contribute, in a race where conditions were stable and your training was solid, the most common culprit is glycogen depletion.

When your muscles run low on carbohydrate, your body compensates by increasing cardiac output to deliver more blood (and more fatty acids) to working muscles. Your heart works harder to maintain the same pace. This is your watch recording, in real time, the moment your fueling plan ran out of road.

What to look for: Compare your average heart rate in kilometres 5-15 with kilometres 30-42. If the gap is more than 12-15 bpm and your pace dropped simultaneously, your fueling almost certainly fell short.

Signal 2: Pace Decoupling

This is the companion signal to heart rate drift, and it is the most reliable post-race diagnostic tool you have.

Pace decoupling means your heart rate is climbing while your pace is slowing. In a perfectly fueled, well-paced race, the ratio between heart rate and pace stays relatively stable. When fueling fails, the ratio breaks: your body can no longer convert effort into speed at the same rate.

Open your Strava or Garmin activity and look at the heart rate overlay against pace. In the first half, the two lines should move roughly together. If they diverge sharply after 25-30km — heart rate rising, pace falling — you have your answer.

A 2025 narrative review in Nutrients examined programmed versus thirst-driven hydration strategies and found that both under-drinking and over-drinking degrade performance in ways that show up as pace decoupling. The point is not which strategy is better — it is that your watch recorded the outcome either way.

What to look for: Calculate your pace-to-HR ratio for the first half and second half. If the second half ratio is more than 5-8% worse, something broke. The question is what.

Signal 3: The Calorie Gap

Your watch estimated how many calories you burned during the race. Now ask yourself: how many did you actually consume?

Most recreational marathoners burn between 2,400 and 3,500 calories during a marathon, depending on body weight, pace, and conditions. Research consistently shows that the gut can absorb roughly 60-90 grams of carbohydrate per hour when using mixed glucose-fructose sources, which translates to 240-360 calories per hour from carbs alone.

A runner completing a marathon in 4 hours who consumed three gels (roughly 300 calories total) against an estimated burn of 3,000 calories has a deficit of 2,700 calories. Even accounting for pre-race glycogen stores (typically 1,600-2,000 calories) and fat oxidation, that math does not work. The bonk was inevitable.

Garmin's new nutrition tracking feature, launched in January 2026 with Connect+, now lets you log food intake alongside calorie burn. But it still does not connect these numbers to a race-day plan or tell you how many grams of carbohydrate you needed per hour at your specific pace and sweat rate. It shows you the gap. It does not close it.

What to look for: Divide your total carbohydrate intake during the race by the number of hours you were running. If the number is below 40g per hour, you were almost certainly under-fueled. If it is below 60g per hour and you bonked after 3 hours, your fueling plan was not aggressive enough.

Signal 4: Recovery Heart Rate and Overnight HRV

Your watch keeps recording after the race, and the recovery data tells its own story.

Recovery heart rate — how quickly your heart rate drops in the first 60 seconds after stopping — is influenced by hydration status. A slower-than-normal recovery (compared to your training runs) can indicate that dehydration compounded your fatigue.

More revealing is your overnight HRV after the race. If your heart rate variability dropped significantly below your baseline and stayed suppressed for 3-5 days, that is your autonomic nervous system telling you the race inflicted more damage than it should have. While muscular damage and inflammation play a role, research on ultra-endurance runners suggests that poor fueling and hydration amplify the autonomic stress response.

Garmin's Body Battery and Apple Watch's recovery metrics reflect this indirectly, but neither connects the dots to nutrition. A Body Battery score of 5 the morning after your marathon tells you that you are wrecked. It does not tell you that starting your gels 15 minutes earlier or drinking 200ml more per hour would have halved the damage.

What to look for: Compare your post-race HRV suppression to your recovery after your longest training run. If the race recovery was dramatically worse despite similar distance, the difference is likely pacing, nutrition, or both.

Signal 5: Sweat Loss Estimate vs Fluid Intake

Some Garmin models now estimate sweat loss for each activity. Pull up that number for your race.

Now count how much you actually drank. Every cup at an aid station is roughly 150ml. Every gel with water is another 100-150ml. Most runners significantly overestimate how much they consumed.

The current guidance from sports science suggests replacing 50-80% of hourly sweat loss rather than trying to match it one-for-one. If your Garmin estimated 1.5 litres of sweat loss per hour and you drank 400ml per hour, you were running at a significant fluid deficit — and the heart rate drift you saw in Signal 1 now has a clearer explanation.

In cool conditions, the trap is subtler. October racing temperatures reduce your thirst cues, but sweat rates can remain surprisingly high. Runners who trained through summer and dialled back their hydration for cooler race-day weather often end up more dehydrated than they would have been in July, because at least in July they were motivated to drink.

What to look for: If your estimated sweat loss was more than double your fluid intake, dehydration likely contributed to your performance drop.

Putting the Signals Together

No single signal tells the whole story. But when you stack them, a picture emerges:

• Heart rate drift + pace decoupling + low carb intake = glycogen depletion. You did not eat enough.
• Heart rate drift + slow recovery HR + large sweat-fluid gap = dehydration. You did not drink enough.
• Pace decoupling + high carb intake + GI distress = gut failure. You ate the right amount but your gut could not absorb it at race intensity.
• All signals normal + still felt terrible = pacing problem, not nutrition. Your watch just saved you from blaming the wrong thing.

The challenge is that doing this analysis manually requires pulling data from multiple screens, doing mental arithmetic, and knowing what the thresholds mean. Most runners glance at their splits, feel bad about the last 10km, and vow to "fuel better next time" without a specific plan.

From Diagnosis to a Plan That Actually Works

This is exactly where Sweatr changes the equation. Connect your Apple Watch, Garmin, or Strava account, and Sweatr reads your race data — the same signals described above — and translates them into a concrete, personalised nutrition plan for your next race.

It calculates your carbohydrate needs per hour based on your actual pace and body weight. It estimates your fluid requirements using your sweat rate data and the conditions you raced in. It builds a gel-by-gel, drink-by-drink timeline you can follow on race day, mapped to the products you actually use.

No spreadsheets. No guesswork. No staring at your Garmin data trying to figure out why mile 35 felt like you were running through wet concrete.

Your watch already has the data. Sweatr tells you what to do with it.