Karel: The GPX file from the FKT site has broken timestamps. After correction, I calculated less than 1800 miles - clearly inaccurate. I manually analyzed the GPX track to determine daily start and stop times, cross-checking with the official distance table and Karel's Strava activity logs. The resulting moving/rest times are only rough estimates, resulting in my total calculated time being 41d1h rather than the official 41d7h39m.
John: Strava GPX files lack timestamps. Instead, I extracted lap data manually. His pace may be inflated if pause times aren't reflected in laps, though moving and elapsed times are mostly consistent. Rest time is calculated as: next start time – previous elapsed time. Times don't match the official tracker splits, likely due to GPS errors. As of day 30, my ~73-mile lead estimate aligns with the live map measurement. The cumulative distances matched John's Strava activity titles up until Day 17, after which I'm unsure what distance source John/his team is using to calculate the titles, but it could be trail markers or a more reliable measurement than John's GPS watch. It appears they round to the nearest mile and a couple days add or subtract 10 miles (possibly by accident or because of actual distance being different from the GPS recording).
Tara: The GPX from the FKT page is missing Aug 14–20. I used the table screenshot instead. Since the GPX data and table disagree even on the first two days, I assume the GPX underreports distance and chose the table as the more complete source.