Triathlon
Triathlon race plan
Adds three discipline times and both transitions into a projected finish, and shows what share of the race the transitions are.
The question this answers: “What will I actually finish in, and how much of that is transitions?”
Result
- Projected finish
- 1:33:51
- Swim
- 17:30
- 750m.
- Bike
- 42:51
- 20km.
- Run
- 27:30
- 5km.
- Transitions
- 6:00
- 6.4% of your race.
Worth knowing about this answer
- Three paces added together, plus the transitions. There is no fatigue model here: it assumes you hold each pace, which is exactly what going out too hard on the bike prevents.
- No drafting, wetsuit or course-profile adjustment. Those depend on your event and your athlete, and inventing coefficients for them would be false precision.
Show the working
- Swim
750 ÷ 100 × 140s17:30 - Bike
20 ÷ 28 × 360042:51 - Run
5 × 330s27:30 - Transitions
210 + 1506:00
Projected finish: 1:33:51. Swim: 17:30. Bike: 42:51. Run: 27:30. Transitions: 6:00
Each leg is distance divided by pace or speed, converted to time. The two transitions are added, and the transition share is expressed as a percentage of the total.
- You hold each stated pace for the whole leg, which is exactly what going out too hard on the bike prevents.
- The transitions are timed and count towards the result, which is why they are inputs rather than an afterthought.
- No fatigue model. The run pace you can hold fresh is not the run pace you hold off the bike, and only brick sessions tell you the difference.
- No drafting, wetsuit or course-profile adjustment. Those depend on your event and your athlete, and coefficients for them would be false precision.
- It does not know your event’s rules. Drafting legality and wetsuit thresholds come from the entry pack.
Runs entirely in your browser — nothing you type is sent anywhere. Last reviewed 2026-08-15. More on Triathlon.