In addition to the problems between London and Reading, we have:


Nothing moving at the moment (16:45). Amongst other services, the 14:53 Paddington to Worcester Shrub Hill has been stuck at Didcot for an hour, and the 13:55 Great Malvern to Paddington (normally starts from Hereford but the outward service never got there) has been sitting at Charlbury since 15:40.

Edit by admin - with the agreement of the active posters already this year, I have split the 2024 delays and cancellations into a new thread - and this was the first post of 2024.

 
There was also a flooding issue between Charlbury and Oxford. And West Midlands Trains had flooding between Bromsgrove and Longbridge.
And indeed, not much moved after that:

Up trains:
1P34 15:17 Foregate Street - Paddington. Held at Moreton (+92 minutes), Oxford (+120), Culham (+143) and Reading (+167). Arrived Paddington +163.
1P05 15:18 Hereford - Paddington : Started from Ledbury. Held at Evesham (+59), Charlbury (+95), Oxford (+121) and Reading (+136). Arrived Paddington +140.
1P38 16:32 Great Malvern - Paddington : Cancelled after Shrub Hill.
1P39 17:26 Foregate Street - Paddington : Started from Oxford and cancelled after Reading.
1P40 18:02 Foregate Street - Paddington : cancelled throughout.
1P42 19:05 Great Malvern - Paddington : cancelled throughout.
1P44 19:45 Great Malvern - Paddington : cancelled throughout.
1P46 20:56 from Foregate Street : cancelled throughout.
1P06 22:00 from Hereford : started from Shrub Hill, but ran through to Paddington OK.
... so nothing from Shrub Hill between 16:16 and 22:52.

Down trains:
1W29 14:53 Paddington - Foregate Street : held at Didcot (+61) and cancelled after arriving Oxford +121.
1W30 15:23 to Foregate Street : left Paddington +38, cancelled after Reading (+63).
1W31 15:52 to Great Malvern : left Paddington +18, cancelled after Reading (+45).
Halts train : cancelled throughout.
1W33 16:58 to Great Malvern  : cancelled throughout.
1W03 17:34 to Hereford : started from Oxford, cancelled after arriving at Shrub Hill +26.
1W34 17:57 to Foregate Street  : cancelled throughout.
1W36 18:57 to Great Malvern : left Paddington +36, arrived Great Malvern +52.
1W05 19:53 to Hereford : cancelled after Oxford.
1W41 20:52 to Great Malvern  : cancelled throughout.
1W43 21:53 to Shrub Hill : started from Oxford (+32), arrived Shrub Hill +34.
1W45 22:51 to Worcestershire Parkway  : cancelled throughout.
... so westbound trains departed Oxford at 14:50, 18:28, 20:35 and 23:17.

Hopefully passengers will have been able to respond to GWR's "don't travel" alert.  And a big "well done" to the staff who did manage to run at least some trains.

Meanwhile, lots of trains will be in the wrong place this morning:

RTT reports that
Train 1P11, 05:14 Shrub Hill - Paddington was cancelled throughout.
JourneyCheck reports that

 
Morning of 3 January 2024 not shaping up very well

Up trains

1P11 0514 Worcester Shrub Hill to Paddington - cancelled at operator's request

1P02 0523 Hereford to Paddington - cancelled by severe flooding

1P16 0649 Worcester Shrub Hill - ran as booked, left Shrub Hill 6 minutes late, arrived Paddington 5 minutes late

2E80 0700 Worcester Shrub Hill to Didcot - ran as booked

1P18 - 0713 Great Malvern to Paddington - ran as booked

1P20 - 0815 Worcester Shrub Hill to Paddington - cancelled at operator's request

Down trains seem to have run as booked so far this morning

(Editied 03/01/24 1121 to correct the date in the text)

 

The 0523 was a cancellation as far as passengers travelling from the Cotswolds were concerned but was run as a 5 car IET starting from Oxford. It departed Oxford 25 minutes late from platform 4. it was still on the platform as the 0643 Worcester Shrub Hill to Paddington service pulled in to platform 3.

 

To clarify - 2024, I'm afraid - still ongoing.  Should I split th thread at 1.1.204 and rename, or do members on the line prefer it to be a single ongoing thread (and I can flush the titles though to something that would cover both years

 

The year changes but the shambles of a "service" does not.

I guess we should have a new thread for the new year

I've corrected the date in my post of this morning

 

My fault as I did the first 2024 post! My view would be a split would be appreciated. Seeing how many pages the topic gets to each year is a useful indication of how good/bad the year has been compared to previous ones.

 


Thread split, as per the views above (and mine).   Post on this thread for 2024 North Cotswold delays and cancellation, look back to http://www.passenger.chat/27079 to remind yourself of 2023.

 

 

and the return 19:05 working as well

 

together with the return 18:02 working

Also, Realtime Trains reporting

 
JourneyCheck is reporting

Which is odd, because RTT is reporting that

Meanwhile (also according to RTT) at 07:13 an extra train will be operating from Great Malvern to Paddington as empty coaching stock.
This looks to be formed by another empty train, at 05:32 from Gloucester to Great Malvern. On its way to Great Malvern, this gets to Shrub Hill at 06:31. On its way back, it'll pass Shrub Hill at 07:31.

I can't help feeling that (1) JourneyCheck's explanation of the cancellation is doubtful, and (2) it doesn't need to do a double run, empty, to Great Malvern.

 
And what's it going to do when it gets to Paddington?

According to RTT it'll go empty to North Pole, scheduled arrival 10:03. That's 4:31 elapsed time from Gloucester to North Pole, empty.

 

and

 

Meanwhile, for the 17:04 RTT says

 
RTT:

JourneyCheck  is reporting a whole day's diagram:

 





Cotswold line should be renamed the Cinderella line, I'm sure

 

I'm afraid it has competition at the bottom of the pile; I sometimes feel that way about the line that serves my home town too.  Like Cinderella, it was rescued many years ago (and remains appreciative) but has become the child that must give way to others wherever they need anything (like working capacity, available crews, useable trains).

I am reminded that Cinderella was a hard working young lady, artificially supressed but with an acceptance and spirit that took her through hard times maintaining a respect even for those who put her down.  And I am reminded that in the end, with help from various parties, it all comes very much right for Cinderella.

 

Perhaps that's the line the railway should take with all of its services between London and the Southwest at the moment, with Messrs Hopwood & Haines cast as the Ugly sisters?

 

Not sure about your ugly sisters - at times I get the feeling that Messrs H and H are far more in line with us than another Mr H who tells them what to do.

I have asked the fairy godmother to (re)double and electrify some routes so the following all-electric services using EMU stock for regional journeys as well as through opportunities to London could be operated hourly.

London - Reading - Didcot - Swindon - Chippenham - Melksham - Trowbridge - Westbury - Frome - Bruton - Castle Cary - Somerton - Taunton - Wellington - Tiverton - Cullompton - Exeter St Davids

London - Reading - Didcot - Oxford - all stations to Hereford, Newport, Cardiff and Swansea

 

Thankyou Cinders.......hopefully you'll get to go to the Ball, unfortunately Prince Charming is stuck in Devon thanks to today's infrastructure meltdown.

 
Oh no he isn't.

 
...and another Mr H who tells that Mr H that he can't have any more money.

 
Yesterday, Saturday January 13, was a good day on the North Cotswold line.  Attached is the RTT report for all day at Evesham - and there's no red (used for late running) visible whatsoever. Well done to all involved.

 
Even if it will cost less in the end because more people will travel

 
The usual diversion of North Cotswold line trains by way of Stroud has been reversed this morning, with the morning via-Stroud train being sent via Evesham:

Meanwhile, other points failures are affecting other trains:



The 07:50 from Paddington is being reported on RTT as cancelled throughout.

 
JourneyCheck is reporting

 
Getting worse:

 
And this evening:
Thanks to the 14 minute scheduled wait at Great Malvern, this train is now on time.

This train started on time from Paddington and is currently on time.


The outbound working, the 17:34 from Paddington, was cancelled after arriving at Shrub Hill 11 minutes late.

 
This mornng is not getting off to a good start. JourneyCheck is reporting

Stacked up behind it are

1P16 06:43 Shrub Hill - Paddington : RTT reports this as having sat at Ascott since 07:32.

2E80 07:04 Shrub Hill - Didcot 'halts' train : RTT has this sat at Moreton since 07:42.

1P18 07:13 Great Malvern to London Paddington : RTT has this sat at Evesham since 07:50.


------------------------------------------------------------------------------------------------------------------------

08:26 : OpenTrainTimes is showing the dead train on the move towards Oxford as 5P02.
1P16 has arrived at Charlbury 51 late.

-------------------------------------------------------------------------------------------------------------------------

08:35 : JourneyCheck is reporting

 
JourneyCheck:

 

 
RTT reports the following of today's trains as cancelled  in part or throughout:

1W21 1053 Paddington to Shrub Hill (23 late at Moreton in Marsh and cancelled beyond there)

1P30 1316 Shrub Hill to Paddington (started on time from Moreton in Marsh)

1W25 1251 Paddington to Foregate Street (on time at Moreton in Marsh and cancelled beyond there)

1P34 1517 Foregate Street to Moreton in Marsh (cancelled throughout)

and an additional Class 6 train on the Down, from Swindon Transfer to Honeybourne Sidings, which passed Moreton in Marsh at 1613.  Would this be a train to inspect the line? 

So, so far, no service in from Evesham since 1141 on the Up, and 1236 on the Down.

Edit to update latest from RTT:

1W29 1453 Paddington to Foregate Street / Honeybourne 1644 (13 late)

1P05  1518 Hereford (Started from Ledbury) / Honeybourne 1647 (3 late)

 

 
From yesterday (Monday January 22), we should also document that train 1P02, the 05:23 from Hereford, was started from Shrub Hill.

This was down to Storm Isha on Sunday, which resulted in blanket speed restrictions across the network.  By the evening, everything was running late.  Train 1W08, the 1848 to Hereford, left Paddington on time but was 12 late at Reading and 28 late at Oxford. It arrived at Great Malvern 55 late and was cancelled thereafter.

Later trains on Sunday evening also suffered:
1W73 1948 London Paddington to Great Malvern arrived 17 late.
1W77 2048 London Paddington to Worcester Shrub Hill left 23 late and arrived 61 late.
1W79 2156 London Paddington to Worcester Shrub Hill left 49 late and arrived 78 late.

 
And back on today...

 
Problems between Norton Junction and Evesham this morning, though it doesn't get listed on JourneyCheck's 'Line updates' section.

Held at Norton for 17 minutes. Arrived Paddington 21 late.

Held at Norton (+42 minutes).


Now 40 late away from Norton Junction - perhaps GWR were thinking of diverting this one via Stroud as well?

Which they did with the next one:

And in the down direction:

 
Eventually, JourneyCheck catches up with the problems today:

 

 
Not sure when you checked, but there was a great big Journeycheck entry....

 

Bit of a mystery - RRT shows this as the five car 800016, and (at 1220) reports that the Down train is at the platform at Paddington

The same notification appeared on Journeycheck yesterday, when 2-car 165125 formed the Down and Up workings, and did, indeed terminate at Reading .

 

 
1W03 1250 London Paddington to Hereford

Timetable arrival time 16:04 Actual arrival time 16:31 - 27 minutes late

1W39 1350 London Paddington to Great Malvern

Timetable arrival time 16:17 Actual arrival time 16:33 - 16 minutes late.

 
Monday January 29:
Held at Wolvercote and now 32 late at Ascott.

Left on time. Currently approaching Oxford, on time.

 
But now there's big problems:

17:35: The location of the bridge strike seems unlikely - this is not affecting the trains between Worcester and Bristol. The bridge is more likely between Pershore and Parkway.

RTT reports 1W27 1350 London Paddington to Great Malvern as departing Evesham 18 late (having waited for the single line) but arriving at Worcestershire Parkway 88 late.

RTT reports this train as leaving Shrub Hill 9 late and arriving at Evesham 20 late (thereby delaying 1W27 above).

At 17:32, RTT reports this as yet to depart Shrub Hill.


17:33 : RTT reports added.

 
And a bit later:

 
Final score from yesterday, Monday January 29:

1W02 1152 London Paddington to Hereford : 6 late away from Paddington, held at Shrub Hill, arrived Hereford 17 late.
1W25 1251 London Paddington to Foregate St : 25 late by Reading, held at Wolvercote, terminated at Shrub Hill 24 late.
1W27 1350 London Paddington to Great Malvern : held at Evesham then stopped between Pershore and Parkway, arrived Shrub Hill 86 late and cancelled thereafter.
1W29 1453 London Paddington to Foregate St : cancelled after Moreton.
1W30 1523 London Paddington to Foregate St : cancelled after Oxford.
1W31 1552 London Paddington to Great Malvern : cancelled after Oxford.
2E14 1704 Didcot Parkway to Moreton-in-Marsh : OK.
1W33 1658 London Paddington to Great Malvern : OK.

1P34 1517 Worcester Foregate St to London Paddington : started from Shrub Hill, 21 late by Evesham, arrived Paddington 19 late.
1P05 1518 Hereford to London Paddington : cancelled after Worcester Shrub Hill.
1P38 1632 Great Malvern to London Paddington : started from Worcester Shrub Hill 48 late, diverted via Stroud, 28 late by Didcot, arrived Paddington 39 late.
1P39 1726 Worcester Foregate St to London Paddington : started from Moreton-in-Marsh, arrived Paddington 12 late.
1P40 1802 Worcester Foregate St to London Paddington : started from Shrub Hill 16 late, arrived Paddington 8 late.
1P42 1905 Great Malvern to London Paddington : started from Oxford.

At Evesham, up trains at 14:35, 15:59 and 18:42. Down arrivals from London at 13:44, 15:02, 15:36 and 18:47.

 
A few items so far for today:


16.28 edit - the 16:58 & 19:45 cancellations no longer showing on JourneyCheck.

 
And today it's

According to RTT
Train 1P22 0856 Great Malvern to London Paddington lost an hour between Pershore and Evesham, and is currently 62 late after Kingham.
1W15 0750 London Paddington to Worcester Foregate Street had to wait at Evesham, arrived at Foregate Street 60 late and was cancelled thereafter.
1P24 0954 Great Malvern to London Paddington waited at Shrub Hill (very sensible) and is currently 33 late after Pershore.

 
100 or so sheep apparently!

 
Linked to the sheep or totally separate?

 

Is this a record for different causes of delay? Perhaps JourneyCheck is on a 'random' setting today?

 
And for once, the Worcester News has a real photo, at https://www.worcesternews.co.uk/news/24087967.herd-120-sheep-railway-tracks-wyre-piddle/.

 

I'm glad that the problem was resolved and that passengers were got on their way eventually.  But it's a surprise that West Mercia Police became involved.  I'd have expected any police involvement would have been from BTP.  I guess the police and some local workmen who happened to be nearby was a quicker solution than having to wait for staff from however the permanent way department is run these days.   Where was the farmer and/or owner of the sheep in all this?

 

No - it was all the one cause, wasn't it?

There was congestion on the line caused by industrial action by sheep on the line not sticking to the field they are constrained to. This incident was being dealt with by the police and in the resulting disruption some train crew were being delayed in getting to their next train.

 

 

Where were the nearest BTP? Birmingham /  Reading / Cardiff most likely.

 
As at 16.34 JourneyCheck is reporting


when actually it has "been cancelled due to action short of a strike."

 
And then the next three services:

1612 from Paddington (1645 Oxford) running 22 late and will apparently be omitting Hanborough, Charlbury, Kingham, Pershore, Honeybourne.

Halts train (1723 Oxford) is cancelled.

1658 from Paddington (1746 Oxford) is running... and is a 5-car.

 

Seriously??? A service is cancelled, the next one misses out two of the busiest stops between Oxford and Worcester, and the one after is cancelled! So passengers for these stations who were hoping to catch the 16:18 from Oxford will have to wait until 17:46!

 

 

Some taxis were laid on, which is better than nothing. I think (via a second-hand report) that there may have been a concern about the IET driver reaching their maximum allowed hours. Omitting the stops, plus the booked dwell at Evesham, meant that the 1612 was running to time by Worcester.

Slightly surprised that the busy West Oxfordshire stops were omitted rather than running late throughout and capeing it at Worcester, but I confess I've not looked at the single line utilisation to see if that would work.

 

A cancellation today

 
And a couple more cancellations:

 
And

 
and also

 
RTT reports that the return working, 20:56 from Foregate Street to Paddington, was cancelled throughout.

 
An unusual one last night (Wednesday February 7).

1P42, 19:05 from Great Malvern, sat at Pershore for 12 minutes. It was cancelled after arriving at Evesham 13 late - "due to a problem with the train" according to RTT.

The next one, 1P44 19:45 Great Malvern to London Paddington, was held at Shrub Hill (was there a concern about 1P42 blocking the line?). It eventually left 31 late but recovered to arrive Paddington only 6 late. It's scheduled to take 2:20 from Shrub Hill, but actually took 1:56 (without omitting any stops).

 

I wonder what happened to the train after being terminated?  It could have turned-back to Worcester, or carried on towards Oxford or beyond, but RTT doesn't tell us.  There's nowhere at Evesham for a failed train to be put out of the way. 

 

Presumably ran ECS back to Worcester Shrub Hill, and from there at 23:26 as 5Z74 to Stoke Gifford depot according to RTT.

 

According to RTT, the train from London which should have formed this, 1W02 1152 Paddington to Hereford, was also cancelled, but due to "late arrival of the inbound service"

 

No mention (yet) of the return working, 19:05 Great Malvern - Paddington.

Meanwhile, at Paddington, the 17:57 to Foregate St has left on time but the 17:34 to Hereford left at 18:03.

19:08 : still nothing on JourneyCheck about the 19:05 from Great Malvern. Nor anything about the 17:34 to Hereford, now 38 late out of Oxford.

21:52 : the 17:34 to Hereford arrived 78 late.

 

 
A post to record the fact that 1P20 0815 Worcester Shrub Hill to Paddington was cancelled between Worcester and Oxford this morning because of "late arrival of an inbound service"

There will be days when the Cotswold route service isn't chopped in places, but today, like so many days, isn't one of them

 

This train was formed from the late-running 04:59 Swansea - Paddington, scheduled into Paddington at 07:44. It arrived at Reading some 24 late and was cancelled thereafter.

 
Tuesday February 13:

 
That's novel!


Thu, 15 February 05:23 Hereford to London Paddington due 08:24

15/02/24 05:23 Hereford to London Paddington due 08:24 will be cancelled.
This is due to a fault on a train in front of this one.

 
Perhaps down to

 
And another very early warning for Thursday (Feb 15):
Will 'cancelled' change to be 'has been reinstated' during the course of the day?

 

 

RTT reports that 1P02 the 0523 Hereford to Paddington was cancelled this morning, because of "an excluded reason"

So, from a timetabled five Up trains at Evesham before 0900 this morning, only three actually ran

People not bothering with trains any more would be perfectly understandable

 
A couple of aspects to this from the point of view of a passenger is that someone heading for the 05:23 from Hereford, as well as several of the later ones will be more than usually motivated to travel for some time-critical reason. They will also be paying peak time prices for a service which has now evolved to be very flaky.

Mark

 

 

RTT gives the code itself too: PL. The wordy version for that is "Exclusion commercially agreed and documented between Network Rail and Train Operator", or AGREED EXC. But in fact all codes starting with P are excluded from the Track Access Performance Regime. Top of the list of P-codes are PA and PB, for temporary speed restrictions. You may think they are all in some sense NR's fault, but these TSRs are left out of the calculations.

Also in the list is PG: "Planned cancellation where that cancellation is identified and agreed prior to 22.00 the day before the schedule runs", PLAND CAPE. So that's the P-code for trains that are P-coded, if you like,.

 
Sunday February 18
Fortunately we're not affected by the flooding, but...

 
Monday February 19
RTT reports that train 1W01 09:52 London Paddington to Hereford "was cancelled between Great Malvern and Hereford due to a problem at the depot (MU)."
It lef Paddington 19 late, lost more time, stood at Oxford for 13 minutes, was held at Evesham for 18 minutes (awaiting the on-time 11:57 from Great Malvern), and arrived Great Malvern 59 late.

 

 

 

 

RTT has the return working 1P28 1157 Great Malvern to Paddington cancelled too.  Not surprising, since the failed 1W17 0851 Paddington was sent back empty from Moreton in Marsh to North Pole as 5Z01




The silence you hear is the bigwigs who "run" the railway not giving a stuff about their paying passengers on the OWW (fully living up to its name).  The clunks you hear are people getting into their cars and closing the doors, having given up on trains as a bad job

 
And somewhat predictably following the failure of 800033 this morning:

 
Thursday February 22
RTT has this one as yet to arrive at Henwick, so at least 83 late.

 
RTT shows

1P22 0856 Great Malvern to Paddington terminated at Worcester Shrub Hill

1P24 0954 Great Malvern to Paddington ran only between Foregate Street and Shrub Hill, here it was terminated

and, as above, 1W02 1152 Paddington to Hereford cancelled throughout

All caused by severe flooding

No Up trains at Evesham between the departure of the 0835 and the time of writing (1237).  1P26, due 1136 off Evesham, was 67 minutes late leaving Worcestershire Parkway, and, according to RTT,  is yet to arrive at Pershore

 

!W25, 1251 Paddigton to Worcester Foregate Street, which forms this service after arrival in Worcester, is running okay (ish - is's a few minutes late)

 
10:59 Great Malvern - Paddington was started from Shrub Hill 47 late due to the flooding, but was held at Norton for the single line. It arrived at Reading 76 late and was cancelled thereafter.

 
And add to that
RTT is reporting it as still being at Evesham, possibly waiting for 1P38, 16:32 Great Malvern - Paddington, which passed Norton 16 late.

 
With the cancellation of the 15:17 Worcester Foregate Street to London Paddington and 15:18 Hereford to London Paddington, followed by the diversion of the 16:32 Great Malvern to London Paddington due to a safety inspection of the track, that means no up services from the Cotswolds to London for the best part of four hours.

It's been a messy day for many reasons - and it'll be interesting to see how bad the service was today overall - but not all the cancellations can be put down to the weather. It's unfortunate that services were cancelled due to more trains than usual needing repair etc when the weather was already causing so much disruption.

 

With no end in sight, and worsening availability of IETs, the situation can’t continue.  Something needs to change and I can’t see Hitachi making any significant improvements to IET reliability.  It should have and would have happened by now.
You either start electrifying more GWR routes to alleviate the reliability issues with the diesel engines or you ditch the fleet and bring in an interim solution in the form of the ex-TPE Mk5 stock. 
They’ll come a point, if it’s not already been reached, where the GWR IET stock is simply too costly to keep running.  There’s obviously a maintenance contract currently in place, once that’s up for renewal, is it possible Hitachi could just walk away from it and saddle GWR with all the reliability issues?

 

 
Sorry for the presentation but this seems to be a summary of most of the issues affecting services on the North Cotswold Line yesterday:

1P22 0856 Great Malvern to Worcester Shrub Hill: cancelled between Worcester Shrub Hill and London Paddington due to severe flooding (X2) (134 late at WOS)
1W01 0952 London Paddington to Great Malvern: cancelled between Great Malvern and Hereford due to late arrival of an inbound service (YI) (65 late at GMV)
1P24 1008½ Worcester Foregate Street to Worcester Shrub Hill: cancelled between Great Malvern and Worcester Foregate Street due to severe flooding (X2) (90 late at WOS)
1W21 1053 London Paddington to Worcester Shrub Hill: 22 late at WOS
1P26 1116½ Worcester Shrub Hill to Reading: cancelled between Great Malvern and Worcester Shrub Hill due to severe flooding (X2) & between Reading and London Paddington due to late arrival of an inbound service (YI) (76 late at RDG)
1W02 1152 London Paddington to Hereford: cancelled due to unknown cause (ZW)
1P28 1157 Great Malvern to London Paddington: 23 late at PAD
1W25 1251 London Paddington to Moreton-in-Marsh: cancelled between Moreton-in-Marsh and Worcester Foregate Street due to a problem with the traction equipment (MD) (12 late at MIM)
1P30 1316 Worcester Shrub Hill to London Paddington: 14 late at PAD
1W27 1418½ Reading to Great Malvern: cancelled between London Paddington and Reading due to late arrival of an inbound service (YI)
1W29 1453 London Paddington to Worcester Shrub Hill: cancelled between Worcester Shrub Hill and Worcester Foregate Street due to late arrival of an inbound service (YI) (59 late at WOS)
1P34 1517 Worcester Foregate Street to London Paddington: cancelled due to late arrival of an inbound service (YI)
1W30 1523 London Paddington to Worcester Shrub Hill: cancelled between Worcester Shrub Hill and Worcester Foregate Street due to late arrival of an inbound service (YI) (60 late at WOS)
1W31 1552 London Paddington to Great Malvern: cancelled due to a problem with the train (M8)
1P05 1518 Hereford to London Paddington: cancelled due to late arrival of an inbound service (YI)
2E14 1704 Didcot Parkway to Moreton-in-Marsh: 34 late at MIM
1W33 1658 London Paddington to Great Malvern: diverted between Didcot and Norton Junction (22 late at GMV)
1P38 1632 Great Malvern to London Paddington: diverted between Norton Junction and Didcot
1P39 1730 Worcester Shrub Hill to London Paddington: 47 late at PAD
1W03 1734 London Paddington to Hereford: cancelled due to unknown cause (ZW)
1P40 1802 Worcester Foregate Street to Reading: cancelled between Reading and London Paddington due to a signalling problem (track circuit failure) (IC) (61 late at RDG)
1W34 1757 London Paddington to Worcester Foregate Street: 33 late at WOF
2E16 1910 Moreton-in-Marsh to Oxford: cancelled between Evesham and Moreton-in-Marsh due to a signalling problem (track circuit failure) (IC) (14 late at OXF)
1W36 1857 London Paddington to Great Malvern:  (50 late at GMV)
1P42 1905 Great Malvern to London Paddington: cancelled due to late arrival of an inbound service (YI)
1P46 2056 Worcester Foregate Street to London Paddington: 42 late at PAD