North Cotswold line delays and cancellations - 2025

[whole diary]

[IndustryInsider]

Though why any scheduling system would have three separate TMs^▸ (Train Manager, or Ticket Machine, or Temple Meads (Bristol), depending on context) (Paddington - Reading - Shrub Hill - Great Malvern) for a journey that is 2:22 long is beyond me.

Sadly that's what the computer churns out these days.  Works on paper, but not in practice as soon as anything goes wrong.  The powers that be, don't seem to get it unfortunately.

[Worcester_Passenger]

As you say, a journey of that length with three pieces of work is best described as "vulnerable".  But I would have expected the software to flag it as a potential issue. Alas, I'd fear that the report of the scheduling efficiency statistics wouldn't notice the shortness of the pieces - they'd be lost in any overall average.

It's odd that it's only a one-way cancellation - does this duty not go back to Reading at some stage?

[IndustryInsider]

As you say, a journey of that length with three pieces of work is best described as "vulnerable".  But I would have expected the software to flag it as a potential issue. Alas, I'd fear that the report of the scheduling efficiency statistics wouldn't notice the shortness of the pieces - they'd be lost in any overall average.

Without checking I don't know for sure, but it's quite possible the TM^▸ (Train Manager, or Ticket Machine, or Temple Meads (Bristol), depending on context) assists on the way back, or that a Worcester based TM booking on standby could work it back.

[Worcester_Passenger]

The A return working has now turned up, though I imagine there's been some juggling of pieces of work:

20:20 Hereford to London Paddington due 23:38 will be terminated at Worcester Shrub Hill.
This is due to a shortage of train crew.
Last Updated:17/05/2025 17:36

23:05 Reading to London Paddington due 23:38
An additional train service has been planned to operate as shown 23:05 Reading to London Paddington due 23:38.
Last Updated:17/05/2025 17:38

18:45 : Reading - Paddington leg added (I hadn't noticed this before).
05:15 : spelling

[Worcester_Passenger]

Sunday May 18

1W49 15:45 London Paddington to Great Malvern arrived Worcester Shrub Hill +5 and was cancelled thereafter "due to disorder (VA)".
1W51 16:45 London Paddington to Great Malvern was held Evesham (+14) and arrived +19.

18:57 Great Malvern to London Paddington due 21:27 was started from Worcester Shrub Hill.
It has been delayed at Worcester Shrub Hill and is now 43 minutes late.
This is due to the police dealing with an incident near the railway earlier today.
Last Updated:18/05/2025 20:12

1P81 18:57 Great Malvern to London Paddington was started from Shrub Hill (+29), was held at Norton (+43), arrived +47.

Later...
1W08 18:45 London Paddington to Hereford (21:54) departed +18, was held Great Malvern (+42), arrived +42.
1W73 19:45 London Paddington to Great Malvern (22:16) was delayed after West Drayton, held at Wolvercote (+14), arrived +25.
1W79 21:45 London Paddington to Worcester Shrub Hill (23:59) departed +37 and arrived +33.