About the Triathlon Time Predictor
Triathletes use this calculator to combine target paces across all three disciplines, plus transition time, into a single predicted finish time, useful for setting a realistic race-day goal or checking whether a training pace plan actually adds up to a target time before race day arrives.
How It Works
Enter distance and target pace separately for the swim, bike, and run legs, along with a combined transition time covering both T1 and T2. The calculator converts each leg into minutes using the pace convention that fits it best, swim pace per 100 meters, bike distance divided by speed, and run pace per mile, then adds all four pieces together for a total predicted time. It also displays each segment individually in a breakdown table alongside the total.
Formula & Methodology
For a standard sprint-distance setup, a 1500m swim at 2.2 min per 100m, a 25 mile bike at 18 mph, a 6.2 mile run at 9 min per mile, and 4 minutes of transitions: swim time = 15 x 2.2 = 33 minutes, bike time = (25/18) x 60 = 83.3 minutes, run time = 6.2 x 9 = 55.8 minutes, and total time = 33 + 83.3 + 55.8 + 4 = 176.1 minutes, or about 2 hours 56 minutes.
Examples
Sprint-distance pacing check
A 1500m swim at 2.2 min per 100m, a 25 mile bike at 18 mph, a 6.2 mile run at 9 min per mile, and 4 minutes of transitions predicts a total finish time of about 2 hours 56 minutes.
Faster bike leg swap
Keeping the same swim and run paces but raising bike speed to 22 mph drops bike time to (25/22) x 60 = 68.2 minutes, cutting roughly 15 minutes off the same predicted total.
Advantages
- Combines three very differently paced disciplines into a single comparable total time.
- Breaks the prediction into a segment-by-segment table, showing exactly where projected race time is spent.
- Makes it easy to test pace changes on one leg without recalculating the entire race total by hand.
Common Mistakes
- Entering bike speed in the wrong unit, such as km/h, when the bike distance field expects miles.
- Underestimating or leaving out transition time, which can meaningfully understate total predicted time, especially at longer race distances.
- Assuming race-day pace will exactly match training pace, when fatigue, terrain, and race-day conditions typically slow later legs of the race.
Edge Cases to Watch For
- Bike speed must be greater than zero, since it's used as a divisor in the bike time calculation; a zero or negative entry returns an error instead of an undefined result.
- The calculator assumes a constant pace across each entire leg, so it won't reflect a faster opening swim, a fading run pace late in a long race, or hills that slow the bike split.
- Transition time is entered as a single combined T1 plus T2 figure rather than modeled as two separate transitions, so it can't isolate which transition is slower.
- Swim pace uses a per-100-meter convention while bike and run use per-mile or mph conventions, so mixed unit entry errors are easy to make if the fields aren't read carefully.
Common Use Cases
- Triathletes building a target pace plan ahead of an upcoming race.
- Coaches checking whether a proposed set of splits produces a realistic overall finish time.
- Athletes comparing how a pace improvement on one leg changes their projected overall finish time.