Late in an Ironman marathon, your mind stops asking for your split and starts asking what your legs have left. The answer often arrives around mile 18, after you've already swum 2.4 miles and ridden 112. That's the basic shape of Ironman racing: a 2.4-mile swim, a 112-mile bike and a 26.2-mile run that arrives on already tired legs. On paper the run is a marathon. In practice it's a different event.

Strong open-road marathoners can feel genuinely confused by how hard the Ironman run becomes. That isn't a fitness problem. It's an ordering problem. By the time your shoes are on for the run, you've been racing for seven hours or more, burning through stored glycogen, fluid, sodium and the early stages of muscle damage. The run asks your body to produce a familiar motion from a very unfamiliar starting point.

Why strong runners struggle after the bike

At mile 80 of the bike, most athletes have been in an aero position, the low tucked posture used on a triathlon bike, long enough to shorten hip flexors and stiffen the lower back. Standing up to run after five or six hours like that is difficult for mechanical reasons, not a matter of will. The first two miles often feel wooden because the muscles that drive running have been holding a seated pedal stroke, not absorbing ground contact.

Add fueling. A marathoner starts with full glycogen stores. An Ironman athlete reaches the run after many hours of burning calories across swim and bike, often at an hourly deficit. When the run starts, the tank isn't empty, but it is thinner than in any standalone marathon build-up. That's why Ironman run pacing and open marathon pacing have so little in common.

There is also the simple effect of heat. Most Ironman races run through midday and into evening. A runner who can hold 8:00 miles in a cool fall marathon may be running in 85-degree sun after a 112-mile ride, which changes cardiac drift, the gradual rise in heart rate at a steady effort, and sweat losses. You're not slower because you lost fitness; you're slower because the conditions and the preceding effort demand it.

Pacing from the first mile

Adrenaline after T2, the bike-to-run transition, makes the opening pace feel easy, and many first-timers go out 30 to 60 seconds per mile faster than they can sustain. That decision is collected later, usually around mile 16, with heavy legs and a stomach that no longer wants gels.

Experienced triathletes often start the run at a pace that feels too slow for the first 10K. A useful cue is to run the first hour at a heart rate five to ten beats lower than your usual long-run effort, or at a perceived effort of 5 out of 10. If you can't speak in short sentences during the first two miles, you're pricing in a late-race walk.

Many Ironman athletes use a run-walk strategy from the first aid station rather than waiting until they're forced to walk. Walking aid stations gives you time to drink properly, take calories, and let the heart rate settle while you scan the road ahead. It sounds slower, but a short walk every mile can protect the rhythm that a continuous jog destroys by mile 20.

Brick workouts and the training hierarchy

A brick session is a bike ride followed immediately by a run. The name comes from the heavy feeling in your legs during the first minutes off the bike. For Ironman athletes, the brick is not a weekly punishment. It's a neurological lesson: teaching the body to accept the switch from cycling to running without letting the first half mile turn into a panicked shuffle.

One practical Ironman brick might be a 2-hour ride with the final 45 minutes at race effort, followed by a 20-minute run off the bike. Start the run at goal Ironman marathon pace, not open marathon pace. The point isn't to finish destroyed; it's to leave the session knowing how the first 10 minutes of the run will feel and how to settle it.

• Ride the final 45 minutes at your expected Ironman bike effort.
• Change shoes quickly and start the run at conversational effort.
• Run 15 to 20 minutes, then walk for two minutes to reset.
• Finish with easy spinning or a short walk, not another hard run.

You'll find detailed brick session layouts at TrainingPeaks. Don't stack hard bricks on top of hard weekends. A long ride plus a short run off the bike is enough when placed every 10 to 14 days. The real Ironman run strength comes from consistent cycling volume and run frequency, not from copying the full race every week.

The Olympic-distance gateway

An Olympic triathlon is a 1.5km swim, a 40km bike and a 10km run. That's the standard set by World Triathlon, the sport's international federation. For a runner coming to triathlon, the 10K is familiar, but the hour-plus of swimming and cycling before it changes the demand. The run is a familiar 10K, but it arrives after your upper body has fought water and your legs have pushed a bike for roughly an hour and ten minutes.

This distance is more beginner-friendly than Ironman because training can fit around a normal working week. A first-timer can build to finishing an Olympic-distance race on four workouts a week: one swim, one shorter bike, one longer bike and one run. A fifth session helps if you want to race, but it isn't required to finish.

The run deserves attention because it is the final discipline and because small mistakes in swim and bike pacing show up in the first mile of the 10K. Strong runners should keep most of their run training familiar while adding one brick run every week or two. That's enough to learn the feeling without sacrificing bike volume.

What to eat when your stomach no longer cooperates

Ironman run nutrition is not simply marathon nutrition multiplied by four. After hours of sweet gels and sports drink on the bike, many athletes arrive at T2 with a stomach that wants salt and real food, not another gel. The most common run-plan error is to keep forcing carbohydrate at the same hourly rate from the bike, even when the gut is slowing down.

Practical approach: aim for 30 to 60 grams of carbohydrate per hour on the run, adjusting to the lower end if your stomach is sloshing. Use aid station water to take gels, and alternate between gels, sports drink and small pieces of banana or pretzels. Sodium matters more in the final marathon because sweat losses are high and overdrinking plain water can make the stomach worse.

You'll see similar advice in Ironman's race-day nutrition resources: eat early and often, but don't force the gut.

Flat cola, broth, salty crackers or even a cup of water with a salt tab often work when nothing else does. They're not magic; they just provide fluid, sodium and a different taste profile that can reset a tired palate. If you reach the point where you can't keep anything down, slow the run, take small sips and let the gut catch up before you force more solid food.

Managing the mental final 10K

When the plan stops working, don't try to solve the whole marathon. Break the remaining distance into the next aid station or the next landmark. A runner who is struggling at mile 20 doesn't need to think about 6.2 miles; they need to reach the next table, take a walk, drink, and leave again.

Experienced triathletes often use a simple internal script: 'run to the next telephone pole, walk 30 steps, then run again to the next marker you pick.' This isn't giving up. It's a contract that keeps you moving when walking the rest feels tempting. The goal in the final hour is to stay in motion and manage the problems you can actually control: fluids, salt, pace and posture.

Expect low moments. They arrive for almost everyone around mile 18 or when the sun drops and the course empties. That's normal and not a sign your race is falling apart. The athletes who finish well are usually not the ones who never walk; they're the ones who keep the walk short and get back to running sooner.

If you come from a marathon background, your pacing instincts are a liability in the Ironman run. The usual marathon strategy of even splits or a slight negative split rarely survives the bike. Instead, think of the run as a 26.2-mile exercise in staying calm while your body gives you reasons to panic.

The best Ironman run is often slower than your open marathon by 20 to 40 minutes, if not more in the heat. Accepting that before the start is what protects you from chasing a number that was never possible on the day. Training should include enough long runs to know you can cover the distance, but the real skill is learning to run at Ironman effort when you're already tired.

Spend your energy in the first half of the run on feeding, hydration and finding a rhythm that you can repeat. Save the hard decision-making for the final 10K, when the only thing that matters is the next mile. The next time you see someone walking an aid station at mile 22 of an Ironman, they're not necessarily falling apart. They may be executing the smartest part of their race.

Photo by Pablo Ulloa on Unsplash