Tri Toolkit
Race › Guide

How to Pace a 70.3 or an Ironman

Updated 2026-11-21

Ride a 70.3 at about 80–85% of your FTP and an Ironman at about 65–75%, with first-timers at the low end. Keep the power steady rather than chasing speed on hills, and start the run slower than feels necessary for the first few kilometres. In long-distance triathlon the bike decides the run: almost every bad marathon or half marathon started with a bike ridden too hard.

Why the bike decides your run

The bike is the longest leg in time for almost everyone. That alone makes it the place where you can lose the most time. But the bigger effect is what it does to the run. Ride a little too hard and you feel fine for three hours, then pay for it with interest once you start running.

That is why every serious pacing guide, from TrainingPeaks coaches to the power-analysis tools, works backwards from the run. The question is not “how fast can I ride 90 or 180 km?” but “how hard can I ride and still run well?”. The honest answer is lower than most people think, and the gap between the two is where races are won and lost Coaching practice.

The numbers below come mostly from coaches and from analysis of power files, not from controlled trials. We mark them that way. They are still the best guidance available, and they agree with each other more than they disagree.

70.3 bike: about 80–85% of FTP

For a 70.3, a TrainingPeaks coach Q&A puts the bike at an intensity factor of 0.80–0.85. Intensity factor (IF) is your normalized power divided by your FTP, so 0.80 means 80% of FTP. With an FTP of 250 watts, that is about 200–213 watts Coaching practice.

Where you land in that range depends on three things:

  • Experience. If it is your first 70.3, start at 0.80. You can always run faster in the last 5 km; you cannot undo the first hour of the bike.
  • Your run. Strong runners have more to lose from a hard bike, so they usually ride nearer the bottom of the range.
  • The course. Heat, hills and wind all argue for the lower end (more on that below).

Not every source gives the same number. Some coaches and pacing tools quote slightly lower or wider ranges for a 70.3, and most agree that weaker or less experienced athletes should go lower. We use 80–85% because it is the one published range we could trace to a named coach, and because it sits in the middle of what others say. Treat it as a ceiling, not a target to hit at all costs.

You can work out your own numbers in the race pacing planner: enter your FTP and expected bike time, and it gives you a target, a range and, for an Ironman, a check of the total load.

Ironman bike: intensity factor and the TSS budget

For a full Ironman the range drops to about 0.65–0.75. Two sources agree on it: TrainingPeaks’ “Lessons from Kona” analysis, which puts a first Ironman at 0.65, and Best Bike Split, which calls 0.68–0.72 the sweet spot for most people. The TrainingPeaks coach Q&A is a little higher at 68–78% Coaching practice.

The difference from a 70.3 is not only the percentage. A full Ironman bike can take anywhere from under five to over seven hours, and a slow rider at a given IF accumulates far more fatigue than a fast rider at the same IF. That is what Training Stress Score (TSS) captures:

TSS = bike hours × IF² × 100

Joe Friel uses this formula to explain Ironman pacing on TrainingPeaks, and coach Rick Ashburn’s chart, reproduced by Best Bike Split, puts a number on it: a bike TSS of about 250–285 is the good range for well-prepared age-groupers, and above that the run increasingly suffers Coaching practice.

Ironman bike TSS by bike time and intensity factorTraining Stress Score for an Ironman bike, from bike hours times intensity factor squared times 100. Below 250 is conservative, 250 to 285 good, 285 to 310 risky, above 310 too high. IF 0.80: 4:30 288, 5:00 320, 5:30 352, 6:00 384, 6:30 416, 7:00 448. IF 0.78: 4:30 274, 5:00 304, 5:30 335, 6:00 365, 6:30 395, 7:00 426. IF 0.75: 4:30 253, 5:00 281, 5:30 309, 6:00 338, 6:30 366, 7:00 394. IF 0.72: 4:30 233, 5:00 259, 5:30 285, 6:00 311, 6:30 337, 7:00 363. IF 0.70: 4:30 220, 5:00 245, 5:30 269, 6:00 294, 6:30 318, 7:00 343. IF 0.68: 4:30 208, 5:00 231, 5:30 254, 6:00 277, 6:30 301, 7:00 324. IF 0.65: 4:30 190, 5:00 211, 5:30 232, 6:00 254, 6:30 275, 7:00 296.0.802883203523844164480.782743043353653954260.752532813093383663940.722332592853113373630.702202452692943183430.682082312542773013240.651902112322542752964:305:005:306:006:307:00bike time (h:mm)intensity factorTraining Stress Scoreunder 250 conservative250–285 good285–310 riskyover 310 too high
TSS = bike hours × IF² × 100 (Friel, TrainingPeaks). Bands after Ashburn's chart via Best Bike Split. The same intensity factor that is fine on a five-hour bike is too much on a seven-hour bike.

Read the chart across a row. At IF 0.70, a 5:00 bike gives a TSS of 245 and a 6:30 bike gives 318. The slower rider is riding at the same percentage of FTP but doing far more work in total. For them, 0.65 (TSS 275) is the better target.

FTP 250 watts IF Target power TSS at 5:30 TSS at 6:30
First Ironman 0.65 about 163 watts 232 275
Middle of the range 0.70 about 175 watts 269 318
Top of the range 0.75 about 188 watts 309 366

The race pacing planner does this check for you and lowers the target when a long bike would push the TSS out of the good range.

Ride steady: hills, wind and surges

The second half of the pacing rule is how you spread the effort. The TrainingPeaks coach Q&A recommends keeping the variability index, normalized power divided by average power, close to 1. In plain words: no big surges Coaching practice.

In practice that means:

  • Climbs: let the power rise a little, but not to threshold. A short hill at 100% of FTP costs more than the few seconds it saves.
  • Descents and tailwinds: keep pedalling lightly instead of coasting, but do not chase speed you cannot hold.
  • Headwinds: they feel slow, so people push. Hold your watts and accept the speed.
  • Other riders: ignore them. Passing someone and being passed back ten minutes later is the most expensive game in long-course racing.

This is one of the few pacing rules with some research behind it. In a study of ten triathletes, a 5 km run after a 20 km ride at constant power was about 50 seconds faster than after a ride at the same average power with surges (Bernard et al. 2007). In a lab study of nine triathletes, an hour of riding with surges left blood lactate much higher at the start of the run and lowered running speed at the lactate threshold, compared with an even ride at the same average power (Etxebarria et al. 2014). The studies are small and the rides far shorter than a 70.3 or Ironman bike, so treat them as support for the coaching rule rather than proof Limited evidence.

No power meter? Heart rate and feel

Power is the easiest number to pace by, because it responds instantly and is not affected by wind or gradient. Without it you have two alternatives.

Heart rate. It works, but it lags. On a climb your heart rate may take a minute or two to catch up with the effort, so by the time it says “too hard” you have already been too hard for a while. It also drifts upwards over a long ride, especially in the heat, even at the same power. Use a cap rather than a target: decide a heart-rate ceiling from your training rides at race effort and stay under it Coaching practice. Your training zones are the place to start.

Feel. For a 70.3 the bike should feel “comfortably hard” for the first hour, and you should be able to speak in short sentences. For an Ironman it should feel almost too easy for the first two hours. If you are breathing hard on the first hill, you are riding someone else’s race Coaching practice.

Speed is the least useful of the three. It depends on the course, the wind and your position more than on your effort, so use it only to check your finish-time prediction, not to pace.

Running off the bike: start easy, then settle

If the bike went to plan, the run is where you use it. The most common mistake is the first few kilometres. Your legs feel strange off the bike, the crowd is loud, and your watch says you are running slowly, so you speed up. Twenty minutes later you understand why everyone told you not to.

A simple plan:

  1. First 2–3 km: run deliberately slower than your goal pace. It will feel too easy. That is the point.
  2. Settle: after that, run at a pace you could hold for the whole distance, checking effort and heart rate more than pace.
  3. Second half: if you still feel good at halfway in a 70.3, or at 30 km in an Ironman, you can push.

Your stand-alone race pace is a ceiling for the run, not the plan. How much slower you run off the bike depends on the bike, the heat and your training, and we do not give a fixed percentage because there is no good evidence for one. The finish-time predictor lets you enter your own slow-down and see what it means for your finishing time.

Aid stations are the other pacing tool. Many age-groupers walk briefly through each station to drink and eat properly, then run again Coaching practice. If you plan to, make it part of the plan from the start, not something you start doing when you are already in trouble. For fluids, drink to thirst rather than to a schedule.

Heat, hills and race-day changes

The ranges above assume a normal day. The TrainingPeaks coach Q&A says hot and hilly courses, and weaker runners, call for the lower end. The reasons are simple:

  • Heat: your body has to send blood to the skin to cool, so the same power costs more. Heart rate rises faster, and the run suffers more from a hard bike.
  • Hills: they tempt you into surges, and long descents leave you cold and stiff before the next climb.
  • Wind and rain: they slow you down, which makes the bike longer and, for an Ironman, raises the TSS at the same IF.

On race morning, check the forecast and decide your number before you start. “I will see how I feel” usually means “I will ride too hard while I feel good”.

Safety note: this guide is general information for healthy adults, not medical advice. In the heat, slow down early. Dizziness, confusion, nausea or chills can be signs of heat illness: stop, get into the shade and ask race medical staff for help.

Practise your race pace

A race-day target only works if you have ridden it in training. Two or three long rides at your target power, on your race bike, with your race fuel and in your race position, will tell you more than any formula Coaching practice. Run 20–30 minutes off at least some of them.

Check two things on those rides. First, can you eat and drink at that power? Second, how does your run feel afterwards? If the answer to either is “badly”, lower the target now rather than on race day. When the plan is settled, print it on a race-day card so you are not doing maths in transition.

Re-test your FTP in the last six to eight weeks before the race. An FTP from last spring makes every number in this guide wrong, usually too high Coaching practice.

What the pros ride

Professional numbers mostly show how different their race is. TrainingPeaks’ Kona analysis puts professionals at about 0.78–0.82 IF, and Lionel Sanders’ power file from Kona 2016 shows about 0.77. That is above any age-group range, but a pro bike often takes around four hours, so the total load ends up similar: two Kona power files Joe Friel analysed came out at a TSS of 285 and 286, the top of the good range. A higher percentage over four hours can cost less than a lower one over six and a half. If you want to copy the pros, copy the TSS, not the percentage.

FAQ

Should I pace a 70.3 by power or heart rate?

Power, if you have it. It responds instantly and is not affected by wind or heat drift. Use heart rate as a ceiling alongside it, especially in hot races. Without a power meter, heart rate plus feel is the next best option.

What percentage of FTP for my first Ironman?

About 65% of FTP, which is an intensity factor of 0.65. That is the figure TrainingPeaks’ Kona analysis gives for first-timers and the low end of the usual age-group range. If your bike will take more than six hours, check that your Training Stress Score stays under about 285.

How much slower will I run off the bike?

It varies too much to give one number. It depends on how hard you rode, the heat and how much you have trained running off the bike. Use your stand-alone race pace as a ceiling, not a target, and plan the first few kilometres slower still.

What TSS should my Ironman bike be?

For most well-prepared age-groupers, about 250–285, based on coach Rick Ashburn’s chart. Below 250 is conservative and fine for a first Ironman. Above about 310 the run is likely to suffer badly.

Can I pace by speed instead?

Not reliably. Speed depends on wind, gradient, road surface and your position more than on your effort. Use it to estimate your finishing time, and pace by power, heart rate or feel.

What if my FTP is out of date?

Re-test before you set race targets, ideally six to eight weeks out. If you cannot, use a conservative estimate and ride at the low end of the range. An FTP that is too high makes every target too high.

Sources

  1. TrainingPeaks coach Q&A, How to pace your half Ironman bike (2014, updated 2022)
  2. TrainingPeaks, Lessons from Kona: how to nail an Ironman bike
  3. Friel, How to cheat by using a power meter in an Ironman (TrainingPeaks)
  4. Schell 2026, IRONMAN bike pacing: intensity factor and TSS (Best Bike Split)
  5. TrainingPeaks, Power analysis of the 2016 Ironman World Championship (Sanders)
  6. Bernard et al. 2007, Constant versus variable-intensity during cycling: effects on subsequent running performance
  7. Etxebarria et al. 2014, Isolated running does not replicate running capacity after triathlon-specific cycling