Thameslink
Thameslink recorded 44,130 services from 6 Aug 2026 to 23 Sept 2026 and cancelled 1,481 of them. Of those whose arrival was captured, 82% were within five minutes — below the national figure for the same days.
Over 49 archived days that is 901 services a day, 3.7% of the national timetable. Of 21,495 recorded arrivals, 17,712 were within five minutes and 259 were more than half an hour down.
Its week is strongly peaked: 986 services on Wednesday, 23 September 2026 against 589 on Sunday, 13 September 2026, a swing of 1.7 times.
The average delay at destination was 2.5 minutes. The worst single arrival recorded was 9h 14m behind schedule, Sutton (London) to Bedford on Wednesday, 2 September 2026.
The day-to-day spread is wide — 30 points between its best day, Monday, 31 August 2026 at 93%, and its worst, Wednesday, 26 August 2026 at 63%.
1,481 services were cancelled, 3.4% of everything booked — above the 2.4% the network cancelled over the same dates. The worst single day was Sunday, 16 August 2026, at 9% of that day's timetable.
Counting those cancellations as failures, the way the industry's own measure does, takes the on-time share from 82% of recorded arrivals to 77% of everything booked whose outcome is known — 5.3 points.
Ranked on on-time share of recorded arrivals against the 30 operators with enough of them to compare, Thameslink comes 19th.
Thameslink in numbers
| Archived days covered | 49 | 6 Aug 2026 to 23 Sept 2026 |
|---|---|---|
| Passenger trains recorded | 44,130 | |
| Share of the national timetable | 3.7% | of 1,203,226 over the same dates |
| Cancelled | 1,481 | 3.4% · network 2.4% |
| Arrival time recorded | 21,495 | 50.4% of those that ran |
| …arrived within 5 minutes | 17,712 | 82.4% |
| …arrived 5 to 30 minutes late | 3,524 | 16.4% |
| …arrived more than 30 minutes late | 259 | 1.2% |
| Average delay at destination | 2.5 min | |
| On time, counting cancellations | 77.1% | of the 22,976 booked services whose outcome is known · network 84% |
| Network, same dates | 87% | on time, against this operator's 82% |
Every percentage among the bands is of the 21,495 services whose arrival reached the archive, not of all 44,130, and the bands are exclusive. 21,154 ran without an arrival being recorded, and nothing is claimed about those. The row counting cancellations is those same 17,712 on-time arrivals over a denominator that also holds the 1,481 trains that did not run at all. Delay is judged at the destination, a stricter test than the industry's own measure and not comparable with it. The on-time share and the average delay answer different questions.
Day by day
49 archived days, 6 Aug 2026 to 23 Sept 2026, widest bar the busiest, filled to the share that arrived within five minutes. The same days across every operator.
In the daily longest-delay league
Thameslink appears 19 times across 49 archived days, on 6 separate dates in the ten shown. These are appearances in the daily league, not this operator's own worst delays.
| Date | Service | Late by |
|---|---|---|
| 2 Sept 2026 | Sutton (London) to Bedford 22:49 · 9O96 | 9h 14m |
| 4 Sept 2026 | Peterborough to Horsham 07:23 · 9J13 | 3h 35m |
| 9 Sept 2026 | Bedford to Brighton 09:16 · 9T21 | 2h 37m |
| 8 Sept 2026 | Brighton to Cambridge 09:44 · 9S18 | 2h 30m |
| 9 Sept 2026 | Peterborough to Horsham 08:53 · 9J19 | 2h 25m |
| 26 Aug 2026 | Peterborough to Horsham 14:23 · 9J41 | 2h 10m |
| 26 Aug 2026 | Horsham to Peterborough 09:55 · 9J26 | 2h 07m |
| 15 Aug 2026 | Bedford to Three Bridges 09:32 · 9R15 | 2h 07m |
| 15 Aug 2026 | Bedford to Brighton 10:16 · 9T25 | 2h 00m |
| 2 Sept 2026 | Sutton (London) to Bedford 23:18 · 9V96 | 1h 51m |
Recorded live from the Darwin and TRUST feeds on each of the 49 days above,
and aggregated here. TL is this operator's ATOC code. How these figures are measured · All operators · Sources and licences