Deepgreen
Established Member
Does anyone have any idea what has happened here? Other trains were not delayed, according to RTT
.
.
-
Our booking engine at tickets.railforums.co.uk (powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!
Wildly-Varying Real Time Reports
- Thread starter Deepgreen
- Start date
- Status
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R
RailUK Forums
From interpreting the data it looks like it either reversed on route (thus overriding any previous data held about when it goes over certain points) or there was a mix up with the headcode somewhere down the line so another train inadvertently changed that train's progress
Deepgreen
Established Member
It is shown as arriving at Woking 3L. It could not have reversed where the timings go adrift without delaying other trains, which, as I mentioned, are shown as being unaffected. I don't understand the headcode change concept - are you saying it assumed another train's identity and then relinquished it again? In any case, no other trains on the line go to Woking.
But it wouldn't delay other trains as it didn't - that's the only plausible explanation for it. I'm not familiar with the area, but there's possibly some sidings somewhere.
In terms of taking another headcode, it was theoretical as again, I dont know the area and its workings, but up where I live it happened to this train:
http://www.realtimetrains.co.uk/train/Y54572/2019/02/21/advanced
Got mixed up with:
http://www.realtimetrains.co.uk/train/Y54524/2019/02/21/advanced
2S13 and 2S31 got mixed up.
Spartacus
Established Member
- Joined
- 25 Aug 2009
- Messages
- 2,926
Seems it got mixed up with this one
http://www.realtimetrains.co.uk/train/O86727/2019/02/27/advanced
Could be that with it coming out early the headcode might not have been changed, or as it's a VSTP the schedule might not even have been in for the return when it set off.
http://www.realtimetrains.co.uk/train/O86727/2019/02/27/advanced
Could be that with it coming out early the headcode might not have been changed, or as it's a VSTP the schedule might not even have been in for the return when it set off.
Deepgreen
Established Member
No sidings at all between Reigate and Guildford, and all crossovers are locked and require ground frame operation, except at Shalford, where any reversal would certainly have delayed other trains. Thanks anyway. Another RTT question arises today - what would constitute a "mishap" in this report (and one other train had the same description)? I note also that this stopper is described as having first and standard seating - it doesn't - 1st was abolished in 2017 on the stoppers.
A 'mishap' is just how RTT reports that cancellation code - it could be any number of things.
Spartacus
Established Member
- Joined
- 25 Aug 2009
- Messages
- 2,926
MY's the code for coupler fault.
That ties in with some reports I’ve seen from this morning, 5O54 came off the depot late after 166110 had coupler issues and necessitated some last minute fitters attention (resulted in a 55 late start). This resulted in some full & part cancellations to North Downs services.
Deepgreen
Established Member
Many thanks for that.
This would appear to be one of those rare occasions where RTT screws up. No odd times seen on http://charlwoodhouse.co.uk/rail/liverail/train/15707962/27/2
This is linked to a different method of tracking trains. A lot of open data sites use Darwin or just TRUST. RTT uses TD based reporting as its primary source and this can happen if something goes weird with tracking the train through a particular route.
- Status