RemoteRacing™ is device agnostic allowing participants to use their choice of training devices and virtual cycling apps. The system analyzes both the activity data and the devices/apps that produced them to account for variances in accuracy and computations.

Virtual App Normalization

Normalization for virtual environment app variances such as CdA calculation and weight (Zwift, Rouvy, and others don’t calculate CdA in precisely the same way). Not a major thing, but we’ve got it.

Device Accuracy Reduction

Bike power sensors (including smart trainers and power meters) have varying degrees of accuracy. This is generally relative to their cost.

To ensure fairness of competition and allow all participants to use the equipment they have or can afford, RemoteRacing applies a Device Accuracy Reduction to offset any potential advantage for participants using less accurate bike sensors.

Participants with top-quality equipment are not impacted.

All others will have a Device Accuracy Reduction relative to the accuracy of their specific equipment.

Participants’ remote race bike result (power) is reduced by their Device Accuracy Reduction. This reduced power is used in their Onsite Sim to generate their official localized finish time.

Each participant’s Device Accuracy Reduction is calculated as the device’s accuracy rating percent minus a standard top-end accuracy rating of one percent.

Your Device Accuracy Reduction, if any, is shown on your Remote Bike Summary page.

Threshold Accuracy Reduction

Threshold Accuracy Reduction only applies to participants using bike power without GPS data (distance).

Instead of performing a distance-based bike effort, athletes participating without GPS data (power only; no distance) will perform a duration-based effort with a duration equal to their predicted bike split shown in RaceX.

This predicted bike duration is based on the participant’s threshold (FTP). RaceX will show both the predicted time and the target watts to hold for this duration based on what the participant has submitted as their threshold. Participants may adjust their threshold to whatever value they believe best reflects their ability.

If the participant holds the target watts (or higher) for the specified duration, then no Threshold Accuracy Reduction is applied.

If the participant holds less than the target watts for the duration, this means that they overstated their Threshold and their predicted duration should have been longer. In this case, a Threshold Accuracy Reduction equal to the target watts minus actual watts is applied. In most cases, any Threshold Accuracy Reduction for an athlete with an honestly submitted threshold is negligible.

Each participant’s remote race bike result (power) is reduced by their Threshold Accuracy Reduction. This reduced power is used in their Onsite Sim to generate their official localized finish time.

If you’re using power only and uncertain of your threshold ability, it’s best to err on the side of entering a slightly lower threshold value.

What's the purpose of this Threshold Accuracy Reduction? This prevents participants from overstating their threshold ability to produce a shorter bike split prediction than they would be capable of if they were performing a distance-based effort.

Your Threshold Accuracy Reduction, if any, is shown on your Remote Bike Summary page.