What appears in a city running race guide?
A city guide lists race pages with the same source-backed event locality and summarises distance coverage, stored route maps and elevation profiles where available.
Loading
Loading page
City race guides
City running race guides with source-backed locality data, mapped-route counts, elevation-profile coverage and distance breakdowns.
Browse cities
DC; 25 race pages across 5 distances, with 3 mapped routes and 2 elevation profiles.
New Mexico; 21 race pages across 6 distances, with 3 mapped routes and 3 elevation profiles.
Nebraska; 20 race pages across 6 distances, with 14 mapped routes and 4 elevation profiles.
Kentucky; 17 race pages across 5 distances, with 6 mapped routes and 0 elevation profiles.
Iowa; 17 race pages across 8 distances, with 3 mapped routes and 0 elevation profiles.
London; 16 race pages across 6 distances, with 2 mapped routes and 2 elevation profiles.
Nevada; 15 race pages across 5 distances, with 6 mapped routes and 3 elevation profiles.
Idaho; 13 race pages across 4 distances, with 12 mapped routes and 0 elevation profiles.
Alaska; 13 race pages across 9 distances, with 6 mapped routes and 0 elevation profiles.
Texas; 13 race pages across 6 distances, with 1 mapped routes and 1 elevation profiles.
Washington; 12 race pages across 6 distances, with 11 mapped routes and 4 elevation profiles.
Kansas; 12 race pages across 5 distances, with 7 mapped routes and 0 elevation profiles.
Nevada; 12 race pages across 6 distances, with 5 mapped routes and 2 elevation profiles.
Missouri; 12 race pages across 5 distances, with 1 mapped routes and 1 elevation profiles.
Louisiana; 12 race pages across 8 distances, with 0 mapped routes and 0 elevation profiles.
Kansas; 12 race pages across 6 distances, with 0 mapped routes and 0 elevation profiles.
Hungary; 11 race pages across 6 distances, with 7 mapped routes and 7 elevation profiles.
Colorado; 11 race pages across 6 distances, with 7 mapped routes and 0 elevation profiles.
Nebraska; 11 race pages across 7 distances, with 6 mapped routes and 3 elevation profiles.
Georgia; 11 race pages across 6 distances, with 0 mapped routes and 0 elevation profiles.
Wisconsin; 10 race pages across 6 distances, with 10 mapped routes and 10 elevation profiles.
South West; 10 race pages across 5 distances, with 9 mapped routes and 9 elevation profiles.
Washington; 10 race pages across 6 distances, with 9 mapped routes and 0 elevation profiles.
Mississippi; 10 race pages across 6 distances, with 7 mapped routes and 7 elevation profiles.
Ohio; 10 race pages across 4 distances, with 7 mapped routes and 4 elevation profiles.
South Dakota; 10 race pages across 5 distances, with 4 mapped routes and 4 elevation profiles.
South Carolina; 10 race pages across 4 distances, with 4 mapped routes and 0 elevation profiles.
Tennessee; 10 race pages across 5 distances, with 2 mapped routes and 0 elevation profiles.
Alabama; 10 race pages across 4 distances, with 1 mapped routes and 0 elevation profiles.
Montana; 10 race pages across 6 distances, with 0 mapped routes and 0 elevation profiles.
New Mexico; 10 race pages across 6 distances, with 0 mapped routes and 0 elevation profiles.
California; 10 race pages across 7 distances, with 0 mapped routes and 0 elevation profiles.
A city guide lists race pages with the same source-backed event locality and summarises distance coverage, stored route maps and elevation profiles where available.
No. City guides use exact event locality strings rather than radius or nearby claims, because raceindex.org does not yet publish normalised latitude and longitude coverage for every race.
A city guide is published only when the city has enough race pages to avoid a thin collection. Cities below the threshold remain discoverable through race search and regional guides.