Purpose
A reusable bundle describing the athlete + bike that all physics depends on.
Contents
Rider profile: linked from your account settings. Weight and Height are required; sex, age, FTP, max. heart rate and training zones are optional.
Bike type (fixed choices): Triathlon, Time trial, Road race, Road endurance.
Positions & CdA: two positions per bike type with an estimated CdA (Base bar / Aerobars for Triathlon and Time trial, Hoods / Drops for road bikes).
Speed range: defines when the rider switches between the two positions. The default switch speed is 20 km/h (12 mph).
Bike weight.
Gearing: chainring(s) and cassette range used on the bike.
Default values (rider height 1.80 m)
The CdA estimate scales with your height; bike weight and gearing are defaults per bike type.
Bike type | CdA position 1 | CdA position 2 | Bike weight | Chainring(s) | Cassette |
Time trial | 0.28 (Base bar) | 0.22 (Aerobars) | 8 kg | 56 | 11–28 |
Triathlon | 0.32 (Base bar) | 0.25 (Aerobars) | 8.5 kg | 52/36 | 11–34 |
Road race | 0.40 (Hoods) | 0.30 (Drops) | 7 kg | 52/36 | 11–30 |
Road endurance | 0.45 (Hoods) | 0.35 (Drops) | 7.5 kg | 50/34 | 11–34 |
Base vs inline edits
Use the collection setup as a base.
Inside an optimization, click Edit on the rider setup card to adjust it (e.g., CdA via Custom positions or gearing via Custom gearing) without changing the setup in your collection.
Only promote it to your collection (Save in my collection) when an edit is broadly reusable (e.g., a new 2026 fit).
If you change your rider profile later, setups inside existing optimizations show "Your rider profile has changed." with a Reload button.
When to create multiple setups
Different bikes (TT vs road), fit changes, or “baseline vs aggressive aero”.
The number of rider setups you can keep depends on your plan; see Quotas & limits on the start page and Plans, trial & credits 💳.
Gotchas
Unrealistic CdA drives unrealistic gains. Stay in plausible ranges unless you’ve measured it.
Speed range of the positions can materially change pacing—treat it intentionally.
The faster position must have a lower CdA than the slower one. If it doesn't, the simulation uses the lower CdA position.