The Clocks on the TVM at Derby have been between 4 and 5 minutes fast for a few days now. It could be much longer, i first noticed Friday morning when i purchased a ticket at 1048 for the very delayed 0952 to Matlock, or given it was likely to be (and indeed was) cancelled at Derby the delayed 1052.
I was told they'll all be cancelled there and it will be RRB, but as i purchased after the announcement i cannot get a refund. It was issued at 1053. It was still 1052!
Sure enough the clocks are fast!
As it happens the 1052 ran 20L and carried on to Matlock, however all passengers for the 0952 AND 1052 were told to get on the RRB. So those who waited for the train that did actually run got there considerably faster than the RRB.
I mentioned it to more station staff, i mentioned it on Twitter, they said they'd look into it, they hadn't when i bought a Derby to Nottingham ticket later that day, like a fool forgetting the Evening Peak on that ticket, and having to get a 50p excess, (i know i went wrong in the first place i was in a rush), they still hadn't by the time i bought a Derby to Leicester (ish) Ticket on Sunday.
How can the clocks be wrong? Surely it picks its time up from a central server which has to be correct.
(on another note, i'm glad i bought the wrong ticket to Nottingham and had to get an excess causing me to miss the Nottingham train and wait half an hour because it meant i got to see 37800 start up in a huge cloud of smoke at the end of the platforms)
Rob
I was told they'll all be cancelled there and it will be RRB, but as i purchased after the announcement i cannot get a refund. It was issued at 1053. It was still 1052!
Sure enough the clocks are fast!
As it happens the 1052 ran 20L and carried on to Matlock, however all passengers for the 0952 AND 1052 were told to get on the RRB. So those who waited for the train that did actually run got there considerably faster than the RRB.
I mentioned it to more station staff, i mentioned it on Twitter, they said they'd look into it, they hadn't when i bought a Derby to Nottingham ticket later that day, like a fool forgetting the Evening Peak on that ticket, and having to get a 50p excess, (i know i went wrong in the first place i was in a rush), they still hadn't by the time i bought a Derby to Leicester (ish) Ticket on Sunday.
How can the clocks be wrong? Surely it picks its time up from a central server which has to be correct.
(on another note, i'm glad i bought the wrong ticket to Nottingham and had to get an excess causing me to miss the Nottingham train and wait half an hour because it meant i got to see 37800 start up in a huge cloud of smoke at the end of the platforms)
Rob