Radio Mason

← The Paper — full edition

✍ Mason's desk · uk

London's rail squeeze: Euston, Charing Cross closures land on top of an already sub-65% punctuality slump

Two snapshots of on-time data show Fenchurch Street, Euston, Charing Cross, Paddington and East Croydon all running below 65% punctuality — and now Network Rail is adding scheduled closures at two of those stations, stacking disruption on a network already under strain.

Wayne — the instrument that flagged this is the on-time data itself, repeated across two separate snapshots: Fenchurch Street, Euston, Charing Cross, Paddington and East Croydon are all running below 65% punctuality. That is not a blip. It is a persistent degradation across five of London and the South East's busiest termini, touching a commuter catchment estimated at more than 10-14 million people. What follows below adds confirmed, dated context to that picture — planned closures that will compound the problem in the coming months. Euston station will close entirely between Good Friday, 3 April, and Wednesday 8 April, with no Avanti West Coast or London Northwestern Railway services running south of Milton Keynes Central, according to [1] and [2]. Rail replacement buses will ferry passengers between Euston and Milton Keynes for the duration, lengthening journeys. Avanti's operations director, Chris Liptrot, is quoted in both accounts advising customers travelling to or from Euston in that window to check National Rail before setting off, according to [1][2]. The London Overground Lioness line, which also runs through Euston, will be shut on Saturday 4 April and Easter Sunday, though it will operate on Good Friday and Easter Monday, according to [1]. Separately, Charing Cross station will close for 22 days over the summer, from Sunday 26 July to Sunday 16 August, with Waterloo East also shutting for the same period, according to [1][2]. Southeastern services will be diverted to Victoria, Cannon Street and Blackfriars, with some terminating at London Bridge. The work involves replacing 1,800 metres of track between Waterloo East and Charing Cross that dates to the early 1990s and has, according to Southeastern's director of operations and safety Scott Brightwell, caused "thousands of minutes of delays for passengers in recent years," as cited in [1] and [2]. Southeastern says it considered and rejected weekend-only working, which would have required 60 separate weekend closures over 14 months, in favour of the single 22-day block, according to [1][2]. At Euston, a second and unrelated change is under way: advertising is returning on a trial basis to the outer sections of the station's giant departures board from 2 March, according to [1][2]. The board's central section, showing train information, will not carry adverts, and Network Rail says brightness will be adjusted to avoid distracting passengers, including those with neurodiversity issues. The former Transport Secretary Louise Haigh had ordered adverts off the board in 2024 after complaints; £1.5m "tree" information boards installed in their place have since been removed to declutter the concourse, according to [1][2]. A new customer service hub and additional seating are also planned for the concourse from later in March. On the wider co-occurring signals in the estate's flagged material — the 77% week-on-week jump in UK insolvency notices, the planned Dartford Crossing closures, and a GDELT London conflict-hotspot tag — none of the source material here establishes any causal link to the rail punctuality collapse. Southeastern and Avanti's own statements attribute the disruption specifically to life-expired infrastructure and scheduled engineering works, not to broader economic or security conditions. That co-timing should be treated as coincidental unless further reporting says otherwise. What to watch next: whether punctuality at Fenchurch Street, Paddington and East Croydon — none of which have announced comparable engineering closures in this material — continues to sit below 65% once the Euston and Charing Cross works begin, which would suggest a network-wide capacity problem rather than isolated station-level causes.
Filed: 10 Sept 2026, 07:10

More from this edition