Entries Tagged 'Thameslink Performance statistics' ↓
February 14th, 2012 — Thameslink Performance statistics
According to the latest performance statistics published by our friends over at First Capital Connect last week, 87.5% of trains on the Thameslink route between 8 January and 4 February were less than 5 minutes late at the final destination. This is, once again, below their target rate of 90.32%. Furthermore, 3.1% of trains across the FCC network were cancelled in the period.
Excuse of the month: Loss of signalling equipment power at West Hampstead.
You may have noticed over on twitter that I Continue reading →
January 19th, 2012 — Thameslink Performance statistics
Between 11th December and the 7th January 89.0% of Thameslink services ran with less than a 5 minute delay at their final destination, and so considered ‘on time’ by First Capital Connect. This is still below their previously published target of 90.32%.
3.5% of services were cancelled for part or all of their journey Continue reading →
January 12th, 2011 — Thameslink Performance statistics
It won’t come as much of a surprise – but only 73.7% of planned thameslink train services were less than 5 minutes late at their final destination between 12 December – 8 January. This is even worse than last period when only 79.3% of trains were ‘on time’. This is also the worst performance in the last 12 months. Figures can be downloaded here.

FCC invest in a new de-icer...
When combined with the Great Northern route, First Capital Connect managed to get 73.0% of trains to their destination less than 5 minutes late.This suggest the Great Northern Route performed slightly worse than the Thameslink route in this period. Furthermore a whopping 14.1% of trains were cancelled across the entire network.
This month, FCC had the following excuses for their terrible performance:
Adverse weather conditions Continue reading →
December 28th, 2010 — Thameslink Performance statistics
The latest statistics (pdf) published by First Capital Connect shows that only 79.3% of planned thameslink train services were less than 5 minutes late at their final destination. When combined with the Great Northern route, First Capital Connect managed to get 83.4% of trains to their destination less than 5 minutes late. Furthermore 6.4% of trains were cancelled across the entire network.
FCC gave the following excuses for the poor performance.
Defective train near Welwyn Garden City Continue reading →
August 11th, 2010 — Thameslink Performance statistics
Today, IhateThameslink launch their campaign to pressure First Capital Connect to release meaningful and transparent statistics.
Please click here to sign the petition, or to read why we have started this campaign, please read out campaign page.
In coming months we will be able to compare the official FCC performance statistics with more meaningful statistics thanks to our guest blogger Stuart who has created a superb application that records data direct from the National Rail database. The results should be interesting!
August 5th, 2010 — Thameslink Performance statistics
That’s right folks. In the period running from 27 June to 24 July FCC only managed to run 89.5% (or 88.1% – see screw up 1 below) of train less than five minutes late at their destination on the Thameslink route. This is just marginally better (or worse) than the 88.2% in the May-June period.
Screw up 1: On the performance home page they state the Thameslink performance is 89.5% however on the report (PDF) it says it is 88.1% and that the FCC combined (Thameslink + Great Northern) is 89.5%.
Screw up 2: First Capital Connect have published their latest report but in true FCC style their performance home page is out of date and still has comments and excuses relating to the last report! Continue reading →
July 21st, 2010 — Thameslink Performance statistics
First Capital Connect recently published their performance stats for the period running between 30 May to 26 June. Once again, performance on the Thameslink route was unacceptable with just 88.2% of planned train service running less than 5 minutes late at their final destination. 3.2% of planned services (Thameslink + Great Northern routes combined) were also cancelled for part or all of their journey.
FCC also disclose that their target is for 90.32% of planned Thameslink services to run less than 5 minutes late at their final destination. Therefore, in the May – June period FCC underperformed even by their own standards! Continue reading →
February 27th, 2010 — Thameslink Performance statistics
First Capital Connect have published their Thameslink service statistics for the Jan/Feb period.
Following the abysmal service experienced over the Dec/Jan period (when only 62.8% of trains reached their final destination less than five minutes late) First capital Connect continue to disappoint with only 76.8% of training running ‘on time’ in Jan/Feb.
It was also revealed that 8.3% of trains were cancelled for part or all of their journey across the whole FCC network. I Hate Thameslink has previously pointed out that FCC do not reveal how many cancellations occurred on the Thameslink route alone which we feel they should.
January 21st, 2010 — Thameslink Performance statistics
First Capital Connect recently revealed their results for ‘period 10′ which covers 13th December 2009 to 9th January 2010. The FCC press release reveals that in this period just 62.8% of trains ran with less than a five minute delay on the Thameslink route and Continue reading →
December 22nd, 2009 — Thameslink Performance statistics
It appears that FCC have hit an all time low by providing an abysmal level of service today on the Thameslink route. I was lucky enough to take today off as annual leave, but have been able to monitor the chaos via twitter. It appears FCC have not only delayed customers for (literally) hours but have endangered lives.
It looks like a train broke down which caused unimaginable chaos. This combined with the bad weather and the ongoing dispute with drivers was just just too much for FCC to cope with.
A selection of tweets are posted below. Shocking. Continue reading →