The swim is about 11% of your 70.3 finish time. Yet in one half-Ironman study, age-groupers put 28% of their training load into the swim. A better starting split is about 20% swim, 45% bike and 35% run.
That’s a starting point, not a law. Here’s where it comes from and how to bend it.
Why Equal Thirds Misses the Race
Equal thirds feels fair. It isn’t how the race works.
Take the average male age-grouper at a 70.3. The reported splits are 38:51 swim, 2:54:38 bike, 2:04:16 run and 13:40 in transitions, for a 5:51:25 finish. Do the division and you get the shares below. Women’s averages come out nearly the same. These shares are our own math from average split data, not a published figure.
In short: the bike is half the day, the run is a third, and the swim is a sliver.
Now compare that to what recreational triathletes actually do. In a 13-week half-Ironman study, athletes trained about 11.9 hours a week. Their training load split about 28% swim, 38% bike and 34% run (Selles-Perez et al., 2019). Race time in that same group ran about 11.8% swim, 53.2% bike and 35.0% run.
Translation: the swim got more than twice its race share. The bike got less.
Think of your weekly hours as a grocery budget. Spend a quarter of it on the cheapest item on the list and you’ll run short on the big ones.
Does that mean skip the pool? No. Swim is a skill sport, and a bad swim costs energy for the next five hours. But an extra swim hour buys less race-day speed than an extra ride hour.
The Leg That Predicts Your Finish
Researchers studied 823,459 age-group finishers across 787 races. Run time correlated 0.89 (women) and 0.90 (men) with overall time. Bike correlated 0.87 and 0.86 (Nikolaidis et al., 2023). Swim came in lowest.
In plain words: how you bike and run tells you most of how you finish.
Among pros, bike correlated 0.85 with finish time, run 0.75 to 0.82 and swim 0.46 to 0.63 (Frontiers, 2024). The authors note this is pro data, so treat it as a partial guide for age-groupers.
Bike and run decide the day. Swim just sets the stage.
How to Split Training Hours at 6, 9 or 12 a Week
Want the total hours question answered first? Read how many hours a week a first 70.3 needs. This post covers only the split.
The numbers below are AthleteOS suggested starting points. They are not study data.
| Weekly hours | Swim | Bike | Run | Sessions |
|---|---|---|---|---|
| 6 | 1.5 h | 2.5 h | 2.0 h | 2 / 2 / 2 |
| 9 | 2.0 h | 4.0 h | 3.0 h | 3 / 3 / 3 |
| 12 | 2.5 h | 5.5 h | 4.0 h | 3 / 4 / 3 |
That’s about 22/45/33 at 9 hours. For a full-time-job layout, see an 8-hour 70.3 week.
For a Slowtwitch snapshot, forum athletes report splits like 22/50/28, 25/35/35 and 12/64/24. The modal answer sits near 20 to 25% swim, 40 to 50% bike and 25 to 35% run. That matches the table. Nobody ties it to race distance, though, so don’t treat forum numbers as proof.
What Changes at a Full Ironman
Everything above is 70.3 math. A full Ironman shifts the picture, but the research is thin, so treat these points as coaching context.
The bike gets even bigger. One Ironman Wisconsin finisher posted a 1:11 swim, 7:30 bike and 4:30 run. That bike is about 58% of a roughly 13-hour day. The run is smaller by share, yet it hurts more when you’re tired.
The swim is a gate, not a prize. One Slowtwitch analysis of Ironman Texas found swimmers slower than 1:30 were far less likely to finish. So a beginner needs enough pool time to clear the cutoff, then no more.
Time is the other squeeze. A swim coach on the same forum pegs competitive age-groupers at about 5 hours a week. On a 9-hour week, that would eat more than half your time. Go much past that and the bike, which is half your race, gets squeezed.
Translation: the longer the race, the less the pool pays back per hour. We have no sourced split for sprint or Olympic races, so we won’t invent one. Start from the 70.3 table and ask a coach.
Hours Aren’t Equal: Run Costs More
An hour of running is not an hour of swimming. Running pounds your joints. Swimming doesn’t.
Injury reviews put triathlon injuries at 0.7 to 1.4 per 1,000 training hours. About 50% are running injuries, 43% cycling and 7% swimming (Etxebarria et al., 2019). Run is about 35% of 70.3 race time but half of injuries.
Here’s the honest part: the evidence on run volume is mixed. In one Spanish survey, injured triathletes ran 28.6 km a week versus 25.6 for uninjured ones, but the gap was borderline (p=0.06). A separate survey of 384 endurance athletes linked more run volume and frequency to fewer injuries.
So don’t cap run hours out of fear. Build them slowly, and spread them over more short runs instead of one long one.
Heavy run weeks are the leaky pipe in your plan. Patch them before you pour in more volume.
How Bike and Run Intensity Should Differ
Elite data shows swim is the hard-hitting sport. One world-class female Olympic-distance triathlete did 74% of swim, 88% of bike and 85% of run training below lactate threshold. A world-champion paratriathlete did 82%, 91% and 88%.
Translation: ride and run mostly easy. Save hard work for the pool and a few key sessions. Zone 2 builds that easy base.
Cycling is easier on the body, so you can tolerate more intensity there than in running. That’s why a hard ride is a smaller injury bet than a hard run.
Case Study: Dan Moves Four Hours
Dan, 41, trained 10 hours a week for a June 70.3. His split was 3.5 h swim, 3.5 h bike and 3.0 h run. His swim was solid at 38 minutes. His bike was slow, and he walked the last 3 km of his last race.
In week 1 of his build (illustrative numbers) he moved to 2 h swim, 5 h bike and 3 h run. He kept two swim sessions short and focused. He rode more easy miles and added one 2.5-hour long ride. His race swim slipped about 2 minutes. His bike dropped about 11 minutes, and he ran the whole half marathon.
He gave up 2 minutes in the water to gain far more on the road.
When to Shift Toward Your Weakest Leg
Fast Talk Labs says equal training suits new triathletes, while advanced athletes benefit from unequal distribution. Fair enough.
Use a simple rule. Hold the starting split for 8 weeks. Then move 30 to 60 minutes a week from your strongest leg to the weakest. Keep that shift for 4 weeks, then check results.
Moving hours toward the run is where people get hurt. Follow these steps:
- Add run time as extra short runs, not a longer long run. Go from 3 runs to 4 before you stretch any single run.
- Move only 30 minutes at a time. Wait a full week before adding more.
- Keep the new run minutes easy. Hard run work stays where it was.
- Take the hours from the swim or bike, not from sleep or recovery.
- If a calf, shin or knee gets sore, hold the run hours where they are for a week.
Weakest-leg work isn’t about doing more. It’s about moving the same hours to where they pay.
Beginners who can’t swim 400 meters without stopping are the exception. A short block of 3 swims a week will help.
Track the Split, Not Just the Total
Your watch gives you total hours. It doesn’t tell you the split drifted to 30% swim in a busy month. AthleteOS shows swim, bike and run hours side by side in your training plan, planned versus completed, so drift shows up early. When a missed week eats your ride, the AI coach rebalances what’s left. Start the 14-day trial and see your real split.
For brick sessions that blend bike and run hours, see how often and how long to do bricks.