Race-day fueling
Triathlon Aid Station Nutrition Planner
Turn bike and run duration into bottles, gels, carbs, sodium, and aid-station timing without burying the pacing calculator.
Bike duration
Run duration
Carb plan
375g
Total bike + run carbs
Bike bottles
4
Bike gels
0
Run gels
6
Aid stations
10
Bottle timing
45 min
Sodium
3500 mg
Nutrition checks
- Practice this plan in long sessions before relying on it in a race.
Connect fueling to pacing
Why 90g per hour is a ceiling, not a target
Carbohydrate absorption is limited by transport, not by appetite. Glucose crosses the intestinal wall through the SGLT1 transporter, which saturates at roughly 60g per hour. Eat more glucose than that and the excess simply sits in your gut, drawing water in and producing the bloating, nausea, and sloshing that long-course athletes know well.
The way past that ceiling is fructose, which uses a different transporter (GLUT5) entirely. Combining glucose and fructose lets you use both pathways at once, and the research on multiple transportable carbohydrates — the basis for the modern 60-90g guidance — showed meaningfully higher oxidation rates than glucose alone. This is why nearly every long-course sports nutrition product now advertises a glucose to fructose ratio.
Two practical consequences follow. First, hitting 90g per hour requires products with a mixed carbohydrate source; you cannot get there on maltodextrin alone. Second, the gut is trainable. Absorption capacity increases with repeated exposure, which means the athlete who has practised 90g per hour in training can use it, and the athlete who tries it for the first time on race day usually cannot.
Practical carbohydrate targets by race duration
Sensible starting points for planning. Every figure assumes you have rehearsed the intake at race intensity, not just tolerated it on an easy ride.
| Race duration | Carb target | Practical approach | Main risk |
|---|---|---|---|
| Under 1 hour | 0-20 g/hr | Water is usually enough; stored glycogen covers the effort | Overthinking it |
| 1-2 hours | 30-45 g/hr | One bottle of sports drink or a gel per 45 minutes | Starting under-fuelled |
| 2-3 hours | 45-60 g/hr | Single-source glucose products are still sufficient | Late-race fade |
| 3-5 hours (70.3) | 60-80 g/hr | Mixed glucose-fructose needed above about 60 g/hr | Gut distress on the run |
| 5+ hours (Ironman) | 70-90 g/hr | Mixed sources, most intake on the bike, smaller doses on the run | Absorption failure and bonking |
Bodyweight matters: a common way to sanity-check the target is 1.0-1.2 g of carbohydrate per kg of bodyweight per hour for long-course racing.
Fuel the bike, survive the run
The bike and the run are not equivalent fueling environments, and planning them identically is one of the most common errors this planner is meant to prevent. On the bike you are stable, your torso is relatively still, blood flow to the gut is higher because the effort is lower, and you can carry everything you need. On the run you are being jolted vertically, gut blood flow has dropped, and you can only carry what fits in a belt.
The practical rule is to front-load. Take the majority of your total carbohydrate on the bike, at the highest rate you have trained, and plan the run around smaller, more frequent doses — a gel every 20-25 minutes rather than large volumes. If you arrive at T2 already behind on fuel, the run is not where you will catch up.
Aid-station spacing is what turns this from theory into a plan. Knowing that run aid stations sit roughly every 2km lets you attach each dose to a physical landmark instead of relying on remembering a schedule at hour six, when arithmetic is the first thing to go.
Sodium, fluid, and the hyponatremia trap
Sweat contains sodium, and sweat rates vary enormously between athletes — both the volume and the salt concentration are largely individual. That makes generic sodium advice weak, but the failure modes are worth understanding.
Under-replacing sodium during a long hot race contributes to cramping and, at the extreme, to exercise-associated hyponatremia: dangerously diluted blood sodium. The counterintuitive part is that hyponatremia is usually caused by drinking too much plain water, not by sweating too much. Athletes who drink to a schedule rather than to thirst, in a long race, in the heat, are the classic case.
The ACSM position stand on exercise and fluid replacement is the standard reference and is cited on our methodology page. Its practical summary: drink largely to thirst, include sodium in long events, avoid losing more than about 2% of bodyweight, and do not force fluid beyond what thirst and sweat rate justify.
Rehearse the plan, then simplify it
Everything this planner produces should be tested in training before it is trusted in a race. Use your longest ride to practise the exact products, the exact hourly rate, and the exact timing. A plan that works at 60% effort on a Sunday morning is not evidence that it works at race intensity in the heat.
Then simplify. The best race nutrition plans are the ones you can execute while tired and slightly stupid: a fixed number of items per hour, attached to landmarks you cannot miss. Complexity is the enemy at hour seven. If the plan needs a spreadsheet on race day, it is the wrong plan.
Finally, know what is on course. Most races publish which drink and gel brands will be at aid stations. Training on those products means you can carry less and still recover from dropping a bottle — and a dropped bottle should never be the thing that ends your race.
How to use the schedule
Enter realistic bike and run durations from your race plan, then choose carb, bottle, gel, fluid, and sodium targets you have already practiced. The output should become a training rehearsal and shopping list, not a brand-new race-day experiment.
- Plan bike intake first because it is easier to absorb steadily.
- Use the run schedule as smaller, more frequent checkpoints.
- Practice the exact products, dose, and timing before race day.
Example race read
For a 3-hour bike and 2-hour run at 75 g/hour, the athlete needs about 375 g carbohydrate total. That might mean two carb bottles plus gels on the bike, then smaller gel or drink doses at predictable run aid stations.
Common mistakes
Most bad plans fail because they count total calories but ignore timing. Taking in too much too late can leave the gut overloaded when the run starts. A useful nutrition plan spreads intake early enough that the bike sets up the run.
When to be conservative
Use lower targets when your gut training is limited, the race will be hot, or the aid-station products are unfamiliar. A slightly smaller plan that you can repeat calmly is usually better than an ambitious number that collapses after one missed bottle.
Next best calculators
Frequently asked questions
- What does an aid-station nutrition planner do?
- It turns bike and run duration into a practical schedule of bottles, gels, carbs, sodium, and aid-station checkpoints.
- How many carbs per hour should I target?
- Many long-course athletes target roughly 60-90 g/hour. Higher targets can work, but should be trained before race day.
- Should bike and run fueling be the same?
- Often no. The bike is usually easier for steady intake, while the run may need smaller and more frequent doses.
- Why can't I just eat more carbohydrate per hour?
- Because absorption is limited by intestinal transport rather than by how much you can swallow. Glucose uses the SGLT1 transporter, which saturates around 60g per hour; anything beyond that sits in the gut drawing in water and causing bloating and nausea. Fructose uses a separate transporter, so combining glucose and fructose raises the usable ceiling to roughly 90g per hour - which is why long-course products advertise a glucose-to-fructose ratio.
- Can I train my gut to absorb more?
- Yes. Absorption capacity adapts to repeated exposure, so athletes who practise high intake rates in training tolerate them far better on race day. Build up gradually on long rides using the exact products you intend to race with. Attempting 90g per hour for the first time in a race is one of the most reliable ways to end up walking.
- How much sodium do I actually need?
- It depends heavily on your individual sweat rate and sweat sodium concentration, both of which vary widely, so generic numbers are weak. What matters more is avoiding the two failure modes: under-replacing sodium across a long hot race contributes to cramping, while drinking large volumes of plain water on a schedule rather than to thirst can dilute blood sodium dangerously. Include sodium in long events, drink largely to thirst, and aim not to lose more than about 2% of bodyweight.
Trust and methodology
How this page should be used
Last updated
August 8, 2026
Maintained by
M Imtinan Farooq
Status
Planning estimate, not a race guarantee
Formula summary
Total intake = bike/run duration x hourly carb and sodium targets.
Key assumptions
Product carbs, aid spacing, and hourly targets match what you have practiced.
Limitations
Gut tolerance, sweat rate, heat, and product choice vary by athlete.