Overview

This is a system to generate the control times used in Randonneurs USA (RUSA) and ACP Brevets. It was written by Jake Kassen (me@jkassen.org). RUSA has a simalar system for determining these times but it doesn't support Gravel events (yet) and it's not as interactive. This system should produce identical results.

How to Use

At minimum all you need is the distance of a route or event to see the offical min/max times. All distances assume miles but will convert from kilometers if the distance entered is followed by "k". For ACP events, use ACP metric distance such as "200k", "400km", etc. The rest should be self explanatory.

Things to Remember

1. The finish control uses the event distance. In most cases the event is slightly shorter than the route. Make sure the finish control lists the correct ending distance for the route but the closing times of the event. Riders do not receive extra time for routes which are "over distance".
2. Distance are truncated for time calculation! If a control is at 55.9 miles, the times produced as if the control was at mile 55.0. [Ed note: I support changing this rule. Give riders the extra time!]
3. Intermediate controls are untimed on Gravel events. This system shows the effective intermediate control times for reference.
4. This system won't check RUSA rules. For example, you can't use a 230km route for a 200k event.

Notes about Calculations

1. The rules for these times can be found on the RUSA site. The formula for Gravel events is provide 20% more time on the portion of the route which is gravel based on the "road" minimum speed.
2. For the first 60km of routes, the closing time of controls in this section is extended to provide a "catch-up" opportunity for riders who might have started up to an hour late.
3. For events that are exactly 200k and 400k, riders receive a 10 and 20 minute respective "bonus" to the finish closing time. Based only on speed the closing time for a 200k should be 13h 20m but ACP tries to simplify the math by rounding to 13h 30m.
4. There are other esoteric rules regarding control times. If in doubt, ask the RBA Liaison or the RUSA Board.

Bugs? Questions?

Please contact me at me@jkassen.org!

API for Time Calculations

This site provides an API for anyone interested. It's easy to use.

Usage

Endpoint: https://rusa.jkassen.org/time/rusa-time-api.php

The above URL can be sent the following parameters via GET or POST. The data returned is JSON.

All parameters are optional. If sent without an event_distance, only the intermediate control times (if using) will be useful.

• event_distance - This is the event distance. Assumes miles, add a "k" if using kilometers.
• route_distance - The route distance. This only appears as the distanced listed for the finish control. The times for the finish control are based on the event distance.
• gravel_distance - Self explanatory. Assumes miles, add a "k" if using kilometers.
• start_date - If unset assumes next Saturday. Supports any date format that PHP's strtotime() function supports.
• start_time - If unset assumes 07:00. Supports any time format that PHP's strtotime() function supports.
• JSON Array of controls with the keys DISTANCE and NAME. DISTANCE is required, assumes miles, add "k" for metric.

Examples using GET

A 200k starting next Saturday @ 7am: Link

A 375 Mile event starting July 4th 2027 @ 8:52pm with 325k of Gravel and 4 controls: Link

Bugs? Questions?

Please contact me at me@jkassen.org!