Find your racing connections.
Look up a racer. Explore the tracks they race, districts in their results, and the race crowds those tracks share.
Find the tracks you share.
Explore a rider’s public race history or compare two venues. Matching names and known hometowns bring records together across sources.
Shared racers
See which race crowds connect.
Mutual venues
Follow the tracks your race crowd visits.
Published hometowns
Explore where each audience comes from.
Pick two tracks. Find the connection.
Choose the same district or compare across districts. National / series results use published event locations when exact track names are unavailable.
Explore districts near you.
Use your current location or pick a state to bring nearby programs to the top.
Your browser asks for location permission only when you click. Your coordinates stay on this device.
Suggestions use broad program home regions, not exact district boundaries or driving distance. Only districts in this growing directory can appear.
Looking beyond these districts?
Use the AMA’s national results center to explore programs that are not yet included here.
Open the AMA national results center ↗What is included?
National reach is different from complete coverage. This page shows captured public reports, missing reports and sources that still need an import adapter.
Source inventory
AMA 2026 national event directory
Outdoor MX candidates are identified by published titles. Explicit arenacross/supercross, ATV/quad, stadium, hillclimb and flat-track titles are excluded from this national import. Original regional feeds retain their source classifications.
Help improve MXmetric.
Tell us about a missing racer, incorrect match, duplicate track or wrong result. Reports are saved for review; they do not change results automatically.
See what connects motocross.
MXmetric helps racers explore their published race history and helps clubs understand the race crowds their tracks share. It is an independent beta built from public results.
What the numbers mean
Racer profiles are source rider records or estimated groups matched by full name and known hometown. They are not verified unique people.
Event appearances count a profile at an included event. Class entries count each entered class, so one appearance can produce several entries. Cross-posted results can repeat across sources.
Know the limits
Coverage is partial. Missing results mean “not observed here,” not “never raced.” Some reports lack hometowns, districts or exact track names. Source event classes can include support disciplines.
Districts in results do not establish official district membership. MXmetric is not affiliated with or endorsed by AMA or the result providers.
Check data coverage · Report an issue · Read privacy information
Public racing data, handled openly.
Race records
MXmetric stores names, published hometowns, race entries and source references from public result reports. Original sources remain linked. Matching names and known hometowns can still refer to different people; matches are estimates.
Location and searches
District discovery uses location only after you click and grant browser permission. Coordinates stay in your browser and are not sent to the MXmetric API or saved by this app. Name searches are sent to the app to retrieve results. MXmetric has no advertising or analytics scripts installed.
Correction reports
The report form stores the issue type, optional racer/track name, your description, an optional public source link, the current app view, submission time and review status. We do not ask for email, phone or membership details. Reports remain stored for review; automatic deletion is not configured. Reports are not displayed publicly, and no email notifications are sent.
Hosting and access
The hosting platform handles access and sign-in. Its own processing is covered by its privacy policy. The MXmetric app does not provide a public report-list endpoint.
Corrections or removal
Use Report a problem and choose “Privacy or removal request.” Include only the public record link and the requested change. Save the report reference shown after submission. Review is manual; there is no guaranteed response time. Changes here do not change the original result provider’s records.
What these numbers mean
“Districts raced in” means the district program represented by a public result feed. It does not establish AMA district membership. Across sources, exact normalized full names with a known matching town and region are grouped automatically. Missing hometowns, different hometowns, fuzzy names and ambiguous duplicate IDs remain separate. A matching profile is an estimate, not identity verification; original records remain linked.
Shared racers within a collection use the same rider IDs. Cross-collection matches use the name-and-hometown grouping rule. “Only at” means not observed at the other selected track in the included listings, never a lifetime claim. Event/day counts and visits are different from class entries.
Published class-entry totals retain source classifications. Mixed event reports can include ATV or balance-bike support classes. Racer profiles are estimates, not verified unique people.
Rider-profile nearby links use the program’s home state and same/land-bordering states. Location-based district discovery ranks broad program regions using state reference centers; selecting a state prioritizes programs in that state. These are not official district boundaries, driving distances, or a statement that a rider raced there. Public hometowns can be missing; unknown remains unknown.
State reference coordinates: Google Public Data, CC BY 4.0. Used for approximate regional suggestions.