Use case · Sub-2:30 · sub-5 · sub-10
Chasing a goal time
You've got a number in your head. We turn it into a number per leg and show you how far off each one is.
| Leg | Goal split | Projected today | Gap |
|---|---|---|---|
| Swim | 0:27:301:50 /100m | 0:28:101:53 /100m | +0:40 to find |
| Bike | 1:11:3033.6 km/h | 1:13:0032.9 km/h | +1:30 to find |
| Run | 0:48:104:49 /km | 0:47:304:45 /km | 0:40 ahead |
Goal 2:30:00 vs 2:31:30 projected from your recent efforts (1:30 to find). Transitions estimated.
The situation
You've got a time you want. Maybe it's a round number, maybe it's the one that got away last season. You know roughly what you can do in each leg, but not whether the sum adds up. Not knowing is the annoying part.
The problem
- A goal time is one number; a race is five.
- You can't tell which leg is furthest from where it needs to be.
- Progress shows up in sessions, not in projected race time.
The race
What the day adds up to
The goal, split by leg. Every number on this page comes back to these five.
Walk-through
On sample data
A short run through how it plays out. The numbers are illustrative.
- GoalOlympic (Standard), sub-2:30:00.
- SplitSwim 0:27:30, T1 0:01:50, bike 1:11:30, T2 0:01:00, run 0:48:10.
- GapProjected 2:32:25. Bike is +1:30, run is already ahead.
- DecisionTwo bike sessions a week move to threshold work. The run stays as it is.
Is the time realistic?
An honest verdict on the time you want.
Where you would finish today, what the weeks you have left can win back, and the stretch target if it all goes right.
How realistic is this goal? · sample data
A rule of thumb on the gap and your fitness trend: the time left usually wins back 0.5% plus 0.7% a month, more if your fitness is climbing.
Other use cases
Obsessed with progress?
Progress, proven.
R99 a month. Connect Strava tonight. Your whole history is there before your next session.