North Cotswold line delays and cancellations - 2025

[whole diary]

[Worcester_Passenger]

Wednesday January 15

07:13 Great Malvern to London Paddington due 09:42 was started from Worcester Foregate Street and will be terminated at Reading.
It has been delayed at Worcester Foregate Street and is now 73 minutes late.
This is due to a broken down train.
Last Updated:15/01/2025 09:07

Held at Norton (+88). Running behind 1P20 08:15 Worcester Shrub Hill to London Paddington.

08:56 Great Malvern to London Paddington due 11:24 will be started from Worcester Foregate Street.
This is due to a broken down train.
Last Updated:15/01/2025 08:08

09:55 Great Malvern to London Paddington due 12:23 will be started from Worcester Shrub Hill.
This is due to a broken down train earlier today.
Last Updated:15/01/2025 09:11

[charles_uk]

19:53 London Paddington to Hereford due 22:57 will no longer call at Hanborough, Kingham, Moreton-In-Marsh, Honeybourne, Pershore and Worcestershire Parkway Hl.
It has been delayed at London Paddington and is now 28 minutes late.
This is due to this train being late from the depot

I wonder what the logic was for retaining the Charlbury and Evesham stops whilst missing out some more used intermediate stations between Oxford and Worcester.

[Worcester_Passenger]

20:52 London Paddington to Great Malvern due 23:13 will be terminated at Moreton-In-Marsh.
This is due to failure of the electricity supply.
Last Updated:16/01/2025 22:12

Arrived Oxford on time. Departed +32.

21:53 London Paddington to Worcester Shrub Hill due 00:01 will be delayed at Oxford.
This is due to failure of the electricity supply.
Last Updated:16/01/2025 22:27

22:00 Hereford to London Paddington due 01:15 will be starting late from Hereford.
This is due to failure of the electricity supply.
Last Updated:16/01/2025 21:39

Departed Hereford on time.

[Richard Fairhurst]

Well, that was entertaining. Held at Oxford platform 4 for half an hour while a supposed signal failure at Wolvercot Junction was sorted out, only for the train crew to be told belatedly that the problem was actually at Norton Junction. Not Wolvercot.

[Worcester_Passenger]

Well, that was entertaining. Held at Oxford platform 4 for half an hour while a supposed signal failure at Wolvercot Junction was sorted out, only for the train crew to be told belatedly that the problem was actually at Norton Junction. Not Wolvercot.

And it caused a lot of disruption further west. RTT^» (Real Time Trains - website) reports that nothing passed Norton between 21:07 and 23:13.

1W05 1953 London Paddington to Hereford ( : departed +28 (late from depot), skipped stops (as above), arrived Evesham +7, departed +87, at Norton 23:13, arrived Hereford +67.
1W41 2052 London Paddington to Great Malvern : held Oxford +32, arrived Moreton-in-Marsh +37, cancelled thereafter. Stock ran ECS^▸ (Empty Coaching Stock) to Shrub Hill.
1W43 2153 London Paddington to Worcester Shrub Hill : held Oxford +21, arrived +21.
1W45 2251 London Paddington to Worcestershire Parkway : held Wolvercote, arrived +15.

Up trains:
1P46 2056 Worcester Foregate Street to London Paddington : at Norton 21:07, OK.
1P06 2200 Hereford to London Paddington : held at Malvern Link (+24), at Norton 23:21, arrived +18.

[Richard Fairhurst]

We were on the 2052 (or the 2144 from Oxford). Passengers for beyond Moreton were told to de-train at Oxford for road transport to be arranged. I strongly suspect it would have been quicker for them to just wait for the following train!