Runner's insane stat line

Attempts to open the two X.com links in the card returned no public content because X has restricted anonymous viewing and many third‑party front‑ends that previously let people read threads without an account became nonfunctional after API and guest‑access changes in early 2024. (gHacks.net). Public reporting and developer issue threads document that Nitter and similar alternative front‑ends lost reliable access after X tightened its API and blocked guest‑account workarounds around January–February 2024, which makes direct inspection of some threads impossible without a logged‑in X account. (GitHub; IndieWeb). Benchmarking the finishes the thread lists against large race datasets shows those performances sit well above recreational norms: RunRepeat’s comparator puts a 10K 10% threshold around 48:11 and the 1% benchmark near 36:18, providing context for where the thread’s 10K result falls relative to mass‑race fields. (RunRepeat). Wide analyses of half‑marathon fields put the median and many recreational averages near 1:50, so the half‑marathon result named in the thread is substantially faster than typical finishers in large U.S. datasets. (Outside Online; MarathonHandbook). Race‑time breakdowns and percentile tables used by clubs and aggregators show a sub‑39‑minute 10K typically ranks among the faster finishers in many community and club cohorts, indicating the thread’s 10K would place the poster well into competitive club‑runner territory rather than casual‑jogger ranks. (MarathonHandbook; FetchEveryone). Because the X thread appears to be the primary public source for the combined race results and the daily cross‑training claims, and because platform access is gated, independent corroboration via searchable race‑result aggregators or publicly linked training logs was not locatable during verification checks conducted through publicly accessible channels. (gHacks.net; Strava running‑pace tools).