One real ride. The real screen.
One of our own road races, 143 km. The exact screen a rider sees after an upload.
For a fair number, the ride has to start and finish in the same place. An out-and-back on a quiet road works, and so do laps of a loop or a velodrome. A one-way ride cannot give one. Where to test
FIT, Notio JSON, GiBLI CSV, Aerosensor FIT, ZIP or GZ
A few questions. Each one sets a measured input, so you can see exactly what goes into the number.
Why we ask: your tyre sets the rolling resistance (Crr), looked up from the BicycleRollingResistance table and corrected for temperature, not folded into the fit.
Why we ask: this sets drivetrain efficiency, taken from the spec card, not an assumed constant.
Why we ask: the device sets the wind convention AeroEdge reads, so apparent air is interpreted correctly.
Why we ask: rider plus bike is the mass the run is measured against.
Why we ask: temperature corrects the Crr from the tyre table.
About this ride: it was a race, so the CdA is a race estimate, not a clean aero test. The corners are in the report. The app uses a corner only when the GPS recorded enough points through it.
With uploads
PaidAnalyse another ride
Keep your tyre, drivetrain, weight and format answers, and read a new ride from the top.