Begins on the original Heartland 100 course, adds a 30-mile detour loop out to Eureka, KS starting at mile 15 (turn at Lapland), rejoining the 100-mile route at Thrall before mile 50. "Graduate Level" format: the Eureka loop has minimal course marking, and runners navigate it from a provided turn-by-turn map. A roving/mobile aid station covers the Eureka loop overnight; reflective gear is required on that section.
An out-and-back 100-mile ultramarathon run entirely on backcountry gravel and dirt roads through the Flint Hills tallgrass prairie near Cassoday, Kansas -- rolling hills, open range with loose cattle, near-constant wind, and almost no shade for the whole course. Kansas' original 100-mile race, held annually in October. The same start/finish and road network host a full weekend of distances (4-person relay, 125 Mile, 100 Mile, 100K, Teter Rock 100K, 50 Mile, Cassoday Marathon, Teter Rock 1/2 Marathon), all truncations or extensions of the same out-and-back route.
The inaugural Heartland 100 Spirit of the Prairie ultra began in 2000, directed by KUS members Randy Albrecht and Jim Davis; a 50-mile distance was added in 2001. This is independently corroborated: a November 2003 newspaper account describes that October's race as the "fourth annual," and DUV Ultra Marathon Statistics records the 2009 race as the "10th Heartland 100 Mile Race" -- both consistent with a 2000 founding. NOTE, UNRESOLVED CONFLICT: the race's own marketing counted 2025 as its "25th Anniversary" and Facebook/ATRA material calls the 2026 race the "26th" Heartland 100 -- one year off from what a continuous count from 2000 would produce (2025 would be the 26th annual, 2026 the 27th). Possibly a cancelled/skipped year is not counted in the anniversary number (no specific cancelled year found); recorded as a conflict, not resolved.
Nobody sees it until we have read it. No account, no sign-in.
This changes nothing on the page on its own. Somebody checks it against the race first.
We want the address of the file the race publishes, not the file. We download it from there so the page can say where the line came from.
We read every one of these and we write back. Every fact here carries the source it came from, and the way a wrong one gets fixed is a person checking it against what you tell us.
NavRun builds your pacing from your own training, then turns it into a plan your crew can follow: when to leave and where to park.
Start free