Cycling Time Calculator

Plan century rides and gran fondos with physics-backed time estimates based on power, setup, elevation, and wind angle assumptions.

Ride Inputs

Build a realistic pacing model with route, wind, and setup assumptions before race day.

Mode

Current mode: Speed target

Route and Wind Conditions

0 = headwind, 90 = crosswind, 180 = tailwind

Run the model

Enter ride assumptions, then calculate to see elapsed time, required power, and benchmark tables.

Results include moving and elapsed time to support event planning.

Cycling Time Calculator Method Guide

How this model estimates ride time, why assumptions matter, and how to use results for practical pacing decisions.

1) What this calculator predicts and what it does not

This tool predicts moving time, elapsed time, required power, and energy cost for a route segment based on user inputs and explicit assumptions. It is a training and planning model, not a medical tool and not a substitute for direct field measurements from a calibrated power meter.

The model is strongest when your assumptions are realistic. If wind angle, bike setup, or elevation are wrong, the output can drift. That is normal for prediction models and does not mean the math is broken.

Use this estimator to compare scenarios before rides: for example, how much time changes if you hold the same power but improve aerodynamics, or how much extra time to budget when route profile and headwind worsen.

  • Best use case: pacing plans for events, centuries, gran fondos, and long endurance rides.
  • Not for clinical diagnosis, rehabilitation decisions, or medical risk assessment.
  • Treat outputs as directional guidance, then validate against actual ride files.

Interpretation rule

Do not change your full training plan from one estimate. Compare multiple rides and consistent assumptions first.

2) Inputs and assumptions that control the model

Distance and elevation define route demand. Bike setup presets set baseline aerodynamic drag (CdA) and rolling resistance (Crr). Wind speed and wind angle are converted into an effective headwind component, because headwind impact differs from crosswind and tailwind.

Rider mass and bike mass matter most when climbing or accelerating back to pace. On flatter routes at higher speed, aerodynamics usually dominates. That is why position and bike setup are high-impact controls.

Stop-factor converts moving time to elapsed time. Use 0% for uninterrupted efforts; use a higher value for urban routes, aid stations, and expected stop-start traffic.

  • Use realistic bike setup presets first, then override only if you have measured data.
  • Wind angle should reflect dominant route direction, not one short section.
  • Use stop-factor for logistics planning, not for fitness scoring.

Primary Sources for This Section

Related Resources

3) Formula A: time-speed-distance foundation

At the base level, moving time follows the distance-speed relationship. This gives the first estimate before terrain, wind, and equipment assumptions are layered in.

Elapsed time then adds the stop-factor multiplier. This split is useful because athletes often train by moving time, while event logistics require elapsed time.

Time foundation

tmoving=dvt_{\text{moving}} = \frac{d}{v}
telapsed=tmoving×(1+s100)t_{\text{elapsed}} = t_{\text{moving}} \times \left(1 + \frac{s}{100}\right)

Where:

  • tmovingt_{\text{moving}}moving time (hours)
  • telapsedt_{\text{elapsed}}elapsed time including stops (hours)
  • dddistance (km)
  • vvaverage moving speed (km/h)
  • ssstop-factor percentage (%)

Moving time assumes continuous progress. Elapsed time includes operational stops, aid stations, and route interruptions.

Example: 100 km at 30 km/h gives 3.33 h moving time (3:20:00). With 8% stop-factor, elapsed time becomes 3.60 h (3:36:00).

Planning tip

If your event has mandatory stops, plan from elapsed time. If your workout block targets load, review moving time.

4) Formula B: physics-based power requirement

The model estimates required power by combining aerodynamic drag, rolling resistance, and climbing power, then adjusting for drivetrain efficiency. This structure is consistent with validated road-cycling power modeling.

Aerodynamic demand increases sharply with speed, so a small target-speed increase can require a large power increase. This is why pacing errors early in long rides often have a bigger physiological cost than expected.

Steady-state cycling power

Paero=12ρCdA vrel2 vP_{\text{aero}} = \frac{1}{2}\rho C_dA\,v_{\text{rel}}^{2}\,v
Proll=Crr m g cos⁡(θ) vP_{\text{roll}} = C_{rr}\,m\,g\,\cos(\theta)\,v
Pclimb=m g sin⁡(θ) vP_{\text{climb}} = m\,g\,\sin(\theta)\,v
Ptotal=Paero+Proll+PclimbηP_{\text{total}} = \frac{P_{\text{aero}} + P_{\text{roll}} + P_{\text{climb}}}{\eta}

Where:

  • ρ\rhoair density (kg/m³)
  • CdAC_dAdrag coefficient × frontal area (m²)
  • vrelv_{\text{rel}}relative air speed (m/s)
  • vvrider ground speed (m/s)
  • CrrC_{rr}rolling resistance coefficient
  • mmtotal system mass: rider + bike (kg)
  • gggravity constant (~9.81 m/s²)
  • θ\thetaroad angle (radians)
  • η\etadrivetrain efficiency (0 to 1)

Relative air-speed relation

vrel=v+vheadwindv_{\text{rel}} = v + v_{\text{headwind}}
  • vheadwindv_{\text{headwind}}effective headwind component (m/s)

CdA is drag area, Crr is rolling resistance coefficient, g is gravity, and system mass means rider + bike.

Example: 40 km TT conditions with realistic road setup assumptions typically require substantially more power than the same distance at endurance pace because aerodynamic cost rises non-linearly with speed.

Primary Sources for This Section

5) Formula C: wind-angle handling

Wind direction is reduced to an effective headwind component using cosine projection. This prevents over-penalizing pure crosswinds and aligns the model with directional wind physics.

A 20 km/h headwind at 0° has a large penalty, while a 20 km/h crosswind at 90° contributes little direct headwind component in this model.

Effective headwind component

vheadwind=vwindcos⁡(ϕ)v_{\text{headwind}} = v_{\text{wind}}\cos(\phi)

Where:

  • vheadwindv_{\text{headwind}}effective headwind used in model (km/h)
  • vwindv_{\text{wind}}ambient wind speed (km/h)
  • ϕ\phiwind angle: 0° headwind, 90° crosswind, 180° tailwind

This keeps wind handling realistic: direct headwind penalizes most, crosswind contributes less direct speed penalty.

Example: 18 km/h wind at 60° gives effective headwind of 9 km/h (18 * cos 60°). The same wind at 90° contributes near 0 km/h headwind.

Why this matters

Directional handling keeps the model from treating every windy day as a full headwind scenario.

6) Formula D: calories from mechanical work and efficiency

This tool estimates energy cost from power and duration rather than relying only on static MET bands. Mechanical work is computed from watts and moving time, then converted to metabolic cost using gross efficiency assumptions.

Gross efficiency is athlete-dependent and changes with intensity, fatigue, and measurement method. For that reason, calorie output should be interpreted as a planning estimate, not an exact nutrition prescription.

Energy estimate

WkJ=P⋅t1000W_{\text{kJ}} = \frac{P\cdot t}{1000}
Ekcal=WkJηgross⋅4.184E_{\text{kcal}} = \frac{W_{\text{kJ}}}{\eta_{\text{gross}}\cdot4.184}

Where:

  • WkJW_{\text{kJ}}mechanical work output (kJ)
  • PPpower output (W)
  • ttmoving time (seconds)
  • EkcalE_{\text{kcal}}estimated metabolic energy (kcal)
  • ηgross\eta_{\text{gross}}gross efficiency (default: 0.24)

Gross efficiency defaults to 0.24 in this tool. Use calories as a planning estimate, not an exact value.

Example: 220 W for 3 hours yields about 2,376 kJ mechanical work. At 24% gross efficiency, estimated metabolic cost is roughly 2,365 kcal.

Primary Sources for This Section

Related Resources

7) Worked examples for common event types

Example A (40 km TT): If a rider targets a high speed with low stop-factor, the model will show high required power and relatively tight elapsed vs moving time spread. This is useful for pacing around threshold and setup optimization.

Example B (100 km gran fondo): With higher elevation gain, variable wind angle, and non-zero stop-factor, elapsed time expands and power demand profile changes. This is useful for fueling and cutoff planning.

Example C (100 miles century): The same athlete can test conservative, current, and aggressive scenario cards to see time-risk tradeoffs before event day.

  • For time-trial planning, prioritize aerodynamic setup and pacing discipline.
  • For gran fondos, prioritize sustainable power and fueling consistency.
  • For centuries, include a realistic stop-factor in elapsed-time planning.

Primary Sources for This Section

8) How to use outputs in weekly training

Use required power and elapsed-time targets to design race-specific sessions. For example, long steady-state intervals can rehearse power durability, while event-specific rides can rehearse aid-station and stop-factor assumptions.

If your predicted and actual times diverge consistently, update assumptions first. Common adjustments are bike setup, elevation profile realism, and wind-angle realism.

For threshold progression, pair this tool with FTP and zone calculators so your pacing target is tied to a clear physiological anchor.

  • Retest with comparable route assumptions every 2 to 4 weeks in build periods.
  • Track moving time and elapsed time separately.
  • Document wind direction and route profile in your training log.

Coach workflow

Estimate time here, anchor intensity with FTP, then convert to structured zones for session design.

Related Resources

9) Common mistakes that reduce prediction quality

Most errors come from assumption mismatch, not arithmetic. Typical mistakes include unrealistic bike setup selection, ignoring stop-factor on urban routes, and applying one wind value to a route with very different directional segments.

Another common issue is mixing units across tools. Keep distance, speed, and weight units consistent before comparing sessions.

  • Use a bike preset that matches your actual posture and tire setup.
  • Do not treat crosswind as headwind unless route geometry supports that assumption.
  • Avoid comparing rides with different route profiles as if they were equivalent.

10) Quality checklist before acting on a prediction

Before using a prediction for race execution, run this checklist: confirm route distance and elevation source, confirm wind assumptions, confirm bike setup preset, and confirm stop-factor based on event logistics.

If your goal is performance progression, compare at least three comparable sessions before changing training load targets. This helps separate real adaptation from route-day noise.

  • Input validation: units and route data are correct.
  • Assumption validation: bike setup, wind angle, and stop-factor are realistic.
  • Decision validation: use trends across multiple sessions before making major changes.

Primary Sources for This Section

Related Resources

Interpretation

  • Use moving time for training load planning and elapsed time for race-day logistics.
  • Prediction quality depends on realistic assumptions for bike setup, wind angle, and elevation gain.
  • Compare model outputs against comparable past rides before making large pacing changes.

What to Do Next

  • Run scenario pacing cards and pick a conservative race-day baseline before your event.
  • Anchor intensity with FTP and zone tools so your pacing target aligns with training metrics.
  • Recheck stop-factor and wind assumptions one day before the event and update your pacing plan.

Methodology

Version v3.0
Updated 2026-03-05
Owner Cycling Regimen Editorial

  • Physics-Based Time Model

    Uses drag, rolling resistance, climbing demand, and drivetrain efficiency to connect power, speed, and time.

  • Wind Angle and Elevation Handling

    Converts wind angle to effective headwind and route profile to average gradient assumptions.

  • Version and Assumptions

    Calculation assumptions and updates are documented in the methodology center.

    Read source
About Our Calculation Approach

Frequently Asked Questions

Why is my real ride slower than the predicted moving time?

Moving time excludes stops by design. Use stop-factor for elapsed-time planning and verify wind angle, elevation gain, and bike setup assumptions before race day.

Should I use speed mode or power mode?

Use speed mode when you have a target pace objective. Use power mode when you have a reliable wattage target from training and want the model to estimate resulting speed and time.

Can this tool help with century or gran fondo pacing?

Yes. It is designed for that use case. Set realistic stop-factor, route elevation, and wind assumptions, then validate your plan against prior comparable rides.

Disclaimer: This calculator provides estimates based on published exercise science models. Results are not medical advice. Individual physiology, health status, and environmental conditions affect real-world outcomes. Consult a qualified healthcare provider or certified coach before making training decisions based on these outputs.