Burning River is an endurance event in northeast Ohio, with 100-mile and 50-mile races, a marathon and a 100-mile relay. Its routes travel through Cuyahoga Valley National Park and Summit Metro Parks.
Region
Northeast OhioRoutes include Cuyahoga Valley National Park and Summit Metro Parks.Source
4 TUM reports · Published coverage below
Publication history
Coverage over time
4 editorial issues
Distinct issues per publication month. Each issue counts once.
Jul 2024Peak 2Nov 2026
Monthly editorial issue counts: Jul 2024: 2; Aug 2024: 0; Sep 2024: 0; Oct 2024: 0; Nov 2024: 0; Dec 2024: 0; Jan 2025: 0; Feb 2025: 0; Mar 2025: 0; Apr 2025: 0; May 2025: 0; Jun 2025: 0; Jul 2025: 0; Aug 2025: 1; Sep 2025: 0; Oct 2025: 0; Nov 2025: 0; Dec 2025: 0; Jan 2026: 0; Feb 2026: 0; Mar 2026: 0; Apr 2026: 0; May 2026: 0; Jun 2026: 0; Jul 2026: 1; Aug 2026: 0; Sep 2026: 0; Oct 2026: 0; Nov 2026: 0.
Sponsor mentions, repeated links and polls are excluded. Credits within editorial items may count. Read the supporting timeline ↓
In The Ultra Minute
Newest first
Published in TUM
Burning River’s 20th running, with preliminary results labeled
Jordan Lafreniere and Stacey Billig led the preliminary 100-mile men’s and women’s results in 15:34:45 and 19:18:38. Caleb Bowen and HollyAnn Swann led the separate 50-mile results. These retain their preliminary publication-time status.
TUM identified Sean Cate as Roots Running Podcast host and relayed his 2025 Burning River 50 account, including help from Arlen Glick. Glick’s cited 100-mile record is a separate historical result.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.
Published article, 2025-08-02T11:26:18.233Z. Public original captured at 2026-10-27T22:18:13.835Z and projected to reviewed article text; no publishing-repository text pin is claimed.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.
Published article, 2024-07-29T14:07:40.458Z. Public original captured at 2026-10-30T17:04:58.576Z and projected to reviewed article text; no publishing-repository text pin is claimed.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.
Published article, 2024-07-22T15:36:42.172Z. Public original captured at 2026-10-30T17:04:58.580Z and projected to reviewed article text; no publishing-repository text pin is claimed.
Exact public destination in the published item. The archived TUM issue establishes the historical attribution; this is not a fresh verification of the destination’s current content.