On 10 June, 16:29, Mizter T wrote:
On Jun 10, 1:57*pm, John B wrote:

So what's the latest (alleged) fault that's required the 377/5s and
378s to be taken out of service all about, then...?

FWIW, JourneyCheck for FCC appears to list all the short formed
services on the Thameslink route:
http://www.jcheck.com/firstcapitalconnect

This is exceptionally bad timing, as the core Thameslink route will no
doubt be under considerable strain today with bods attempting to route
around the Tube strike.

For strike and other reasons, I've used Thameslink through the middle
more than usual lately.

My impression is the same as many people's was back in the late 1980s:
incredibly slow, trains waiting minutes at every station and crawling
between stations (while keeping to time).

Also a huge delay and palaver in terminating trains at City Thameslink
(two staff shutting one set of doors at a time while a train stands
for several minutes).

I can't easily reconcile this, slow, grinding route with a service so
fast and frequent that no existing trains will be able to accelerate
fast enough to keep up. When and how is the seismic shift going to
happen?