You've been there. Mile 70, maybe mile 75. The legs go from tired to absent. Not the gradual fade of honest fatigue — a switch. One minute you're riding, the next you're surviving. Power drops, cadence drops, motivation vanishes so completely you start doing maths about whether you could get a taxi home from here. And every time it happens, the instinct is to blame fitness. Not enough base, not enough miles, not strong enough.
Wrong diagnosis. Almost every rider who falls apart at mile 70 caused it at mile 10. Not with bad legs — with bad decisions. Went out a fraction too hard. Skipped a feed because the pace felt easy. Didn't drink enough because the temperature was "fine." Those small errors compound silently for three hours, then arrive all at once as a catastrophic failure that feels sudden but was completely predictable.
This is the strategy for rides where the distance itself becomes the opponent. Not how to get faster. How to still be riding — and riding well — six, seven, eight hours into a day when most people around you have already cracked.
A 6-hour ride is not a longer 3-hour ride
This is the first thing to get straight, because it changes everything that follows.
On a 3-hour ride, your body runs primarily on glycogen. You have enough stored carbohydrate in muscle and liver to cover the entire effort if intensity stays moderate, and fuelling is a top-up rather than a lifeline. You can get away with sloppy pacing. You can skip a feed window and recover. You can go 5% too hard on the first climb and pay for it without catastrophe.
On a 6-hour ride, none of that is true.
The difference is not proportional — it is qualitative. Four things change as duration extends past the 3-hour mark, and each one multiplies the others:
Glycogen becomes finite in a way you can feel. Even with aggressive fuelling at 90g of carbohydrate per hour, you cannot fully replace what you burn at any meaningful intensity. You are always running a deficit. The longer the ride, the deeper the deficit, and the more dependent you become on fat oxidation and exogenous carbohydrate to keep moving.
Core temperature rises and stays elevated. By hour four, especially in warm conditions, your core temperature has been climbing steadily. The body redirects blood to the skin for cooling, which means less blood for working muscles and less blood for the gut. That's why fuelling gets harder as the ride goes on — the organ responsible for absorbing your food is getting less blood flow precisely when you need it most.
Cumulative dehydration compounds. Even modest fluid deficits — 2-3% of body weight — reduce plasma volume, thicken the blood, and make the heart work harder for the same output. Over six hours, a rider who falls 200ml behind target per hour arrives at hour five with a litre-sized problem that no amount of drinking can fix quickly.
Muscular fatigue accumulates non-linearly. The repeated eccentric loading, the micro-damage, the progressive depletion of intramuscular fuel stores — these don't scale linearly with time. Hour five is disproportionately harder than hour three, even at the same power, because the muscles have been accumulating damage that they cannot repair while you keep pedalling.
This is why the strategies that work for a 3-hour group ride don't transfer to a century. Different physiology demands a different plan.
The intensity ceiling: what you can actually sustain
Here's where most people go wrong before the ride even starts. They know their FTP, they know their zones, and they ride the first hour at an intensity that feels comfortable — maybe 78-80% of FTP. It is comfortable. For an hour.
But the metabolic cost of riding at 80% of FTP for six hours is vastly greater than the metabolic cost of riding at 68% of FTP for six hours. Not just "a bit more" — disproportionately more. The relationship between intensity and glycogen cost is exponential, not linear. Push 10% harder for 30 minutes and you don't burn 10% more glycogen. You burn 20-30% more, because the proportion of energy coming from carbohydrate rises steeply as intensity increases.
For rides over four hours, the intensity ceiling for most amateur riders is 65-75% of FTP. That's the range where fat provides a meaningful share of the fuel, glycogen burn stays manageable, and the body can sustain the effort without digging a hole it can't climb out of. The FTP Zone Calculator will give you the exact wattage for your numbers — set the target and respect it, especially in the first two hours when the temptation to ride harder is strongest.
Seiler's work on intensity distribution supports this from a different angle. His research into how elite endurance athletes structure their training — overwhelmingly easy, with hard sessions polarised at the top end — applies directly to how they race long events too. The athletes who win 200km races don't ride tempo for seven hours. They sit at low intensity for most of the day and save the matches for when they count. The principle holds whether you're a WorldTour professional or riding your first century: spending time above the ceiling early means spending time below the floor later.
And that floor is ugly. Once glycogen depletion starts to bite — once you cross the line from "tired" to "bonking" — there is no recovery. You can slow down and eat, but you won't get back to where you were. The damage is done. The bonk is a one-way door. Which is why the intensity ceiling is not a suggestion. It is the single most important number on a long ride.
Even pacing beats negative splitting
The instinct is appealing: start easy, finish fast. Negative splitting — riding the second half faster than the first — works beautifully in a 10k running race. It works less well in a marathon. And on a 100-mile bike ride, it doesn't work at all.
The reason is the metabolic cost curve. At lower intensities, your body draws a larger proportion of energy from fat. At higher intensities, the carbohydrate contribution rises steeply. On a long ride where glycogen is the limiting factor, any time spent above the target intensity burns through your finite carbohydrate stores at an accelerated rate. And the cost is not recoverable — you can't "save up" glycogen by riding easier later. The extra glycogen you burned in hour one is gone.
Even pacing — holding a consistent power output throughout the ride — produces faster overall times on long events because it minimises the total glycogen cost. It keeps you in the fat-burning sweet spot for the maximum number of hours and avoids the sharp spikes in carbohydrate demand that come from surges, climbs attacked too hard, or that classic first-hour enthusiasm when the legs feel fresh and 300 watts feels like nothing.
This doesn't mean robotic, perfectly flat power. Hills change things. Wind changes things. But the intention should be even effort, not even speed. On climbs, hold the power target and let speed drop. On descents, back off and recover. In a headwind, resist the urge to push harder — you'll burn disproportionately more fuel for a marginal gain in speed. Match effort to the intensity ceiling, not to what feels manageable in the moment.
If you want to go faster over the final 20 miles, the way to do that is not to save energy — it's to arrive at mile 80 with glycogen still available and a body that isn't on fire. That only happens if the first 80 miles were ridden at the right intensity.
Fat oxidation and the endurance sweet spot
Here's the good news about riding at 65-75% of FTP: you are not just saving glycogen. You are actively using a fuel system that is effectively unlimited.
Fat oxidation — the rate at which your body burns fat for energy — peaks at around 55-65% of VO2max. At that intensity, fat provides 40-60% of the total energy, depending on training status, and it does so from a store that even the leanest rider could draw on for days. A 70kg rider at 10% body fat carries roughly 63,000 calories of fat. Compare that to the 2,000-2,500 calories of glycogen in muscle and liver combined, and the arithmetic is obvious: the goal of a long ride is to keep intensity in the range where fat can do most of the heavy lifting.
This is the physiological basis for everything else in this article. It's why the intensity ceiling matters. It's why even pacing beats negative splitting. It's why Zone 2 base training makes long rides easier — not because it makes you fitter (though it does), but because it shifts the crossover point, letting you burn more fat at a higher power output and sparing the limited glycogen you carry.
Well-trained riders oxidise more fat at the same absolute power than less-trained riders. That's one of the most valuable adaptations in endurance cycling, and it's why base miles matter. If you've done the work — months of consistent Zone 2 riding — a 100-mile day at 65-70% of FTP feels sustainable because your body is pulling most of its energy from a source that will never run out. If you haven't done the work, the same ride burns through glycogen faster, and the wall arrives earlier.
Fuelling protocol: timing, quantity, and the Jeukendrup framework
Pacing keeps the burn rate manageable. Fuelling replaces what pacing can't save. Together, they are the two pillars of cycling nutrition for any ride over four hours. Get one wrong and the other cannot compensate.
Asker Jeukendrup's research on carbohydrate oxidation during exercise is the foundation of modern in-ride nutrition, and the practical takeaway is this: your gut can absorb up to 60g of glucose per hour through one intestinal transporter, and adding fructose opens a second transporter that pushes the ceiling to 90-120g per hour using a 2:1 glucose-to-fructose ratio. For rides over three hours, you should be aiming for the upper end of that range. The Fuelling Calculator sets a per-hour target based on your ride duration and intensity.
But the number only matters if you hit it consistently. And that's where most riders fail — not because they don't know the target, but because they drift away from it. Here's the protocol:
Start eating in the first 20 minutes. Not when you're hungry. Not when you feel like you need it. In the first 20 minutes. Hunger is a lagging indicator — by the time you feel it, you're already behind on intake, and catching up from a fuelling deficit on a long ride is like chasing back after a puncture in a crosswind. Technically possible, practically miserable.
Eat every 20 minutes, without exception. Set a timer. A watch alarm, a phone alert, whatever it takes. Every 20 minutes, take in a gel, a few bites of a bar, or a swig of concentrated energy drink. The specific food matters less than the consistency. The most common fuelling mistake on long rides is not eating the wrong things — it's gradually extending the gap between eating from 20 minutes to 25 to 35 to "I'll eat at the top of the next climb" to suddenly being 45 minutes behind target intake.
Alternate textures and flavours. Gel fatigue is real. After four hours, the thought of another sticky, sweet gel can make your stomach turn. Pack a mix: gels for convenience, bars for chewing satisfaction, rice cakes for something savoury, a banana if you can carry one. The in-ride nutrition guide breaks down the options and their carbohydrate density.
The carbohydrate per hour target for a 100-mile ride:
| Ride Phase | Hours | Target Intake | |---|---|---| | First quarter | 0-1.5hr | 60-80g/hr | | Middle half | 1.5-4.5hr | 80-90g/hr | | Final quarter | 4.5hr+ | 60-80g/hr (as tolerated) |
That slight taper at the end is not about needing less fuel — you need more, if anything — but about the practical reality that gut function degrades as core temperature rises and blood is redirected to the skin. Better to front-load and have a buffer than to attempt 90g per hour at hour five and find it coming back up.
Front-loading: the first two hours strategy
The first two hours of a long ride are a gift. Your legs feel good. Your gut is functioning at peak capacity. Blood flow to the digestive system is strong. Core temperature is low. Absorption is efficient. And most riders waste this window completely by eating too little because "I feel fine."
Front-loading calories means deliberately eating more in the first two hours — when absorption is easiest — to build a buffer for the later hours when eating becomes harder. This doesn't mean gorging yourself at the start. It means hitting 70-80g per hour from the first feed stop, not easing into it with a gel at 45 minutes and then gradually ramping up.
Think of it as paying rent in advance. The carbohydrate you absorb in hour one is glycogen you don't have to replace from an increasingly reluctant gut at hour five. And because gut function peaks early in a ride — before heat, dehydration, and sympathetic nervous system activation start to compromise absorption — the food you eat early is absorbed more completely than the food you eat late.
This is not speculation. The research on gut blood flow during prolonged exercise is clear: as exercise duration increases, splanchnic blood flow decreases. The organs responsible for digesting and absorbing food get progressively less blood. That's why riders who feel perfectly fine eating 90g per hour at hour two can barely tolerate 40g per hour at hour five. The gut hasn't changed. The blood flow has.
Front-load accordingly. Bank the calories when your gut is willing and the cost is low.
The hour 4-5 low point: what is happening and what to do about it
If you've ever ridden a 100-mile sportive, you know the low point. It sits somewhere between hours four and five. The specific symptoms vary — dead legs, mild nausea, total loss of motivation, a strange emotional flatness where you don't care about anything, least of all finishing the ride — but the timing is remarkably consistent.
This is not a sign of poor fitness. It is a predictable, physiological event caused by the convergence of several systems all reaching their limits at the same time:
Glycogen stores are materially depleted. Even with perfect fuelling, you're running a deficit by this point. Muscle glycogen is substantially lower than it was at the start, and liver glycogen is being maintained only by what you're eating. You're running on exogenous carbohydrate and fat oxidation now, not stored fuel.
Core temperature has risen. Four-plus hours of continuous exercise elevates core temperature by 1-2 degrees Celsius, even in moderate conditions. The cardiovascular system is working harder to cool the body, redirecting blood to the skin and away from the muscles and gut. Heart rate drifts upward for the same power output — cardiac drift — and the effort of maintaining target watts increases without the watts changing.
Cumulative dehydration has reduced plasma volume. Even with disciplined drinking, most riders lose 1-3% of body weight in fluid over five hours. That's enough to reduce blood volume, increase heart rate, and make the same power feel substantially harder. The blood is thicker, the heart pumps less per beat, and every system has to work more to maintain what was effortless at hour one.
Muscular fatigue has accumulated. Thousands of pedal strokes have produced micro-damage in the working muscles. Calcium handling is impaired. Contractile force is reduced. The legs don't respond the way they did, even at the same neural drive. This is real, structural fatigue — not in your head.
How to manage it:
Expect it. Knowing the low point is coming and that it will pass is half the battle. Riders who don't expect it panic, assume they're bonking, and either stop or push harder — both wrong. Riders who know it's a predictable trough just ride through it.
Reduce intensity by 5-10%. Drop from 70% of FTP to 63-65% for 20-30 minutes. The slight reduction cuts carbohydrate demand, allows more fat to contribute, and gives the cardiovascular system a small reprieve. You will feel noticeably better within 15-20 minutes.
Eat something different. If you've been on gels for four hours, switch to a bar or some real food. The novelty matters — your brain is tired of the same stimulus, and a different flavour or texture can reset the appetite enough to get calories in.
Cool yourself. Pour water over your head and neck if conditions are warm. This won't lower core temperature dramatically, but it reduces skin temperature and frees up some blood flow from the cooling system back to the working muscles.
Talk to yourself. Not motivational platitudes. Practical self-talk: "This is the low point. It passes. I need to eat, drink, and ride 10 minutes at a time." Breaking the remaining distance into small chunks makes it manageable when the idea of "40 miles to go" is paralysing.
The low point passes. It always does. Riders who come out the other side with glycogen still available and hydration still intact often feel surprisingly good in the final 90 minutes. Not fresh — but functional, which is all you need.
Hydration and sodium at distance
Water and sodium are the silent partners to carbohydrate on a long ride. Underfuelling gets the attention because its failure mode — the bonk — is dramatic and unmistakable. Dehydration creeps in without a headline moment. You just get progressively slower, and your heart rate drifts higher, and the power feels harder, and eventually you're 10% down on output and can't figure out why because you "ate fine."
The target is 500-750ml of fluid per hour, adjusted for conditions. In cool weather, the lower end. In heat, the upper end or more. The Hydration Calculator factors in ambient temperature, body weight, and expected intensity to give you a per-hour target.
But volume alone is not enough. Sodium matters, and it matters more the longer you ride.
You lose 500-1500mg of sodium per litre of sweat, depending on your individual sweat composition. Over five or six hours, a heavy sweater in warm conditions can lose 5,000-8,000mg of sodium — a massive deficit that plain water or low-sodium sports drinks cannot replace. The consequence is not just cramp (though cramp is one symptom). It's hyponatraemia in extreme cases, and more commonly, it's impaired gut absorption — because sodium is a co-transporter for glucose across the intestinal wall. If sodium is depleted, your ability to absorb the carbohydrate you're eating is reduced, which means the fuelling plan fails even though you're doing everything right on paper.
Aim for 500-700mg of sodium per hour on rides over three hours. Electrolyte tablets in your bottles, salt capsules in your pocket, or salted food in your feed bag. This is not optional on a long day. It's infrastructure.
And a practical point: don't rely on thirst. Like hunger, thirst is a lagging indicator. By the time you're thirsty, you're already 1-2% down on fluid. Drink to a schedule, not to sensation.
Mental strategies for the final quarter
The last 25 miles of a 100-mile ride are where the race is won or lost — not against other riders, but against yourself. The body is fatigued. The brain is bored. The power is lower than it was four hours ago, and every small annoyance — a headwind, a climb, a red light — feels disproportionately significant.
This is normal. Your brain has been making decisions and maintaining focus for five hours. Cognitive fatigue is real, and it manifests as poor decision-making, reduced pain tolerance, and a specific flavour of despair that says "this is pointless" even though you have 25 miles left and the finish is absolutely achievable.
What works:
Process goals, not outcome goals. Don't think about the finish. Think about the next feed stop, the next junction, the next 10 minutes. "I'm going to hold 160 watts to that tree" is manageable. "I have 25 miles to go" is paralysing.
Dissociation and association. Research on ultra-endurance athletes shows they alternate between two mental modes: association (focusing on body signals, form, cadence) and dissociation (thinking about anything else). Neither is permanently better. When the body is fine and just boring, dissociate — think about something else, listen to the road, look at the scenery. When the body sends a warning signal — cramp brewing, stomach turning, power dropping — switch to association and address it.
Keep eating. This sounds like fuelling advice, and it is. But it's also a mental strategy. Eating gives the brain a task, provides a small dopamine hit from the sugar, and prevents the cognitive decline that comes with hypoglycaemia. Riders who stop eating in the last hour because "I'm nearly done" often crack mentally before they crack physically. The brain needs glucose to function. Keep feeding it.
Cadence check. Fatigue drops cadence unconsciously. Riders who started at 90rpm are often grinding at 75rpm by hour five without realising it. Lower cadence shifts more load to the muscular system and less to the cardiovascular system — which sounds efficient, but fatigued muscles respond badly to high force per revolution. Consciously bring cadence back up to 85-90rpm and the effort will feel lighter even if the power stays the same.
Remember the plan works. If you're still riding at mile 75 and you paced correctly and you fuelled correctly, you will finish. The discomfort is not a sign of failure. It's the expected cost of asking your body to work for six hours. You planned for this. It's fixable. Keep pedalling.
Putting it all together
A 100-mile ride is an exercise in compounding small decisions over a very long time. No single gel, no single pacing choice, no single bottle of fluid decides the outcome. But each one either adds to a total that lets you finish strong or subtracts from it until the deficit becomes too large to cover.
The principles are simple. The intensity ceiling is 65-75% of FTP. Fuelling starts in the first 20 minutes and runs at 60-90g per hour with a timer to keep it honest. Front-load calories in the first two hours when the gut works best. Hydrate to 500-750ml per hour with sodium. Expect the hour 4-5 low point and ride through it with reduced intensity and different food. Use the final quarter for process goals and keep the cadence up.
None of this requires talent. It requires a plan and the discipline to follow it when the legs say "faster" at mile 10 and the brain says "slower" at mile 70. The riders who finish centuries looking like they could do another 50 miles are not fitter than the riders crawling home at half their starting power. They just made better decisions in hour one.
If you want to build a specific fuelling and pacing plan for your next long event — your per-hour targets, your intensity ceiling, your feed schedule — the Fuelling Calculator, Hydration Calculator, and FTP Zone Calculator will give you the numbers. And the Calories Burned Calculator is worth running beforehand to see the total energy cost of the ride, because knowing the bill before you start is the only way to make sure you've packed enough to pay it.
Got a century or a long sportive coming up and want to plan it properly? Come talk pacing and fuelling with us — it's where riders share feed plans, pacing data, and the hard-won lessons from rides where they got it right and rides where they didn't.