"Not" Calling at....

[lj9090]

On a similar theme, on some timetables there is sometimes one or two stations which appear to be served by virtually all services, but one occassionally doesn't call, for no obvious reason. I remember on the North london Line timetable many years ago, one train, I think in the morning peak, missed a Hampstead Heath call, inexplicably to me, whilst every other train stopped.
Can anyone offer reasons for this sort of thing, or examples of others?

The weekday 1705, 1735 and 1835 ex Waterloo don't call at Brockenhurst.

 

[tamesidedepot]

I had 'this service does not call at Goole' today on the 1057 from Hull to Sheffield today - understandable in the situation with this diverted via Selby due to the landslip. I suspect this has been common practice on Northern services recently

 

[krus_aragon]

Noticed another interesting one today:

1053 Treherbert.
First Stop Radyr.

It runs fast via the city line. There's a southbound service that does the same (1517 from Radyr). This is the plan for all the fast Merthyr services once the 'Radyr curve' (Track south of Canton Depot from Central to Ninian Park) is redoubled.

 

[Eeveevolve]

"This is the late running XX:08 to Liverpool Lime Street that will NOT be calling at Dewsbury. Get off the train and get the train coming in behind us"

Cue lots of people getting off pretty swiftly.

 

[dvboy]

There used to be one single Birmingham - Manchester train that didn't call at Wolverhampton, and would be announced as such, but it now calls at Wolverhampton along with every other north-west-bound train from Birmingham.