Why Pace — Not Just Duration — Decides How Much Fuel You Need

You've done the maths. Body weight, race distance, finishing time. Your calculator spat out 60 grams of carbohydrate per hour. You packed six gels, practised the timing, and went to work.

By mile 20, you were walking.

Here's what the calculator didn't ask you: how fast are you running relative to your threshold? That single variable changes your carbohydrate burn rate more than body weight, more than temperature, and more than whether you ate porridge or toast for breakfast.

The variable every fueling calculator ignores

Every fueling guide you've ever read starts with the same inputs: body weight, race duration, maybe the distance. Some advanced ones factor in conditions — heat, humidity, altitude. But almost none ask the question that matters most:

What percentage of your maximum aerobic capacity will you sustain?

This matters because your body has two primary fuel tanks: fat and glycogen (stored carbohydrate). At low intensities — an easy jog, a warm-up shuffle — your muscles burn a relatively high proportion of fat. As intensity rises, the fuel mix shifts. Hard.

Here's what the research shows across decades of metabolic testing:

• At 60% VO2max (easy long run pace): roughly 40–50% of energy comes from carbohydrate
• At 70% VO2max (steady marathon pace for an experienced runner): roughly 55–65% from carbohydrate
• At 80% VO2max (pushing for a PB): roughly 70–80% from carbohydrate
• At 85%+ VO2max (the red zone, first-half adrenaline pace): 80–90%+ from carbohydrate

That progression isn't linear — it's exponential. A 10% increase in intensity doesn't cause a 10% increase in carb burn. It causes a disproportionately larger shift because your body can only mobilise fat at a limited rate, and once intensity exceeds that rate, carbohydrate fills the entire gap.

What this means in gels

Let's put real numbers on it.

A 70 kg runner at 70% VO2max burns approximately 60–70 grams of carbohydrate per hour. That's manageable. Two gels every 45 minutes, or one gel plus a carb drink. The standard advice works.

The same runner at 85% VO2max — perhaps because they went out with the faster corral, or the downhill first miles felt too good to slow down — burns approximately 90–110 grams of carbohydrate per hour.

That's not a small difference. That's 50% more fuel per hour. Over a 3.5-hour marathon, the total carbohydrate demand jumps from roughly 230g to 350g. That's five extra gels worth of carbohydrate that the runner's plan didn't account for.

And here's the cruel part: the faster you run, the harder it is for your gut to absorb the extra fuel you now need. Blood redirects from your digestive system to your working muscles. Your gut's absorption ceiling doesn't rise with your pace — if anything, it drops. So you need more fuel but can process less of it. The mismatch is what makes bonking at mile 20 feel so sudden and so total.

Why "going out too fast" is a nutrition problem, not just a pacing problem

Every running coach will tell you not to go out too fast. They'll talk about cardiac drift, lactate accumulation, and muscular fatigue. All true. But the nutrition cost of a fast first half is the mechanism that turns a pacing mistake into a collapse.

Consider a runner whose goal is 4:00 (9:09/mile). Their fueling plan targets 65g of carbs per hour — perfectly appropriate for their intended effort level of about 72% VO2max.

But they run the first 10K in 53 minutes instead of 57 minutes. That's only 40 seconds per mile faster. It barely registers as a mistake. But at that intensity (approximately 80% VO2max), they burned roughly 85g of carbs in that first hour instead of 65g. They're already 20g in the hole — one gel behind schedule — and they don't know it because they feel great.

By halfway, that deficit has compounded. Their glycogen stores are tracking toward depletion at mile 18 instead of mile 24. When they slow down at mile 16, which is inevitable because the early pace was unsustainable, the damage is already done. Their fuel tank hit empty six miles earlier than their plan predicted.

Your watch already knows this

Here's what makes this fixable, not just explainable: your wearable captures the exact data needed to calculate this in real time.

Your watch knows your heart rate throughout every workout. Heart rate is a reliable proxy for oxygen consumption, which directly determines substrate utilization. A run at 155 bpm uses a fundamentally different fuel mix than a run at 145 bpm — even if the pace is similar on different days due to heat, fatigue, or terrain.

Your watch also knows your training history. Months of data establish your aerobic threshold, your typical intensity distribution, and your training load trend. All of these shape how efficiently you burn fat at a given intensity — which in turn determines how much carbohydrate you need to supplement.

The problem is that your watch shows you the data and stops there. It doesn't connect heart rate zones to carbohydrate burn rates. It doesn't adjust your fueling plan when conditions push your heart rate 8 beats higher than expected. And it definitely doesn't tell you to take an extra gel at mile 8 because your first 5K was too fast.

That connection — from pace and heart rate data to a specific, adjusted fueling plan — is what turns raw wearable data into something you can act on.

How to estimate your real carb needs by intensity

You don't need a lab to get a useful estimate. Here's a practical framework using data you already have:

Step 1: Find your threshold heart rate. This is the heart rate you can sustain for roughly 60 minutes at maximum steady-state effort. Most GPS watches estimate this. If yours doesn't, your 10K race heart rate is a close proxy.

Step 2: Calculate your race intensity as a percentage of threshold.

• If your threshold heart rate is 172 bpm and you plan to race at 152 bpm, you're at approximately 88% of threshold — which corresponds to roughly 75% VO2max for most trained runners.

Step 3: Apply the intensity-adjusted carb burn estimate.

• 65–70% of threshold HR → ~45–55g carbs/hour
• 75–80% of threshold HR → ~60–75g carbs/hour
• 85–90% of threshold HR → ~80–100g carbs/hour
• 90%+ of threshold HR → ~100–120g carbs/hour

These numbers assume a trained runner between 60–85 kg. Heavier runners trend higher; lighter runners trend lower. But the intensity multiplier is consistent.

Step 4: Build your fueling plan around the intensity number, not just duration.

If your plan says 60g/hr because you're running a 4-hour marathon, but your intensity estimate says you'll burn 80g/hr at your target heart rate, your plan is 25% short. That's the deficit that shows up at mile 20.

The two-speed mistake

There's a subtlety that catches experienced runners. It's not just about average pace — it's about pace variability.

A runner who goes through the first half in 1:55 and the second in 2:05 doesn't have the same fuel profile as a runner who runs both halves in 2:00. The fast first half burned through carbohydrate at a higher rate during a period when the gut was absorbing fuel at full capacity. The slow second half reduced the burn rate, but also reduced gut motility (because fatigue, dehydration, and sympathetic nervous system activation all impair digestion in the back half).

The result: a positive split costs more glycogen than an even split for the same finishing time. The mathematics of fuel burn punish inconsistency.

This is why negative splitting isn't just a pacing strategy — it's a nutrition strategy. Starting conservatively keeps your carb burn rate within range of what your gut can replace. It preserves glycogen for when you need it. And it keeps blood flow to the gut higher during the early miles when absorption capacity is highest.

What TrainingPeaks shows and what it misses

TrainingPeaks recently launched Fueling Insights, which estimates fat vs carbohydrate utilization during workouts. It's a step in the right direction. But it currently works only for cycling (requires power meter data), uses population-level metabolic profiles rather than individual data, and shows you a graph after the workout — not a plan before it.

For runners, there's no equivalent. Your training log shows pace, heart rate, distance, and maybe Training Load. None of those screens connect to a carbohydrate number. The substrate utilization data exists in your heart rate file — it's just not being translated.

The Sweatr approach

Sweatr connects the dots that your watch and training platform leave disconnected. It takes your heart rate data, training history, body weight, and planned race conditions and calculates a carbohydrate burn estimate specific to your intended intensity — not a population average, not a one-size-fits-all range.

When your race intensity changes — because conditions are hotter than expected, or because the first miles are downhill, or because race-day adrenaline pushes you 10 bpm higher — Sweatr adjusts the plan. It tells you when to take your next gel, how much fluid to target per aid station, and what to change if your heart rate is running higher than planned.

It's the difference between "take a gel every 45 minutes" and "take 25g of carbs at mile 4, another 25g at mile 7, and increase to 30g every 2.5 miles from mile 10 because your planned intensity means you'll burn 80g/hr, not 60g/hr."

The bottom line

Your marathon fueling plan has a pace problem. Not because you'll necessarily go out too fast — but because the plan itself doesn't account for the fact that intensity changes everything about how much fuel you burn.

Sixty grams per hour is a fine number. For one specific intensity. At one specific body weight. In one specific set of conditions. Change any of those inputs — especially intensity — and the number changes with it.

Your watch already captures the data to calculate your real number. The question is whether anything connects that data to your gel schedule. Most fueling tools don't. Sweatr does.

Build a plan that matches your pace, not just your distance. Your mile-20 self will thank you.