Average Ironman Swim, Bike and Run Times at 160 Races

The average Ironman swim, bike and run times at a 70.3 are about 40 minutes, 3:00 and 2:04. At a full Ironman they are about 1:20, 6:11 and 4:38. I got these by pulling the typical swim, bike and run from 160 races in my race results database and taking the middle race. The bike is about half the day at both distances, the run a bit over a third and the swim about a ninth.

What I didn't expect was how far the courses sit apart. At the slowest 70.3 the typical bike takes about an hour longer than at the fastest. A few swims also looked too quick to be real. Below I go through the averages, what they mean as pace, the fastest and slowest races, and the odd swims. For finish times by age group, see my average 70.3 finish time and average Ironman finish time posts.

Average Ironman 70.3 swim, bike and run times

For each of 117 Ironman 70.3 races I took the typical finisher's swim, bike and run, then looked at the middle race. The second column covers most races, from the 10th to the 90th percentile. Transitions aren't in these numbers. I left one race out of the swim row, because its swim was shortened (more on that below).

The three typical splits add up to 5:44. That is a little under the 6:00 typical finish in my 70.3 finish time post, because the median of the parts never adds up exactly to the median of the whole. The bike range is the one that caught me. Most races fit inside a 30 minute window on the bike, and the two extremes are over an hour apart.

Average full Ironman swim, bike and run times

Same exercise for 43 full Ironman races. Again one swim was shortened and one race's bike times were adjusted, so each of those is left out of its own row.

These add up to 12:09. The bike range is about 78 minutes wide and the run range is 61 minutes wide, so the race I pick can change the day by more than an hour.

The same splits as pace

Times mean more to me when I can set them next to what I do in training, so I turned the typical splits into pace. At both distances the typical swim works out to about 2:06 per 100 metres. The bike is about 29.9 km/h at a 70.3 and 29.1 km/h at a full Ironman. The run is where they differ. The typical run is 5:52 per km at a 70.3 and 6:35 per km at a full Ironman, about 12% slower.

So if you can hold about 2:06 per 100 metres, 30 km/h and a run under 6:00 per km off the bike, you are looking at the typical 70.3 finisher. That's just arithmetic on the medians.

Fastest and slowest races for each leg

These are the extremes at each distance. At a 70.3 the fastest and slowest bike are 2:35:39 at Tours Metropole and 3:36:52 at San Salvador, a gap of just over an hour. The quickest swims in both tables are odd, and I come back to them below.

Ironman 70.3 Goa sits at the slow end of all three legs. It has the slowest swim and run and the second slowest bike, 3:34:57. I haven't looked into why.

The bike gap at the full distance is bigger. The typical rider at Ironman Wales takes about 1:46 longer than the typical rider at Les Sables. If you want to know how hard a course is overall, my rankings combine these legs. Start with the toughest 70.3 courses and the hardest full Ironman courses, or look at the fastest 70.3 bike courses and the fastest full Ironman bike courses.

Swim times that look too fast

I need to flag the swims. Two races had a shortened swim, so I took them out of the swim row. Ironman 70.3 Gulf Coast 2026 had a typical swim of 12:19. A race report says IRONMAN shortened the swim because of overnight swells and cut the pro swim to about 1,000 metres. It doesn't say what the age groupers swam, but 12 minutes tells me they swam short too. Ironman Taiwan 2025 had a typical swim of 42:36. The Taipei Times reported the swim was cut from 3.8 km to 1.9 km because of rough seas.

Nine more 70.3 races have a typical swim under 30 minutes. For a 1.9 km swim that means a pace faster than about 1:35 per 100 metres for the middle of the field. I looked up what I could.

A downriver swim is a real result, just a quicker course. Maine and Tri-Cities both describe theirs that way, and Triathlete's review of 2023 swims had Maine and Oregon among the fastest 70.3 swims. It also called the quick Chattanooga and California swims at full distance river swims, and they are the two fastest full-distance swims left in my data. For the other races in the table I haven't found out whether it was a current or a shortened swim, so I wouldn't use them to judge your own swim.

If I leave those nine out as well, the typical 70.3 swim goes from 40:02 to 40:14. They barely move the average.

Does a slow bike mean a slow run?

I wondered whether the courses that are slow on the bike are slow on the run too. Mostly they go together, but not tightly. Across races the link is about 0.5 at both distances, where 1 would be a perfect match. Goa is the clearest case in the 70.3 table above. I haven't tested whether heat, hills or wind is behind it, so I'd call this a pattern and leave it there.

How I'd use these numbers

The swim is the leg where I have the most room to improve. For the bike, I'd check the bike split of the race I'm thinking about against the 3:00 typical 70.3 bike. If a course runs 3:20, that's about 20 minutes of the day I'm not going to train away. Then I'd look at the run the same way. If you want your own predicted time at a specific race, put your swim, bike and run into the race time estimator. If you are choosing a first 70.3, my most beginner-friendly 70.3 races post uses the same race data.

About the data

• I read the typical swim, bike and run from each public race page on 12 November 2026. Each one is the median split of the finishers at that race.
• I kept the latest 2025 or 2026 edition of each race with at least 300 finishers and splits shown. That left 117 Ironman 70.3 races and 43 full Ironman races, with 240,060 finishers in all. I left out the World Championship pages.
• I left Ironman Maryland 2026 out of the full-distance bike numbers. A crash around km 133 stopped riders for up to about nine minutes, and IRONMAN removed the 109 to 133 km stretch from everyone's bike split and finish time, so its bike times can't be compared with other races.
• I also left Gulf Coast 2026 and Taiwan 2025 out of the swim numbers, because their swims were shortened.
• Typical race is the median of the race medians. Most races is the 10th to 90th percentile of races. Splits cover finishers only, and transitions are not included.
• Pace uses a 1,900 m swim, 90 km bike and 21.0975 km run at a 70.3, and a 3,800 m swim, 180 km bike and 42.195 km run at a full Ironman.
• My 70.3 finish time post uses a slightly different set of races, so its typical swim and total are a little different from the numbers here.
• I haven't checked course changes, weather or wetsuit rules at each race. Other pages with average splits, such as Marathon Handbook's, merge several sources and don't list the races, which is why I did my own count.