Calculator Input
Enter realistic segment data, transition times, and race-day penalties. The calculator estimates a full-distance finish using your pacing profile.
Example Data Table
These sample profiles show how segment pace, transitions, and penalties can shift an overall projected finish.
| Scenario | Swim Pace | Bike Speed | Run Pace | Transitions + Stops | Projected Finish |
|---|---|---|---|---|---|
| Balanced Age-Group Plan | 02:00 /100m | 30.0 km/h | 06:00 /km | 00:24:00 | 12:21:15 |
| Strong Competitive Plan | 01:50 /100m | 33.0 km/h | 05:20 /km | 00:20:00 | 11:00:56 |
| Conservative Finish Plan | 02:20 /100m | 27.0 km/h | 06:45 /km | 00:33:00 | 14:18:59 |
| Steady Negative-Split Plan | 02:05 /100m | 31.0 km/h | 05:45 /km | 00:22:00 | 11:56:52 |
Formula Used
This calculator combines base segment times with planning multipliers for race conditions and late-race slowdown. It is intended for pacing strategy, not official race scoring.
The weighting gives the run the largest fatigue effect, because most athletes slow more on the marathon than on the swim or bike. Weather affects all segments, but it hits open-water swimming and cycling differently from steady indoor-style pace estimates.
How to Use This Calculator
Start with your realistic race-day swim pace per 100 meters, average bike speed, and run pace per kilometer. Then enter transitions, likely stop time, and a modest safety buffer.
Use the fatigue factor when your training suggests noticeable slowdown late in the race. Use the weather penalty for hot, windy, rough, or wet conditions.
After calculation, review the predicted finish time, cumulative split table, and pacing chart. Adjust one variable at a time to see which segment offers the safest improvement.
FAQs
1. What does this calculator estimate?
It estimates a projected full-distance finish time using swim pace, bike speed, run pace, transitions, extra stops, and optional planning penalties for fatigue and weather.
2. Does it include transitions?
Yes. T1, T2, and extra stop time are included separately, so you can see how non-moving minutes affect the final projected finish.
3. Why are fatigue and weather separate inputs?
They affect pacing differently. Fatigue usually grows later in the race, especially on the run. Weather can affect all segments through heat, wind, chop, or rain.
4. Can I use custom distances?
Yes. You can overwrite the default swim, bike, and run distances for custom long-course events, course changes, or race simulation planning.
5. Why is my predicted finish slower than simple math?
Simple math ignores transition losses, aid-station pauses, terrain disruption, and late-race fade. This calculator adds those planning elements for a more realistic projection.
6. What swim pace should I enter?
Use your sustainable open-water race pace per 100 meters, not your best short pool interval. Open-water pacing is often slower than controlled training sets.
7. How should I set the safety buffer?
Add a small margin for pacing drift, congestion, or fueling delays. Many athletes use a modest buffer instead of assuming a perfect, uninterrupted race day.
8. Are the checkpoints official?
No. They are common planning checkpoints for a full-distance event. Always confirm the official rules and cutoffs for your specific race organizer and venue.