Improving the May 2019 timetable

Following our biggest timetable revamp in a decade, we’ve been closely monitoring the service to see how it’s bedding in.

The good news is that since the changes in May, over 100,000 extra journeys are being made across the London Northwestern Railway network each week, thanks to better links, more frequent trains and additional carriages.

However, when you make over 2,500 alterations to a timetable, it’s inevitable that some things don’t quite go to plan. That’s why we’ve been listening to your feedback to understand what you think is going well, and where we need a rethink.

Making changes can be a complex process, not least because our timetable has to fit in with other train operators and meet a specification set out by the Department for Transport. That means some suggestions simply don’t work – certainly in the short term. But where there is a solution to a problem, we’re doing all we can to make the necessary adjustments as quickly as possible.

The tables below set out the issues you’ve raised, and what we’re doing to address them. If you think there’s something missing, please get in touch

From 8 July 2019

Train What we're doing Why we're doing it
0710 Northampton to Euston Adding 4 carriages Reduces overcrowding
0634 Watford Jct to Euston

Removing 4 carriages

To provide extra seats on busier service
0805 Tring to Euston

Removing 4 carriages

To provide extra seats on busier service
1650 Euston to Milton Keynes

Train will stop at Kings Langley instead of Apsley

Reduces gap in trains at Kings Langley (1654 from Euston still calls at Apsley)

From 15 July 2019

Train What we're doing Why we're doing it
1644 Watford Jct to Euston New service To provide extra rush hour seats
1743 Watford Jct to Euston

New service

To provide extra rush hour seats

From 22 July 2019

Train What we're doing Why we're doing it
1714 Birmingham to Euston Removing stops at Lea Hall and Marston Green Reduces overcrowding – there is a train at 1717 (3 minutes later) calling at these stations.

If you want to get in touch about an issue not listed above, please click here