I take it this was 1B21 on 13/6/23.
Liverail/Livetrain (or Open Rail) does indeed show it as arriving
SWA» 1836, 4 late. However, that's after it left Neath 1843, so you are entitled to think the system has got mixed up. The departure time of the continuing part of the train is 1908, agreeing with
RTT» .
I suspect a conflict between different data feeds. Livetrain has "
TRUST▸ Event Data" as its heading, while RTT shows "TD(C6)" (i.e. train describer data) for its times.
GWR▸ may be using this Open Rail software as a simple tool, or internal access to TRUST, with similar results. RTT would not be much use to them because of its limited history. They ought not to need "amateur" open data service at all, so it's probably a case of relying of TRUST data. But you need a real expert in this to identify the real answer.
That's useful to know. Now the appeal is done I have to follow complaint procedure, but hopefully if a human looks into it properly they can see there's unrealistic data. I'll present a screenshot of RTT (live data will expire soon) – might not be "admissible" but at least as evidence to say there's an error to investigate. Part of me says forget it for £1.25, but I have a thing about companies giving false information, and not correcting it when given the opportunity.
I note on RTT that a London train left SWA P3 at 18:28, then the stock from an earlier arrival was presumably shunted back in to form the 19:23. Perhaps that shunt arrived at 18:36, and for some reason the wrong headcode was entered. In the RTT world, the arrival of the real train would override that, but maybe internal systems work differently. Not particularly relevant to the claim, but satisfying curiosity as to
how something happened can make it more palatable!
