Peterson’s Hundred Mile Wilderness account
Will Peterson’s 26:55:45 was listed as the men’s unsupported FKT. He described a late change of plans and his five-year speed chapter on the route with Xander Keiter.
Athlete
Will Peterson is an ultrarunner and long-distance backpacker whose first-person author biography traces his start in long-distance travel to an Appalachian Trail thru-hike in 2019. His published writing includes accounts of New England route records.
16 TUM reports · Published coverage below
Publication history
14 editorial issues
Distinct issues per publication month. Each issue counts once.
Monthly editorial issue counts: Jul 2024: 0; Aug 2024: 0; Sep 2024: 1; Oct 2024: 0; Nov 2024: 0; Dec 2024: 0; Jan 2025: 1; Feb 2025: 0; Mar 2025: 0; Apr 2025: 0; May 2025: 0; Jun 2025: 0; Jul 2025: 0; Aug 2025: 2; Sep 2025: 1; Oct 2025: 0; Nov 2025: 0; Dec 2025: 0; Jan 2026: 0; Feb 2026: 0; Mar 2026: 0; Apr 2026: 0; May 2026: 5; Jun 2026: 0; Jul 2026: 0; Aug 2026: 1; Sep 2026: 1; Oct 2026: 2; Nov 2026: 0.
Sponsor mentions, repeated links and polls are excluded. Credits within editorial items may count. Read the supporting timeline ↓
Newest first
Will Peterson’s 26:55:45 was listed as the men’s unsupported FKT. He described a late change of plans and his five-year speed chapter on the route with Xander Keiter.
TUM reported Will Peterson’s unsupported effort and compared it with Austin Black’s listed mark. The issue did not establish a formal new FKT listing.
TUM previewed the September 13 Tor des Géants start and linked Finn Melanson and Will Peterson’s Singletrack conversation.
TUM recorded a tracker snapshot of the unsupported Long Trail effort and its gap to Peterson’s record pace, before the later stop.
TUM reported that he ended his self-supported Appalachian Trail FKT attempt after falling too far behind his target pace.
Will Peterson’s team reported improvement during his self-supported Appalachian Trail attempt, a lost phone and a replacement stop. The reported gap to plan narrowed to 42 miles; this was an in-progress update before the later end of the attempt.
TUM reported Will Peterson’s 57-mile Day 20 at mile 932 of his self-supported Appalachian Trail attempt, 46 miles behind plan. This checkpoint precedes the later end of his attempt.
Will Peterson’s team reported a difficult Day 16 and said he was moving again during the Appalachian Trail attempt. This in-progress account precedes the later end of the attempt.
Will Peterson was reported 398 miles into his self-supported Appalachian Trail attempt on Day 9, ahead of plan. This precedes the later end of the attempt.
TUM cited Peterson’s 2024 Long Trail mark as the earlier overall benchmark.
TUM cited his 2024 supported Long Trail mark as Dower’s target.
TUM cited his 2023 unsupported Long Trail time of 4d11h34m, separate from his 2024 supported mark.
TUM described Will Peterson helping create Fastest Known Time’s Northeast regional notable-routes list in 2025.
TUM highlighted Fastest Known Time’s 2024 countdown: Krupicka, Hegemann, Sansone/Hamilton at number5; Power/Fowler at4; Porter/Curtin at3; Anderson/Peterson at2. These are annual-list positions, not race podiums or interchangeable current FKT categories. The source specifically described Fowler’s Arizona Trail effort as self-supported; number one had not yet been revealed.
Event date: 2024 · TUM publication: January 2, 2025
TUM reports Will Peterson setting a Long Trail FKT of 3 days, 21 hours and 10 minutes, breaking four days; the source does not specify direction or a formal support category.
Event date: 2024 · TUM publication: September 3, 2024
In the quotation introduced as Peterson’s Instagram post, he credits dozens of locals with the Long Trail effort and describes himself as the runner; it repeats the 3-day, 21-hour, 10-minute time.
Event date: 2024 · TUM publication: September 3, 2024
Original public source
Original public context, separate from the dated TUM account.
Will Peterson / The Trek
Route record
Men’s unsupported FKT, 26:55:45 · 2026-10-16
SourceMedia appearance
Participant in the Tor field-preview discussion · 2026-09-11
SourceEnded his self-supported Appalachian Trail FKT attempt
Will Peterson ended the Appalachian Trail FKT attempt TUM had followed at self-supported record pace. He said he had lost roughly 120 miles over a week and accepted that the target was out of reach.
SourceReported 2024 FKT of 3d 21h 10m
TUM reports Will Peterson setting a Long Trail FKT of 3 days, 21 hours and 10 minutes, breaking four days; the source does not specify direction or a formal support category.
SourceSource publication and event dates are shown separately.
Reported 2026-05-22
TUM reported that he ended his self-supported Appalachian Trail FKT attempt after falling too far behind his target pace.
TUM · May 22, 2026Reported 2026-05-20
Will Peterson’s team reported improvement during his self-supported Appalachian Trail attempt, a lost phone and a replacement stop. The reported gap to plan narrowed to 42 miles; this was an in-progress update before the later end of the attempt.
TUM · May 20, 2026Facts above link directly to their sources. Published TUM dates and public-source check dates describe different things.
Public background sources checked October 18, 2026. The selection contains 127 published issues.
Facts are limited to selected published accounts and retain their dates. Original links may change or require sign-in; no live status or current affiliation is implied.
Career context from one original public source. TUM’s dated reporting appears below.
This is a limited career snapshot, checked October 18, 2026. Source publication dates and event dates are shown separately.
The published newsletter is the authority for each October 12 mention.
Exact destination preserved from the published item. Supports the item’s original attribution; not a claim that its current state was freshly checked.
Exact destination preserved from the published item. Supports the item’s original attribution; not a claim that its current state was freshly checked.
Published article, 2026-09-11T18:18:01Z. Archived published text is pinned to canonical main 0b95fbf3ae3a.
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, 2026-08-17T16:54:00Z. Archived published text is pinned to canonical main 032eba22cd61.
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.
This URL returned 404 at the 2026-10-15 check. The TUM issue preserves the dated attribution.
Published article, 2026-10-16T19:49:15Z. Archived published text is pinned to canonical main 832e6528bf19.
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, 2026-05-22T04:14:25.716Z. Public original captured at 2026-10-23T01:32:51.614Z 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.
Published article, 2026-05-20T06:38:01.226Z. Public original captured at 2026-10-25T00:14:26.912Z 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.
Published article, 2026-05-19T05:41:39.084Z. Public original captured at 2026-10-25T00:14:26.843Z 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.
Published article, 2026-05-14T04:47:00.000Z. Public original captured at 2026-10-27T16:49:12.856Z 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.
Published article, 2026-05-07T05:45:12.790Z. Public original captured at 2026-10-27T18:56:10.725Z 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.
Published article, 2025-09-06T12:46:42.719Z. Public original captured at 2026-10-27T18:56:10.730Z and projected to reviewed article text; no publishing-repository text pin is claimed.
Published article, 2025-08-16T09:01:10.641Z. Public original captured at 2026-10-27T22:18:13.818Z 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.
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-08T17:53:54.883Z. Public original captured at 2026-10-27T22:18:13.833Z 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.
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-01-02T23:04:55.958Z. Public original captured at 2026-10-30T08:39:44.975Z 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.
Published article, 2024-09-03T20:36:26.572Z. Public original captured at 2026-10-30T15:10:54.389Z 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.