Fenchurch St and Charing Cross Both Stuck at 64% On-Time — But the Data Trail Runs Cold

The estate's monitoring tools registered London Fenchurch Street and London Charing Cross both running at 64% on-time performance, a pairing flagged as worth a look given the ongoing strain on London's rail network noted in prior tracking (see memory id 22). But the two web sources retrieved to substantiate that number contain no punctuality statistics whatsoever. The National Rail page for the Fenchurch Street to Charing Cross route, according to [1], is largely promotional — it covers Railcard discounts, advance-ticket savings and a "Days Out Guide" for attractions near Charing Cross. There is no live or historical on-time data on the page. The South Western Railway page for the reverse journey, Charing Cross to Fenchurch Street, according to [2], was even less useful for verification purposes. It states plainly that the operator is "currently experiencing technical issues" with its live departures and arrivals feature, and that "there are no trains departing from this station in the next two hours" — a message that reads as a system outage notice rather than a genuine service gap, since it appears on both the Charing Cross and Fenchurch Street sections of the same page. Neither source confirms, denies or contextualises the 64% figure the instruments flagged. It is unconfirmed here how that number was derived, over what time window it applies, or which operators' services it aggregates — Fenchurch Street is served by c2c, while Charing Cross is a Southeastern terminus, and a South Western Railway page turning up for a route between the two is itself a mismatch worth noting, since South Western Railway does not operate either station. What can be said is that the retrieved evidence is consistent with general disruption on London's rail network — the kind of live-data failures and technical caveats that tend to accompany periods of service strain — but it does not independently verify the specific 64% punctuality reading, nor does it establish any causal link between the two stations' performance. The echo with memory id 22's broader London rail strain thesis remains plausible but unproven on this evidence. Separately, the estate's instruments also surfaced a gov.uk company strike-off notice alongside this rail item. Nothing in the material retrieved connects that notice to either station, either operator, or to London rail infrastructure generally. Absent any shared entity, date or geography in the sourced text, the co-timing looks coincidental rather than connected, and no further claim is made here. Worth flagging plainly to Wayne: this is a case where the trigger's headline number outran what the fetched pages could actually support. The instruments spotted a pattern; the source material didn't hold it up. What to watch next: whether a direct operator or Network Rail performance dashboard for c2c (Fenchurch Street) and Southeastern (Charing Cross) can be pulled to confirm or correct the 64% figure independently.