Skip to main content

Free triathlon planning tool

Triathlon Race Predictor

Predict a triathlon finish time from results you already have. Enter a recent 5k, 10k, half marathon or marathon, your FTP and body mass, and a pool swim time, and the predictor scales each one to your race distance - including the run penalty for racing off the bike.

Predict from your current fitness

The Fitness-Aware Pacing panel below is the predictor. Enter a running race you have actually completed, your FTP and mass, and a recent pool time; the estimate updates as you type. If you would rather work backwards from a goal finish time, the same tool does that too - set the target and read off the required splits.

Reverse goal-time calculator

Race Predictor

Open the Fitness-Aware Pacing panel to predict from a recent running race, FTP, and pool time - or set a target finish time to see the splits it requires.

Goal clock
06:00:00
Race distance
Carb target
75 g/hr
3065100

Input your training metrics to estimate realistic splits based on your current fitness.

Swim Fitness

Recent Pool Time
ms

Bike Fitness

Run Fitness

Race Time
hms
Fitness Predictions
Swim Split:38:00 (2:00/100m)
Bike Split:2:48:45 (32 km/h)
Run Split (off-bike):2:01:41 (5:46/km)
Total Time (w/ trans):05:34:26
Swim
Aggressive
39:39
2:05 / 100 m
11.0% of total
Bike
Solid
3:05:51
29.1 km/h (18.1 mph)
51.6% of total
Run
Solid
2:08:30
6:05 / km
35.7% of total

Checkpoint Clock

Swim exit00:39:39
T1 exit00:43:09
Bike finish03:49:00
T2 exit03:51:30
Finish06:00:00

Fuel & Hydration Estimate

Total carbs350 g
Bike carbs230 g
Run carbs120 g
Bike bottles4 (every 46 min)
Bike gels0 gels
Run gels5 gels (every 26 min)
Run aid stations10
Total sodium3144 mg
Total fluids3667 ml

Based on your body weight of 70kg, your carb target of 75g/hr corresponds to 1.07g/kg/hr.

Bike/Run Tradeoff

More conservative bike
Bike
3:10:51
28.3 km/h (17.6 mph)
Run
2:03:30
5:51 / km
More aggressive bike
Bike
3:00:51
29.9 km/h (18.6 mph)
Run
2:13:30
6:20 / km

Plan Checks

  • This split shape looks internally consistent. The next check is whether your recent training supports each required pace.

Add your wave or rolling-start time and the exported PDF shows checkpoints as times of day rather than elapsed time.

What the predictor assumes for each distance

These are the actual constants in the model, not a general description of it. Bike intensity is expressed as a fraction of FTP; the run penalty is added to your projected standalone pace; the swim adjustment converts pool pace to open water and is editable.

What the predictor assumes for each distance
Race distanceBike intensity (of FTP)Run-off-bike penaltySwim: pool → open water
Sprint (750 m / 20 km / 5 km)0.8818 s/km+10 s/100 m
Olympic (1.5 km / 40 km / 10 km)0.8424 s/km+10 s/100 m
70.3 (1.9 km / 90 km / 21.1 km)0.7845 s/km+10 s/100 m
Ironman (3.8 km / 180 km / 42.2 km)0.7075 s/km+10 s/100 m

Source: the site's own pacing model. The bike split is solved from a power balance rather than a speed lookup, so mass and course profile change the result independently of watts.

Community rules of thumb, and what this model gives instead

Triathletes answer the 'how much slower off the bike' question with rules of thumb long before any calculator is involved. On short course this model matches them. On long course it is deliberately harsher, because the rules of thumb describe races that went well and the failure mode people actually post about is the Ironman marathon that fell apart.

Community rules of thumb, and what this model gives instead
ConversionCommon rule of thumbWhat this model producesVerdict
Open half marathon → 70.3 run+5 to 12 minutes+16 min (45 s/km × 21.1 km)More conservative
Open marathon → Ironman run+20 to 40 minutes+53 min (75 s/km × 42.2 km)More conservative
Open 10k → Olympic-distance run+2 to 5 minutes+4 min (24 s/km × 10 km)Agrees
Open 5k → sprint run+1 to 3 minutes+1.5 min (18 s/km × 5 km)Agrees

Rules of thumb are the recurring answers on triathlon forums; the model column is computed directly from the constants in the table above. If your own brick sessions consistently beat these numbers, trust your data over the default.

How the run projection actually works

Your standalone race result is first scaled to the triathlon run distance with Riegel's endurance formula, T₂ = T₁ × (D₂ / D₁)^1.06, which is equivalent to multiplying pace by (D₂ / D₁)^0.06. That exponent is why a 10k runner does not simply hold 10k pace for a half marathon.

The distance-specific penalty from the table above is then added to that projected pace. It represents the cost of arriving at the run already several hours into a race rather than fresh at a start line - the accumulated bike load, the fuelling deficit, and the heat exposure that a standalone race does not carry.

Two things this deliberately does not model: the wind and elevation of a specific bike course, and your own fuelling execution. Both can move an Ironman marathon by more than the penalty itself, which is why the output is a planning range rather than a prediction you should pace off directly.

Sanity-check the prediction before you trust it

  • Use a running race you have raced, not a training run. A parkrun effort and a 5k time trial in a session produce different predictions.
  • Use a real FTP number. An inflated FTP - from an auto-estimated figure or a short test - propagates into an optimistic bike split and then hides the run cost of riding at that intensity.
  • Raise the open-water adjustment above 10 s/100 m if this is an early open-water race, a non-wetsuit swim, or a crowded rolling start.
  • Check the result against the cutoff calculator if you are close to the limits, since the bike gate is the one that ends most days.

Frequently asked questions

How do I predict my triathlon time from a 5k or 10k?
Enter the running race you have actually done and the calculator scales it to the triathlon run distance using Riegel's endurance formula, then adds a run-off-the-bike penalty for the distance you are racing. A 48-minute 10k runner (4:48/km) racing a 70.3 is projected at 5:01/km for a standalone half marathon and 5:46/km after 90 km of riding - a 2:02 run split.
Is a race predictor different from a finish time calculator?
Yes, and the difference is what you type in. This predictor starts from results you already have - a running race, an FTP test, a pool time - and works out what they imply. The finish time calculator starts from the swim, bike and run paces you intend to hold on race day. Use the predictor when you do not yet know what paces are realistic.
How much slower will I run off the bike?
This model adds 18 seconds per kilometre for a sprint, 24 for an Olympic, 45 for a 70.3 and 75 for an Ironman marathon, applied to your projected standalone pace. Over the full distance that is +1.5, +4, +16 and +53 minutes respectively. The long-course figures are deliberately more conservative than the rules of thumb triathletes trade on forums, which put a 70.3 run 5 to 12 minutes down on an open half and an Ironman marathon 20 to 40 minutes down on an open marathon. If you fuel well and ride within yourself you should beat this model; it is built to be the number that still holds on a bad day.
What FTP percentage does the prediction assume?
Intensity factor defaults to 0.88 for a sprint, 0.84 for an Olympic, 0.78 for a 70.3 and 0.70 for an Ironman. Those are conventional age-group race intensities. Riding harder than the assumed intensity does not simply produce a faster prediction - it also means the run penalty you should expect is larger than the default.
Why is my predicted swim slower than my pool time?
Ten seconds per 100 m is added by default to convert pool pace to open water, and you can raise it. Open water removes the walls you push off, the black line you follow and the lane that keeps you straight. Swimmers racing open water for the first time often need 15 to 20 seconds per 100 m rather than 10.
How accurate is a triathlon race predictor?
Treat it as a range, not a time. It cannot know the wind on the bike course, how well you fuel, whether the swim is wetsuit legal, or how much elevation the run has. It is at its most useful for deciding whether a goal is plausible and for seeing which discipline is actually limiting you.
Can I predict an Ironman time from a 70.3 result?
The common rule of thumb is to double the 70.3 and add 30 minutes to an hour, which puts a 6:00 half at roughly 12:30 to 13:00. That rule assumes the full-distance fuelling and long-ride volume are actually there. Entering the underlying fitness numbers here is more informative, because it shows which leg the extra time comes from.
Which discipline should I train to gain the most time?
Change one input at a time and watch the total. For most age-group athletes the bike leg holds the largest absolute gains simply because it is the longest, and the swim the smallest - gaining 5 seconds per 100 m saves under two minutes in a 70.3, while 10 watts of FTP can save several.

Related calculators

Trust and methodology

How this page should be used

Model last reviewed

August 8, 2026

Maintained by

M Imtinan Farooq

Age-group triathlete and data engineer

Status

Planning estimate, not a race guarantee

Formula summary

Projected splits are scaled from recent race or time-trial results you enter.

Key assumptions

The reference result is recent, complete, and raced rather than trained.

Limitations

Predictions built from fresh single-sport bests run optimistic; race data predicts far better.

Sources

Full formulas, constants, and limitation notes are published on the methodology page. Use the official athlete guide for your own race when it comes to rules, cut-off times, venue policies, and safety instructions - those override anything here.