Northern’s low threshold for skipping stops?

[Falcon1200]

Was the singling of these sections (and also part of the Milngavie branch?) enacted around the time of the establishment of the infamous "single-lead" junctions which sadly brought the suburbs of Bellgrove and Newton into unwanted prominence following collisions?

The Balloch branch was singled in 1973, IIRC the redundant equipment was used to electrify the Lanark branch! Westerton/Milngavie was singled around 1990 as part of the North Clyde resignalling scheme (and I have never quite understood why as although a few miles of track were saved, additional points were required where there had been none before).

 

[Spamcan81]

Skipping stops due to delays is by no means unusual on Thameslink.

Correct. I’ve seen stop skipping for a delay as short as seven minutes.

 

[Horizon22]

It’s not unusual really anywhere that is a regional or metro operator. It’s simply one of the tools of service recovery.

 

[Falcon1200]

I’ve seen stop skipping for a delay as short as seven minutes.

Where trains converge on a route with a service every two (or less) minutes, even one just seven minutes late can cause havoc! And reactionary delay out of all proportion to the original problem.

 

[Andy Pacer]

EMR have started doing more skip-stopping, especially on Intercity services skipping many stations.

Really? Do you have any examples? As a frequent user I've never encountered this. In fact there's relatively few stops at all now since the timetable recast that sees most scheduled non stop between Kettering and London.

 

[tram21]

Really? Do you have any examples? As a frequent user I've never encountered this. In fact there's relatively few stops at all now since the timetable recast that sees most scheduled non stop between Kettering and London.

If a service is 30+ minutes late stopping Intercity services frequently skip stops between Nottingham and Leicester, and sometimes even Market Harborough and Kettering as well if its very late (stopping at Leicester, although once one ran non stop!)

The Nottingham to Leicester stopping services occasionally skip stops too to avoid blocking the busy Midland Mainline if late, most frequently Beeston and Attenborough.

 

[VT 390]

Really? Do you have any examples? As a frequent user I've never encountered this. In fact there's relatively few stops at all now since the timetable recast that sees most scheduled non stop between Kettering and London.

If a service is 30+ minutes late stopping Intercity services frequently skip stops between Nottingham and Leicester, and sometimes even Market Harborough and Kettering as well if its very late (stopping at Leicester, although once one ran non stop!)

The Nottingham to Leicester stopping services occasionally skip stops too to avoid blocking the busy Midland Mainline if late, most frequently Beeston and Attenborough.

I have been on a Sheffield service relatively recently which skipped Long Eaton, East Midlands Parkway and Loughborough.

 

[Andyh82]

An example of one today that I noticed, a Manchester to Leeds was running 40 minutes late, with the next service not far behind, so it ran fast from Sowerby Bridge to Leeds meaning the return journey could depart near enough on time

Realtime Trains | 1E66 1426 Chester to Leeds | 21/02/2026

Real-time train running information for 1E66 1426 departure from Chester to Leeds on 21/02/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

 

[D6130]

An example of one today that I noticed, a Manchester to Leeds was running 40 minutes late, with the next service not far behind, so it ran fast from Sowerby Bridge to Leeds meaning the return journey could depart near enough on time

Realtime Trains | 1E66 1426 Chester to Leeds | 21/02/2026

Real-time train running information for 1E66 1426 departure from Chester to Leeds on 21/02/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Running non-stop via Elland saves a lot of time.

 

[Craig1122]

I've known SWR to skip stop up services on the Windsor lines when the fast lines are closed surely control should know that's the case?

Also common to run fast from Twickenham to Waterloo but be routed behind a stopping train. There's usually a major churn of passengers at Richmond who are all inconvenienced just for the train to crawl to Barnes where it becomes 4 track.

 

[VT 390]

I've known SWR to skip stop up services on the Windsor lines when the fast lines are closed surely control should know that's the case?

Also common to run fast from Twickenham to Waterloo but be routed behind a stopping train. There's usually a major churn of passengers at Richmond who are all inconvenienced just for the train to crawl to Barnes where it becomes 4 track.

I have been on a few SWR services that have run fast skipping stations on the Windsor lines but have never been put behind a slower service, I know it does happen but have never personally experienced it.

Last year I was even on a service (booked all stations except Queenstown Road) that was changed to non stop, and is was actually non stop, Twickenham to London Waterloo. The service made up around 13 minutes.

 

[BG2024]

I had a ridiculous one today.

The 1632 Manchester Airport - Liverpool Lime Street service ran fast due to "overcrowding because of a football match".

First problem: the football match (Everton v Man Utd) was irrelevant. The service was overcrowded because Northern short-formed, sending a 3-car to handle a busy commuter route. Once we'd cleared the commuter stations of Eccles, Patricroft and Newton-le-Willows, it wasn't overcrowded at all.

Second problem: it didn't run fast. Having kicked loads of us off at Huyton so it could run fast to Lime Street, it then parked up at Roby to let a TPE overtake it. For those who don't know, Huyton and Roby are so close that you can see one from the other, meaning all the passengers for Roby got to stand in the rain watching the train they'd just been forced to leave stop-but-not-stop at their intended destination.

 

[D6130]

I had a ridiculous one today.

The 1632 Manchester Airport - Liverpool Lime Street service ran fast due to "overcrowding because of a football match".

First problem: the football match (Everton v Man Utd) was irrelevant. The service was overcrowded because Northern short-formed, sending a 3-car to handle a busy commuter route. Once we'd cleared the commuter stations of Eccles, Patricroft and Newton-le-Willows, it wasn't overcrowded at all.

Second problem: it didn't run fast. Having kicked loads of us off at Huyton so it could run fast to Lime Street, it then parked up at Roby to let a TPE overtake it. For those who don't know, Huyton and Roby are so close that you can see one from the other, meaning all the passengers for Roby got to stand in the rain watching the train they'd just been forced to leave stop-but-not-stop at their intended destination.

It may well be that the other unit was purloined to strengthen a service from Liverpool because of the expected match day crowds.

 

[Kite159]

...

I had a ridiculous one today.

The 1632 Manchester Airport - Liverpool Lime Street service ran fast due to "overcrowding because of a football match".

First problem: the football match (Everton v Man Utd) was irrelevant. The service was overcrowded because Northern short-formed, sending a 3-car to handle a busy commuter route. Once we'd cleared the commuter stations of Eccles, Patricroft and Newton-le-Willows, it wasn't overcrowded at all.

Second problem: it didn't run fast. Having kicked loads of us off at Huyton so it could run fast to Lime Street, it then parked up at Roby to let a TPE overtake it. For those who don't know, Huyton and Roby are so close that you can see one from the other, meaning all the passengers for Roby got to stand in the rain watching the train they'd just been forced to leave stop-but-not-stop at their intended destination.

At least Northern didn't do their usual trick on the Manchester Airport - Liverpool via Chat Moss line in having the delayed train call all stops from Manchester Airport to Piccadilly (delaying other trains such as the Blackpool North & TPE Scottish service) to have it run nonstop from Oxford Road to Lime Street skipping the hourly served stations along the route.

 

[VT 390]

I had a ridiculous one today.

The 1632 Manchester Airport - Liverpool Lime Street service ran fast due to "overcrowding because of a football match".

First problem: the football match (Everton v Man Utd) was irrelevant. The service was overcrowded because Northern short-formed, sending a 3-car to handle a busy commuter route. Once we'd cleared the commuter stations of Eccles, Patricroft and Newton-le-Willows, it wasn't overcrowded at all.

Second problem: it didn't run fast. Having kicked loads of us off at Huyton so it could run fast to Lime Street, it then parked up at Roby to let a TPE overtake it. For those who don't know, Huyton and Roby are so close that you can see one from the other, meaning all the passengers for Roby got to stand in the rain watching the train they'd just been forced to leave stop-but-not-stop at their intended destination.

Whatever caused the overcrowding (football or short form), is overcrowding really the reason for skipping some stations as you have mentioned after Newton-le-Willows it was not overcrowded?
The original 6 minute at Ordsall Lane Jn would have been to let the late 1K24 (Hull to Liverpool TransPennine service) through first.

As there was an alternative service only about 5 minutes later at Huyton for all stations to Liverpool (2C24) I don't think its entirely unreasonable to run fast to Liverpool to get it out the way as otherwise your service would have either started to delay stopping services behind (had it waited for the fast TransPennine 9M15) or delayed the fast 9M15.

 

[BG2024]

It may well be that the other unit was purloined to strengthen a service from Liverpool because of the expected match day crowds.

It ran 6-car for the first three services of the day, but half of it was sent back to Allerton Depot shortly after 10am due to a technical fault

Whatever caused the overcrowding (football or short form), is overcrowding really the reason for skipping some stations as you have mentioned after Newton-le-Willows it was not overcrowded?

That's what the guard said, and what was shown on JourneyCheck. I suspect they paniced that they'd pick up more and more Everton fans as they got closer to Liverpool and it'd be a crush at the final stations

 

[thenorthern]

While I was at Lancaster on Monday the 1751 train to Barrow in Furness was listed as calling at Barrow in Furness only. It was running 36 min late but I don't think I have ever seen one skipping all stations on the Furness line before.

 

[Mcr Warrior]

While I was at Lancaster on Monday the 1751 train to Barrow in Furness was listed as calling at Barrow in Furness only. It was running 36 min late but I don't think I have ever seen one skipping all stations on the Furness line before.

Did it actually fail to call (or skip stop) all intermediate stations?

 

[thenorthern]

Did it actually fail to call (or skip stop) all intermediate stations?

Not sure I was at Lancaster and it was listed as calling at Barrow in Furness only, I had just got off another train from Grange-over-Sands where at at Grange-over-Sands the 1816 train to Barrow was listed as cancelled.

 

[Mcr Warrior]

Not sure I was at Lancaster and it was listed as calling at Barrow in Furness only, I had just got off another train from Grange-over-Sands where at at Grange-over-Sands the 1816 train to Barrow was listed as cancelled.

Realtimetrains suggests it did call, but 40 mins down at Grange.

https://www.realtimetrains.co.uk/service/gb-nr:G89055/2026-07-06

 

[pokemonsuper9]

Realtimetrains suggests it did call, but 40 mins down at Grange.

https://www.realtimetrains.co.uk/service/gb-nr:G89055/2026-07-06

I don't think it actually stopped anywhere between Carnforth and Barrow, in detailed mode I can see the reports for Silverdale, Arnside and Grange-over-Samds are simultaneous (would usually expect 0.5-1 minutes per stop), and the arrivals were manual reports but the departures were GPS, which is quite odd.

 

[Pinus contorta]

I don't think it actually stopped anywhere between Carnforth and Barrow, in detailed mode I can see the reports for Silverdale, Arnside and Grange-over-Samds are simultaneous (would usually expect 0.5-1 minutes per stop), and the arrivals were manual reports but the departures were GPS, which is quite odd.

It did that with the 1651 ( and I think 1751) on friday. I was a whopping 140 minutes late arriving home due to the missed Corkickle train and the next one being held at Barrow for 20 minutes.

 

[Russel]

LNR Have developed a nasty habit of ripping out stops on the Trent Valley which then leaves a 2 hour gap in the service.

 

[Teapot42]

I don't know what the reason for skipping stops was, but last Wednesday the 0716 from Buxton skipped Heaton Chapel and Levenshulme. For some reason RTT shows it as skipping Davenport and calling at Levenshulme.

The delay? It was under 2 minutes late at Stockport.

There was a single announcement, from the guard, around Woodsmoor. Nothing at Davenport or Stockport, and the automatic announcements still said it was calling at Heaton Chapel and Levenshulme. Plenty of people at both stations looking suitable unimpressed as it sailed past pretty much right on time.

The unit in question wasn't due to depart Manchester for over half an hour, so I can only guess there was a prediction of delays around the station throat and they wanted it in earlier rather than later?

 

[Jamesrob637]

I don't know what the reason for skipping stops was, but last Wednesday the 0716 from Buxton skipped Heaton Chapel and Levenshulme. For some reason RTT shows it as skipping Davenport and calling at Levenshulme.

The delay? It was under 2 minutes late at Stockport.

There was a single announcement, from the guard, around Woodsmoor. Nothing at Davenport or Stockport, and the automatic announcements still said it was calling at Heaton Chapel and Levenshulme. Plenty of people at both stations looking suitable unimpressed as it sailed past pretty much right on time.

The unit in question wasn't due to depart Manchester for over half an hour, so I can only guess there was a prediction of delays around the station throat and they wanted it in earlier rather than later?

2-car rather than booked 4. Prevented overcrowding.

 

[Killingworth]

When running late westbound Hope Valley trains often skip stops after New Mills into Piccadilly to recover time for their next journey. Those wanting intermediate stations should be able to change onto the stopper from New Mills that should run roughly half an hour later.

Late running eastbound trains are picking up a habit of terminating at Grindleford and skipping Dore and Sheffield! Waiting at Grindleford an hour or more for the next train into Sheffield can be an interesting experience. Waiting an extra hour in Sheffield offers a choice of places to sit down under cover and get refreshment.

 

[Teapot42]

2-car rather than booked 4. Prevented overcrowding.

I was actually surprised how quiet it was. I know it can get really busy when Stockport College is in, but the lack of students would suggest term is over? There were spare seats leaving Stockport, whereas I've seen a 4 car with the aisles full in the past.

As the guard didn't appear at any point I wonder if this is the default when it's a 2 car rather than it being assessed on how busy the train actually is?

My main concern though was how poor the announcements were, unless there was an on-station announcement then anyone from Davenport wouldn't have known it wasn't stopping, and it was fairly easy to miss the single announcement there was, especially when the auto annoucements were giving the opposite message.