Cycling Race Finish Time Estimator
Created by: Emma Collins
Last updated:
Predict race or sportive finish time from course distance, elevation gain, FTP, drag, and terrain type, then inspect the segment-by-segment pacing breakdown instead of relying on one average speed guess.
Cycling Race Finish Time Estimator
CyclingEstimate race or sportive finish time from distance, elevation, FTP, drag, and terrain type with a segment-by-segment pacing breakdown.
What is a Cycling Race Finish Time Estimator?
A cycling race finish time estimator predicts how long a race, sportive, or fondo may take from course distance, total elevation gain, FTP, and aerodynamic drag. For cyclists, that matters because a single average-speed guess usually ignores how differently flat and hilly terrain convert power into time.
This estimator keeps the route structure visible by modeling flat, rolling, and climbing segments separately. That makes it more useful than a one-number speed target because riders can see where the event is likely to be decided.
How the Course Model Works
The calculator splits the total course into flat, rolling, and climbing segments based on the selected course type. It then applies terrain-specific power targets derived from FTP and solves the likely speed for each segment using a steady-state cycling physics model.
The total race time is simply the sum of those segment times. That gives riders both a finish-time estimate and a pacing breakdown they can inspect.
Core logic
Course type defines the flat, rolling, and climbing split
FTP anchors target power for each segment type
Segment speed is solved from drag, rolling resistance, gravity, and target power
Practical Applications
- Estimate event finish time from route profile instead of using one flat-road average speed.
- Compare flat, mixed, and hilly course outcomes for the same rider.
- See whether aerodynamics or climbing sections are driving the event result.
- Build more realistic pacing expectations before race day.
FAQ
What does a cycling race finish time estimator predict?
It predicts an approximate finish time for a race, sportive, or fondo from course distance, elevation gain, rider FTP, and aerodynamic drag. That matters because race time depends on more than one flat average speed guess. Terrain type changes how power converts into forward speed.
Why are flat, mixed, and hilly courses modeled separately?
Because the same rider and FTP can produce very different finish times on different terrain splits. Flat courses reward aerodynamics and steady pacing more, while hilly courses shift more of the result toward climbing power and total mass.
Does this assume perfect drafting or solo riding?
It sits somewhere between the two by using steady-state power targets without trying to model a full peloton. That makes it useful for planning, but it is still an estimate rather than a race-day guarantee.
Why include CdA in a race estimator?
CdA matters because aerodynamic drag dominates on flatter and faster sections. Two riders with the same FTP can still finish at different times if one presents much less drag to the wind.
Should I treat the finish time as a pacing target?
Treat it as a planning benchmark, not a promise. It is most useful when compared across realistic scenarios rather than treated as a single guaranteed outcome.
What is the value of the segment table?
It shows where the modeled time is actually going. That helps riders see whether the course is mostly flat-speed limited or whether climbing sections are driving the result.