Would it not be useful to choose a point where the weather is the same. Some of the delays might be due to that.I hope by that you mean compare it to the same period from last year rather than some random point in this year.
Would it not be useful to choose a point where the weather is the same. Some of the delays might be due to that.I hope by that you mean compare it to the same period from last year rather than some random point in this year.
Right now, the Thameslink website is showing "Major Disruption" on the front page for the Brighton to Bedford line, but when you click to the details page, it's showing everything is fine. National Rail and Thameslink twitter are not reporting problems, so it looks like another fault with their website...
They have stopped using the Journeycheck information page for some reason, and in a reply to my tweet said that there is no current plan to use it. Southern also don't use it, instead preferring to clutter up their Twitter feed with individual train alterations.
Why do you say that? I actually find it very useful. However I'm happy for the counter argument against it to be put.I won't repeat my views on JourneyCheck here suffice to say that the fewer TOCs that use it the better IMHO
Right now, the Thameslink website is showing "Major Disruption" on the front page for the Brighton to Bedford line, but when you click to the details page, it's showing everything is fine. National Rail and Thameslink twitter are not reporting problems, so it looks like another fault with their website...
Right now, the Thameslink website is showing "Major Disruption" on the front page for the Brighton to Bedford line, but when you click to the details page, it's showing everything is fine. National Rail and Thameslink twitter are not reporting problems, so it looks like another fault with their website...
You have to wonder whether this is now the most regular disruption in all London. For many years the most common one was the Bakerloo Line Not Running North Of Queens Park, this appeared to be reported countless times for equally countless reasons (I once saw graffiti chalked up that it was because of bush fires in Australia..... with Thameslink services from Bedford to Brighton diverted via Elephant and Castle instead of London Bridge .....
), but I think that Thameslink Not Serving London Bridge now has it beat. Of course, before long it won't be doing so for around three years.I suspect GTR is saving money by not having to have a dynamic website that updates with real time information, and has hedged its bets that there will be major disruption on the Thameslink route more often than not.![]()
A signalling problem at London Bridge is delaying trains by up to 20 minutes between London Bridge and New Cross Gate / Tulse Hill.
Thameslink services from London Blackfriars towards East Croydon will not call at London Bridge.
There is no firm estimate yet of how long disruption will last but it is likely to continue until at least 18:00
In their infinite wisdom they also cancelled the first offpeak service to Bedford. Good times were had by all.
I get the impression Govia doesn't know how to run a bath let alone trains. Let's not forget they run London Midland...
In their infinite wisdom they also cancelled the first offpeak service to Bedford. Good times were had by all.
I get the impression Govia doesn't know how to run a bath let alone trains. Let's not forget they run London Midland...
While I deeply hate to admit it, you could argue that Thameslink is one of the harder franchises to run because of the core, the dual power, London bridge, a diverse set of routes, and sharing lines with several other operators. [Before you even add the passenger volumes and two airports]
Well, mostly the core![]()
I'm still of the view that Govia probably regretted winning it after the awful first couple of weeks (am summoning up energy to file my *two* delay repay claims for that period tonight).
I agree that the thought of GN trains piling into the core fills me with dread too; it's really difficult to see how anything will recover if there is an repeat of something like the overhead wires coming down at City (again).
Less worried about the spread - Blackfriars is pretty spacious now; City Thameslink isn't the best - but as it's not connected to the Tube it doesn't matter quite so much; Farringdon is pretty good down the southern/new part of the platforms now (it's just people aren't trained into standing there!); and St. P is fine
It's quite clear to see that Farringdon's extension has been built with passengers heading south in mind. The majority of trains are 4/8 carriages as you know and thus a considerable amount of the train will be in the new part.
Not true for the northbound platform. The majority of trains will not even have a carriage in the new part. When 12 carriages run more regularly then yes. Now most services are relegated to the original part.
My first encounter with the new operator - queues at the ticket office (when there usually aren't) and no information on the display screens or platform indicators. The train was on time though.
Beats mine with one working ticker machine and one window on a Monday morning. Train was far from on time.
asylumxl - which date/journey?
It was Monday of last week. The delay on the train isn't really their fault (person hit by train).
Ticket machine and ticket window on the other hand... Was Luton station. I arrived 0705 and queued 25 mins for a ticket from the one working machine. Doesn't that violate their Passenger Charter?
The route has obviously had some stuff outside of their control. The biggest difference to me so far is that the number of train faults seems to have increased. Secondary is a decrease in comms.
Suspect passenger charter is aspirational
You may have been on the same train as me. My train left Leagrave at ?7.27 (after missing the 7.18 because I could get a ticket in time). Neither TVM were working and the credit card machine in the booking office wasn't either - I ended up paying cash. (He said Luton had just reported a problem with machines too)
We were delayed - like everyone else - by the person hit by train. But the train I was on had a train fault as well, so was taken out of service at Kentish Town - don't think it was due to call there (whereas I wanted Blackfriars). Other trains that morning probably were under 30 mins; because this one was had a fault as well it was definitely longer. Will try to remember to update you when my claim is processed! Perhaps mine is more likely because there is less choice from Leagrave than from Luton.
And to think people used to moan about First Capital Connect... In reality it seems they did a quite efficient job of running the railway compared to GoVia's efforts.!!
I assume you've replied saying words to the effect of "no, I couldn't, it didn't stop at Kentish Town"Yes, we must have been on the same train. I intended to get an earlier train but was unable to do so. The Kent House service seemed to be the only service running.
The ticket machines had issues the next few days too, with one being stuck in a boot cycle (showing its ancient BIOS screen) for several days. Seems it wasn't a priority for GTR to fix it.
I look forward to hearing how they deal with your delay claim, since they rejected mine claiming I could have got to London in x time had I got y train that never stopped at Kentish Town...