Run Woodstock
Michigan
Next race
- Map
- Profile
- Character
GPS trace: 1,121 pts / www.runwoodstock.com
- Gently Rolling
- Parkland
- Forest
- Lakeside
- Ascent
- 1,764 m
- m/km
- 11.0 m/km
Mapped terrain routes
14 mapped ultramarathon race pages tagged as gravel. Elevation metrics appear only where the source route supports them.
Mapped race pages
Michigan
Next race
GPS trace: 1,121 pts / www.runwoodstock.com
Washington
Latest edition
GPS trace: 1,341 pts / www.cascadecrest100.com
Washington
Next race
GPS trace: 1,484 pts / chuckanut50krace.com
Nebraska
Next race
GPS trace: 1,436 pts / www.gravelworlds.com
South Dakota
Latest edition
GPS trace: 1,186 pts / leanhorseultra.com
Kentucky
Next race
GPS trace: 1,485 pts / www.nextopportunityevents.com
Slovenia
Latest edition
GPS trace: 1,469 pts / soca-outdoor.com
Norway
Next race
GPS trace: 1,391 pts / strandafjordtrailrace.com
Virginia
Next race
GPS trace: 1,324 pts / enduranceeventsva.com
Kentucky
Next race
GPS trace: 1,197 pts / www.crookedcreek100.com
Arkansas
Latest edition
GPS trace: 585 pts / www.fullmoon50k.com
Virginia
Next race
GPS trace: 1,370 pts / runmmtr.com
Wyoming
Latest edition
GPS trace: 1,109 pts / bighorntrailrun.com
Wisconsin
Latest edition
GPS trace: 763 pts / runningfitevents.redpodium.com
A race appears in a route-map collection only when raceindex.org has stored route geometry. Elevation, ascent and GAP values appear only when the route has enough elevation-bearing evidence for a publishable profile; unsupported signals are omitted.
A ultramarathon race must have stored route geometry and a source-backed terrain tag of gravel to appear here.
No. Elevation profiles appear only when the stored route has enough elevation-bearing points for a publishable profile.
This collection includes only races with stored route geometry and the matching route-character tag. Other races can still appear in the main race catalogue with route-attempt status shown on their race pages.