The race is half Ironman distance, but the effort is anything but half-sized
- The standard format is 1.2 miles of swimming, 56 miles of biking, and 13.1 miles of running.
- That adds up to 70.3 miles, or about 113 km, before transitions.
- The swim is short on paper, but technique and open-water comfort carry a lot of weight.
- The bike usually decides how fresh you are when the run starts.
- A realistic build is often 16 to 20 weeks, with roughly 8 to 13 training hours per week depending on the phase and your background.
The exact distances in each leg
According to IRONMAN, the official half-distance format is a 1.2-mile swim, a 56-mile bike, and a 13.1-mile run. I like to think of it as three different endurance problems back to back: the swim demands calm breathing and efficient technique, the bike rewards restraint, and the run exposes every pacing mistake you made earlier in the day.
| Leg | Miles | Kilometers | What it really asks of you |
|---|---|---|---|
| Swim | 1.2 | 1.9 | Efficient stroke, sighting, and open-water control |
| Bike | 56 | 90 | Sustainable power, steady fueling, and patience |
| Run | 13.1 | 21.1 | Controlled pace, hydration, and mental discipline |
| Transitions | Not counted | Not counted | Fast, clean movement between sports |
| Total | 70.3 | 113 | The full race distance, not including time in transition |
That table is the clean version. The real version depends on water temperature, wind, hills, heat, and how well you manage effort from the first five minutes onward. Once you understand the raw numbers, the next question is where this distance sits among the other common triathlon formats.
How it compares with shorter and longer triathlons
British Triathlon’s standard-distance comparison is useful here: Olympic distance is 1.5 km swim, 40 km bike, and 10 km run. That makes the 70.3 clearly longer than an Olympic race, but still far more manageable than a full Ironman, which doubles the swim, bike, and run again to 2.4 miles, 112 miles, and 26.2 miles.
| Format | Swim | Bike | Run | Why it matters |
|---|---|---|---|---|
| Sprint | 750 m / 0.5 mi | 20 km / 12.4 mi | 5 km / 3.1 mi | Fast, sharp, and beginner-friendly |
| Olympic | 1.5 km / 0.93 mi | 40 km / 25 mi | 10 km / 6.2 mi | The classic speed-endurance middle ground |
| 70.3 | 1.9 km / 1.2 mi | 90 km / 56 mi | 21.1 km / 13.1 mi | Long-course racing with a half-marathon finish |
| Full Ironman | 3.8 km / 2.4 mi | 180 km / 112 mi | 42.2 km / 26.2 mi | A full-day endurance test |
For American athletes, this comparison is practical because it tells you what kind of fitness matters most. A sprint rewards speed. A 70.3 rewards restraint, durability, and planning. A full Ironman asks for the same qualities, just stretched over a much longer day. That is why the training approach changes so much as the distance grows.
What the distance means for pacing and training
The mileage on paper does not tell you how much preparation you need, but it does tell you the shape of the work. For many age-group athletes, a sensible 70.3 build is 16 to 20 weeks. I usually think in three phases: base, build, and taper.
| Phase | Typical length | Weekly load | Main goal |
|---|---|---|---|
| Base | 8 to 12 weeks | 8 to 10 hours | Endurance, technique, and consistency |
| Build | 6 to 8 weeks | 10 to 13 hours | Race-specific sessions, pacing, and bricks |
| Taper | 2 to 3 weeks | Reduced volume | Freshness without losing sharpness |
A brick workout, which is a bike session followed immediately by a run, is one of the most useful tools in this distance. It teaches your legs how to switch gears when they are already tired, which matters more than people expect on race day. If you only have time to improve one discipline, I would usually choose the bike first, because it occupies the longest stretch of the race and has a huge effect on the run that follows.
Time-wise, many athletes finish a 70.3 in roughly 5 to 8 hours, depending on fitness, course profile, and weather. That spread is a reminder that the challenge is not just distance. It is how well you control effort across several hours without burning matches too early. From there, the swim becomes the smartest place to gain free time and avoid chaos.
Why the swim takes more technique than mileage suggests
The swim is only 1.2 miles, but I do not treat it as a small piece of the race. It is the leg where poor technique, tension, and panic show up fastest. A strong, efficient swim makes the rest of the day easier; a messy one raises stress, heart rate, and energy cost before you have even reached the bike.
What to practice in the pool
I like swimmers to work on balance, body position, relaxed exhalation, and sighting before they chase more volume. Shorter intervals are more useful than endless steady swimming when the goal is to hold form under fatigue. A lot of athletes build well with two or three swim sessions per week, and one of those should feel like race-specific work rather than casual laps.
If you are building toward a 70.3, a single-session target of roughly 2,500 to 3,500 yards is common, but not all at once. Sets like 10 x 100, 8 x 200, or mixed pace work are more realistic than forcing a nonstop hero swim every time. That approach protects technique while still building the endurance you need for open water.
What gear actually helps
For the swim, the useful gear is usually simple: goggles that fit, a wetsuit if the race allows one, and a suit that does not fight your shoulders. For the day overall, I also care about the small things that reduce friction, like anti-chafe balm, a well-fitted trisuit, and a race setup that lets you move cleanly through transition. None of that makes you faster on its own, but it can save more time and energy than another expensive gadget.Read Also: Ironman Training - Build Durability, Not Just Fitness
The mistakes I see most often
- Starting too hard and paying for it on the bike.
- Ignoring sighting until race day.
- Training only in the pool and never practicing open water.
- Overestimating how much speed raw fitness can buy when technique is inefficient.
The swim is short compared with the bike and run, but it is not a throwaway segment. If you get it right, the rest of the day becomes much more manageable. Once that is in place, the details around race day start to matter even more than the headline distance.
The details that make the distance manageable
What separates a controlled 70.3 from a messy one is usually not heroic fitness. It is course awareness, pacing discipline, and practical execution. A flat, cool course and a hilly, windy, hot one can feel like different sports even though the mileage is the same.
Here is what I would check before race day:
- Course profile - A climbing bike course demands more restraint than a flat one.
- Water conditions - Choppy open water changes breathing, sighting, and confidence.
- Fuel plan - Most of your calories should come on the bike, not after you already feel empty.
- Transitions - Fast is good, but clean is better than frantic.
- Weather - Heat and humidity punish aggressive pacing far more than athletes expect.
- Equipment checks - Test goggles, nutrition storage, shoes, and the saddle position before race morning.
I also think it helps to remember that the distance is fixed, but the experience is not. Two athletes can both race 70.3 and have very different days depending on how well they swim, how smart they ride, and how much they can still run when fatigue arrives. If you keep the swim efficient, ride with patience, and treat the half marathon as a controlled finish rather than a sprint, the event becomes much more manageable.
That is the real value of understanding the distance: it stops being a scary number and turns into a set of decisions you can train for. If I were preparing now, I would spend my first energy on open-water swim comfort, steady bike pacing, and a fueling plan I had already practiced under fatigue.
