Considering they're still struggling to run 50% of the weekend service, their customer service is shocking. You'd think with one train per hour, they'd try to help people given this sounds like their cock up or break down. The quality of answers on Twitter has also fallen off a cliff, presumably because they're not party to any useful information so people may as well look at the National Rail Enquiries app.I've actually been avoiding using the Arlesey-Kings Cross trains during the weekend because the service frequency/reliability is still so poor, but on Sunday had no alternative so had to give it a go. The 1023 got cancelled, so I had low expectations about the 1123, given that it would have two hours' worth of passengers inside. Shouldn't have: the carriage had approximately 10 people in it. This is a service that last year used to be so incredibly jammed full that traveling was actually very unpleasant. It's incredible how big the fall-off of people using it has been. Even after Stevenage it was only about 25% full.
Coming back was the usual sort of stuff: Missed the hourly Arlesey train through my own fault, so no complaints there, got on one going to Letchworth since I'd rather wait at Hitchin in (comparative) fresh air for a connection than Kings Cross, then five minutes after it's supposed to have left the driver says the (700) train's broken and we all need to get off, but one going to Cambridge which was leaving from platform 11 (the Letchworth train was on platform 10) was going to have extra stops added to it. Then two minutes before the Cambridge train was supposed to leave, even though the platform was still empty, everyone got told it was actually leaving from platform 7, so cue everyone running back down the platform, through the barriers, and across the entire concourse to the other side of the station. I didn't bother, and the train disappeared from the departures board bang on time, so don't know if it waited for anyone or just drove off empty.
Considering they're still struggling to run 50% of the weekend service, their customer service is shocking. You'd think with one train per hour, they'd try to help people given this sounds like their cock up or break down. The quality of answers on Twitter has also fallen off a cliff, presumably because they're not party to any useful information so people may as well look at the National Rail Enquiries app.
Yesterday there was a stop order put on a fast train because the Cambridge stopper was likely to be cancelled (no driver). Then a driver was found so if ran some 40 minutes late and the 1Cxx service ran as booked.
I’ve just noticed on RTT that a service from St Albans to Sutton is cancelled “due to lineside vegetation” which conjures up images of triffids to me. Or possibly something less sinister!
Not a good start to the week:
07:10
07:32
07:47
All cancelled from Stevenage this morning.
They could indeed.They could stop running weekend services altogether & DfT wouldn't notice. Wouldn't be amazed if they actually do that on GN before too long .
I haven't been on the Sutton loop for a long time but it would appear in many locations around the network, vegetation has been "allowed" to flourish beyond belief. Presume, there is no strategy to keep it down or under control?
There was a pay dispute (triggered from on high at First) that triggered one full "BBQ Sunday" and RDW refusal until First came to their senses.They could indeed.
Didn't FCC do this at one point in the midst of a dispute with the drivers, who refused to work overtime or rest days?
There was a pay dispute (triggered from on high at First) that triggered one full "BBQ Sunday" and RDW refusal until First came to their senses.
I've actually been avoiding using the Arlesey-Kings Cross trains during the weekend because the service frequency/reliability is still so poor, but on Sunday had no alternative so had to give it a go. The 1023 got cancelled, so I had low expectations about the 1123, given that it would have two hours' worth of passengers inside. Shouldn't have: the carriage had approximately 10 people in it. This is a service that last year used to be so incredibly jammed full that traveling was actually very unpleasant. It's incredible how big the fall-off of people using it has been. Even after Stevenage it was only about 25% full.
A specific example, but take the train I used to get most days before the timetable change - the 0949 Ely to Cambridge - this had within-5-minutes arrival at Cambridge at about 97% before May according to RecentTrainTimes. I know this is pretty accurate as otherwise I missed my bus connection.
Now it is at 0948, and this week's record for arrivals at Cambridge : 7 late, on-time, 10 late, 8 late, cancelled - ie. 20% reliability, quite a bit down from high nineties pre-May! So I can no longer rely on this train and have to get the preceding GA ex-Norwich instead. Partly this is due to the fact it starts back from Kings Lynn now and has a nasty tight squeeze through Ely North junction - but that's not my problem, the timetable should be taking that into account. Now I have to get to the station earlier to get to work on time as this train has gone from very reliable to very unreliable.
I should note that the performance of this train has actually drastically improved - last week it was on-time to within a minute every day. A couple of times it looked like the signaller had the sense to send things through Ely North out-of-order when there were slight delays, which definitely helped, but however it worked out this is a big improvement. Let no-one say I'm not fair to GN on the rare occasion that I feel I ought to be![]()
Us harden commuters now know operational incident - means something within GTRs control but they don’t want to admit liability.
Would a SPAR due to a signal reverting to danger be 'withing GTRs control ?
'operational incident' is very much an admission of liability. It's used to be generic and avoid technicalities that the hoi pollio don't need to understand. It's a very umbrella term to cover the plethora of incidents that occur regularly on the railway. My incident this afternoon was not mentioned specifically on the radio on my trip home. They simply announced it as "trains being unable to call at XX and up to 15 minute delays" I don't think anyone really needs the specific minutiae of every single incident.
I've actually been avoiding using the Arlesey-Kings Cross trains during the weekend because the service frequency/reliability is still so poor, but on Sunday had no alternative so had to give it a go. The 1023 got cancelled, so I had low expectations about the 1123, given that it would have two hours' worth of passengers inside. Shouldn't have: the carriage had approximately 10 people in it. This is a service that last year used to be so incredibly jammed full that traveling was actually very unpleasant. It's incredible how big the fall-off of people using it has been. Even after Stevenage it was only about 25% full.
I would agree there is a lot of buck passing with TOC/NR. Personally I wish it would stop but I think it came about because passenger perception is all based on the TOC being at fault and I think that TOCs finally snapped. The blame game winds me up at the best of times. There is a flip side of the coin where it could be seen as being transparent. Eveyone must own up to what they cause and who's fault it is. NR seem to hide behind the TOCs just as much as the TOCs pass the blame back to them.
I am still at odds where it is 'within GTRs control' There is no intent to have an operational incident and it covers many things but I cannot, for the life of me, see it as 'controllable' in any way. **** happens and how it gets dealt with that is important. What happened to me today effectively shut down a major platform on a major route. The impact will be felt for a couple of days if NR don't pull their finger out and felt by two TOCs and a metric ton of services. Nobody is to blame for it but there will be consequences. I don't think for a second that its within anybodys control.
But you have to admit it was still appalling customer service. This driver didn’t as if by magic appear to run the service. It was nearly 50 Down. I was on it.