Anyone any idea what happened here. Look initially like a turnaround via the Rhubarb curve, but the time for Lawrence Hill (16.32) was as near as makes no difference the time passengers for stations for Warminster were being turfed off at Temple Meads and told to get the 16.45 so the train definitely wasn’t at Lawrence Hill.
-
Our new ticketing site is now live! Using either this or the original site (both 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!
Weird timings 1F23 Cardiff - Portsmouth
- Thread starter The exile
- 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
father_jack
Established Member
- Joined
- 26 Jan 2010
- Messages
- 1,557
So it was a turn via Lawrence Hill then - but that doesn't explain that 16.32 timing at Lawrence Hill - the train was most definitely at Temple Meads at 16.32. Fully appreciate the need for working aircon for the driver - but makes being turfed off the 16.22, where the saloon aircon was working beautifully, on to the 16.45 (why suddenly 16.45 not 16.47?) Warminster service, where it wasn't, all the more galling!
My understanding is that RTT, when computing a passing time, will average the arrival and departure times that it computes on the basis of train describer berth steps.
So what I think happened is, the train went into Bristol Temple Meads, passing Lawrence Hill at around 16:16 or so. It then ran back out as far as Lawrence Hill, reversing there at around 16:48-16:50 or so, then went round the Rhubarb Loop. The average of 16:16 and 16:48 gives the passing time of 16:32.
Ah right - weird, but thanks for the explanation!
Yes, it's very weird, and it's specific to how RTT handles passing times. Every other industry source would simply take the departure time as the passing time.
But I've seen it in disruption many times where a train will stop out of course at a station for a long time - at the location before it will be on time, at the location after it will be +30, but if it's not booked to call at the station, RTT will show the train as having passed the station +15, even if it actually stopped in the platform for half an hour.
That's not so unreasonable on its own, I guess, but this is a particularly weird edge case where that's gone badly wrong!
- Status