Ironman Nutrition Case Study for a 12-Hour Race

A 12-hour Ironman is not won by finding a gel you like at kilometre 30 of the run. It is won by arriving with a nutrition plan that has been tested under load, adjusted for conditions and simple enough to execute when your decision-making is compromised. This Ironman nutrition case study follows a realistic age-group athlete through the numbers, the choices and the adjustments that protect performance across a long day.

The athlete is a 78 kg triathlete targeting a 12-hour finish: 1:15 swim, 6:10 bike, 4:10 run, plus transitions. They have trained consistently, tolerate carbohydrates well when they are practised and expect moderate conditions of 18-21°C. The objective is not to consume the maximum possible amount. It is to maintain carbohydrate availability, replace a meaningful proportion of fluid and sodium losses, and reach the marathon with a stomach that still works.

The Ironman nutrition case study: starting with demand

A race plan must reflect duration and intensity. For an event lasting around 12 hours, muscle glycogen alone is not enough. Even with a substantial pre-race carbohydrate intake, the athlete will need to take in energy consistently from the bike onwards. The bike is the primary fuelling window because power output is controlled, drinking is easier and gut tolerance is generally better than it is on the run.

For this athlete, the target is 80 g of carbohydrate per hour on the bike and 65-70 g per hour on the run. That sits within the commonly used 60-90 g per hour range for long-course racing, but it is not a universal prescription. An athlete who has only trained at 50 g per hour should not jump to 90 g on race day. Gut training is training.

The plan also starts with a sweat-rate estimate. In a representative two-hour brick session at similar effort and temperature, the athlete loses 1.0 litres per hour after accounting for fluid consumed. This does not mean they need to drink 1.0 litre every hour in the race. Full replacement is rarely practical and can create its own problems. It does establish that 650-750 ml per hour is a sensible starting range, to be adjusted for heat, wind, rain and the reality of aid-station access.

Sodium is set at 800 mg per hour. The athlete has visible salt marks on kit after long sessions, has previously cramped late in hot races and has tested this intake without gastrointestinal distress. Sodium needs vary widely. A lower-sweat athlete racing in cool weather may need closer to 400-600 mg per hour, while a salty, high-volume sweater in significant heat may require more than 1,000 mg per hour. The right number is the one supported by training data and repeated practice, not the biggest number on the packet.

Before the swim: arrive fuelled, not full

The plan begins 36-48 hours before the gun. Training load drops, carbohydrate intake rises and fibre is reduced modestly if the athlete is prone to pre-race bowel urgency. This is not an excuse for an uncontrolled pasta feast. It is a deliberate shift towards familiar, carbohydrate-rich meals that top up glycogen without introducing unfamiliar foods.

On race morning, three to four hours before the start, the athlete eats roughly 2 g of carbohydrate per kilogram of body mass: about 155 g. Porridge, toast with jam, a banana and a sports drink can achieve this without excessive fat or fibre. They drink to thirst alongside the meal, rather than forcing large volumes of plain water.

Fifteen minutes before the swim, the athlete takes 20-25 g of carbohydrate with a few mouthfuls of water. This is not about fixing a deficit. It is about starting the day with a clear, rehearsed routine and avoiding the temptation to chase energy after the swim.

The swim changes nothing - but transition does

There is no need to fuel during a 75-minute swim for this athlete. The priority is getting through T1 without losing the plan. A gel or concentrated carbohydrate source can be taken immediately after the wetsuit is removed, followed by water as the athlete settles onto the bike. That first intake prevents a common error: waiting until hunger appears. Hunger is a poor race-day alarm system.

The bike: build the race around repeatable hourly intake

Over 6 hours and 10 minutes, the athlete needs approximately 495 g of carbohydrate. Rather than relying on memory, they divide this into repeatable hourly blocks. Each block provides 80 g carbohydrate, 800 mg sodium and around 700 ml fluid.

A practical version might combine carbohydrate from bottles and gels, with electrolyte sachets mixed at the concentration already tested in training. The format matters less than the accounting. If a bottle contains 40 g of carbohydrate and two gels provide 20 g each, the athlete has one clear hourly unit. They know what one hour looks like, and they can see whether they are falling behind.

The first two bike hours are deliberately calm. The athlete takes the full target despite feeling fresh, sipping fluid regularly and taking carbohydrate every 15-20 minutes. This steady approach is preferable to taking a large dose every 45 minutes, particularly for athletes with a history of bloating or reflux.

At the halfway point, conditions are warmer than forecast. The athlete has already finished slightly more fluid than planned and has urinated once, pale yellow, before getting on the bike. They increase fluid towards 800 ml per hour for the next 90 minutes but keep sodium concentration consistent. Increasing plain water without replacing sodium can dilute the drink strategy and leave the athlete feeling sloshy.

The final 45 minutes of the bike is where discipline matters most. Many athletes back off fuel because they are preparing mentally for the run. That simply transfers the problem to the marathon. This athlete continues taking carbohydrates, has one final planned gel 15 minutes before T2 and avoids experimenting with solid food. The goal is to run off the bike with energy coming in, not to hope that breakfast lasts.

The run: protect the gut and keep moving forward

The run target is 65-70 g carbohydrate per hour, producing roughly 275 g across a 4:10 marathon. Intake is slightly lower than the bike target because impact, heat and fatigue reduce digestive comfort. It is still substantial enough to support pace and preserve concentration.

The athlete uses aid stations to create a simple rhythm: a gel every 25 minutes, water at each station and electrolyte drink in measured amounts. If the race offers cola late in the marathon, it can be useful for carbohydrate, caffeine and a change of flavour. It should be a planned option, not a rescue strategy introduced after the stomach has already failed.

At kilometre 24, the athlete reports mild nausea. The wrong response would be to stop all intake for an hour. That often turns a manageable issue into an energy collapse. Instead, they reduce the size of each carbohydrate dose, take water in small sips, walk 20-30 seconds through the next aid station and reassess. The hourly target may fall to 55-60 g temporarily, but the system stays active.

This is the central trade-off in long-course racing. Perfect numbers are useful, but only if the athlete can absorb them. A slightly lower intake that continues is better than an aggressive plan that triggers vomiting, diarrhoea or a complete refusal to fuel.

What this athlete would test before race day

This plan should never appear for the first time on race morning. The athlete needs several long rides at 80 g per hour, brick sessions that include the transition from bike intake to running, and at least one warmer session where fluid and sodium needs are tested. They should also practise opening packaging with tired hands, carrying the required fuel and mixing bottles accurately.

A structured system such as truefuels can simplify those repetitions by keeping carbohydrate and hydration decisions consistent. But the system only works when the athlete records what happened: grams per hour, fluid consumed, sodium taken, weather, pace, stomach comfort and perceived energy. That record turns guesswork into a usable race protocol.

The lesson from the numbers

The athlete finishes in 11:54. They do not feel brilliant for every minute of the marathon, because Ironman racing is not designed to feel comfortable. They finish with a controlled fade rather than a nutritional collapse, having taken in approximately 780 g of carbohydrate, maintained fluid intake through changing conditions and adapted without abandoning the plan.

Your own numbers may be lower, higher or distributed differently. Start with what your gut tolerates, test it repeatedly at race intensity and make every hour easy to execute. On an Ironman day, precision is not complexity. It is knowing exactly what comes next when the race gets hard.