AutocrossRank
About This Site

Built to track autocross history, results, classes, and rankings in one place.

AutocrossRank.com brings together event results, driver history, class and PAX data, uploads, claims, and public rankings so racers and fans can follow performance across seasons.

What AutocrossRank Does

The site is designed to make autocross data easier to explore and easier to trust. Visitors can browse events, drill into class results, look up drivers, review class and PAX information, and see public driver rankings built from imported event data.

For signed-in users, the site also supports uploads, result claiming, and account-level history. For admins, it adds review tools, parsing workflows, class management, and ranking controls.

About Chris Hammond

AutocrossRank.com is the work of Chris Hammond, an autocrosser from St. Louis who has been part of the sport for more than 25 years.

Chris first launched Christoc.com's Racing Forums, which later evolved into Pylon.cc and ultimately SOLO2.ORG. This site continues that long-running effort to give the autocross community useful tools, shared history, and a place to follow the sport online.

Pick The Winners

AutocrossRank.com is also the home of the annual Pick The Winners contest. That tradition is coming back again for the 2026 season.

Learn More About Pick The Winners

What's Public Today

Public visitors can already browse events, drivers, classes, and rankings without needing to log in. As more data is reviewed and imported, the historical picture should keep getting better.

How The Current Ranking Algorithm Works

The current system is a margin-based ranking. Every driver starts with the same base score, then gains or loses points event by event based on who they beat in the same class and by how much.

1. Rankings are computed inside each class, not across all cars at once.
For each event, the algorithm groups drivers by class and only compares drivers who actually ran against one another in that class.
2. It uses each driver’s stored event result time.
Right now the default configuration uses the stored raw event time. If PAX-adjusted times are enabled later, the same process can use those instead.
3. Beating faster people by a bigger margin helps more.
Within a class, the algorithm compares every valid finisher head-to-head. If your time is better than another driver’s time, you gain points from that matchup. If you are slower, you lose points.
4. One event cannot swing the rankings too wildly.
After all head-to-head comparisons are added up for an event, the total event gain or loss is capped so a single result does not completely dominate the season picture.
5. Bad or incomplete results should not count as valid finishes.
A result is excluded from ranking comparisons if it has no usable event time, or if it appears to be an incomplete multi-course result where only part of the required day was actually completed.
6. Invalid results can still show that a driver attended, but they are treated like a loss for ranking purposes.
If a driver has an invalid result in a class where valid competitors finished, the algorithm applies a capped loss instead of rewarding the row with a suspiciously low partial time.
7. Final order is by score first, then wins and event count.
After all events in the chosen scope are processed, drivers are sorted by score. Wins and total ranked events are then used as tie-breakers.

In plain English: the algorithm tries to reward drivers for consistently finishing ahead of strong competitors in their class, while ignoring result rows that look incomplete or unreliable.