Sweatr
All articles
Wearable Data6 min read1 November 2026

What Your Strava Splits Tell You About When You Ran Out of Fuel

Your pace dropped in the last 10K. Was it fitness or fueling? Here's how to read your Strava data to find out.

What Your Strava Splits Tell You About When You Ran Out of Fuel

In Summary

  • A sudden pace drop in the final third of a race is almost always a fueling signal, not a fitness one.
  • Heart rate drift plus pace fade is the strongest sign you ran out of carbohydrate.
  • Cadence drop reveals the moment your nervous system started rationing energy.
  • Sweatr reads your Strava and wearable data to pinpoint fueling gaps automatically.

You finished your fall race. Maybe it was a marathon, maybe a half. You uploaded to Strava, scrolled through your splits, and saw it: that gut-punch moment where your pace fell off a cliff in the final kilometres.

Now you're asking the question every endurance athlete asks after a rough finish. Was that a fitness problem — or did I just run out of fuel?

Your Strava data can answer that question. You just need to know what to look for.

The three signals hiding in your splits

Most athletes glance at their per-kilometre (or per-mile) splits, see the slow ones at the end, and assume they need to train harder. But splits alone don't tell you why you slowed down. You need to cross-reference three data streams that your watch already recorded.

1. Pace fade pattern

Not all slowdowns are created equal. A fueling failure has a specific signature.

Fitness fade looks gradual. You slow by 10–15 seconds per kilometre across the second half. It's a gentle downward slope. Your body ran out of aerobic capacity and you just couldn't hold the pace.

Fueling fade looks sudden. You're on pace through 25K, maybe even 30K, and then you lose 30–90 seconds per kilometre in the space of 2–3 splits. This is what runners call "hitting the wall" or "bonking," and it happens when your glycogen stores are depleted faster than your fueling can replace them.

Open your Strava activity. Look at where the pace change happened. If it was sudden and dramatic — not a hill, not a wind change — you're looking at a fuel problem.

2. Heart rate drift vs. pace

This is the most telling signal, and almost nobody checks it.

In a well-fueled race, your heart rate rises gradually as the effort accumulates. That's called cardiac drift, and it's normal. Your pace might slow a little, but heart rate and pace roughly track together.

In a fuel-depleted race, something different happens. Your heart rate stays elevated or even drops slightly while your pace falls sharply. Your body is still trying to work hard, but it doesn't have the substrate to produce the energy. Or in some cases, your heart rate spikes as your body goes into a stress response, trying to compensate for the energy deficit.

Pull up the heart rate overlay on your Strava activity. Find the point where pace dropped. If your heart rate stayed flat or dropped while your pace cratered, that's a carbohydrate depletion signal. Your engine was running, but the fuel tank was empty.

3. Cadence collapse

This is the one most runners miss entirely, and it's the earliest warning sign.

Your running cadence — steps per minute — is partly controlled by your central nervous system. When your brain detects falling blood glucose, it starts rationing energy before you consciously feel anything. One of the first things it does is reduce stride rate.

A drop of 5–10 steps per minute in the final quarter of a race, even before you notice feeling bad, is your nervous system pulling the handbrake. By the time your pace visibly falls, the cadence drop has been happening for a kilometre or two already.

Check your cadence data in Strava or your Garmin/Apple Watch app. If cadence dropped before pace did, your body was running out of fuel before you knew it.

Putting the three signals together

Here's how to do your own post-race fueling audit in five minutes:

  1. Open your Strava activity and switch to the analysis view with pace, heart rate, and cadence overlays.
  2. Find the inflection point — the kilometre where your pace first dropped more than 15 seconds from your average.
  3. Check heart rate at that point. If HR stayed high or rose while pace fell, that's effort without fuel. If HR dropped, that's your body giving up on maintaining output.
  4. Check cadence at that point — and the 2K before it. If cadence started dropping before the pace crash, you got an early warning you didn't know how to read.
  5. Cross-reference with your fueling log. When did you take your last gel? When did you last drink? If there's a gap of more than 30 minutes between your last fuel and the pace drop, the correlation is likely causal.

Why this matters more than "just take more gels"

The generic advice — "take a gel every 45 minutes" — ignores everything that makes you an individual. Your sweat rate, your body weight, your pace, the temperature, how you've been training, and what you ate the day before all change how much carbohydrate you need per hour.

Recent research from the European Journal of Sport Science found that marathon runners planned to consume about 38 grams of carbohydrate per hour but actually managed only about 32. And they still believed they'd hit their target. The gap between intention and execution is where race days fall apart.

This isn't a willpower problem. It's an information problem. You don't know your actual carbohydrate needs per hour because nobody's calculated them from your data.

From data to action

Your Strava splits, your heart rate trace, and your cadence graph already contain the answer to "when did I run out of fuel?" The harder question is "how do I stop it happening next time?"

That's where your wearable data becomes genuinely useful — not as a dashboard to look at, but as an input to a plan you can follow.

Sweatr connects to your Strava, Apple Watch, and Garmin to build a fueling plan based on your actual data: your sweat rate, your training history, your body weight, and the specific conditions of your race. Instead of guessing that you need "a gel every 45 minutes," you get a plan calibrated to your body — with the exact gram-per-hour target and the timing to match.

Your watch recorded everything. The question is whether you'll use it as a rear-view mirror or a navigation system.

What to do this week

If you raced this autumn, do the five-minute audit above before you lose the data context. Write down:

  • The kilometre where your pace dropped
  • Whether heart rate tracked with pace or diverged
  • Whether cadence dropped before pace did
  • Your last fueling moment before the fade

That's your baseline. Next race, you'll know exactly what to fix — and exactly when your body started asking for help.