A knock on from the signalling problems between Didcot and Swindon this morning:

No line updates on JourneyCheck but a speed restriction due to defective track between Oxford and Evesham is causing some degree of congestion including so far:




outward bound 15:50 PAD:MIM surprisingly going beyond Oxford and arriving at MIM 28 minutes late


later update

Line update now on JourneyCheck:


and the 15:14 Hereford to Paddington has just come through Wolvercote Junction 58 minutes late having been almost on time at Ascott-under-Wychwood.

Days like this certainly support the case for further redoubling at the eastern end of the line as per IndustryInsider's new thread today.

further update


another update

and for those who wanted to go beyond Oxford on the 18:22...


and has just left Reading 34 minutes late, with further delays of up to 45 minutes expected beyond Hanborough.

Things are certainly getting better. However:


and


The wording of the 17:52 and timing - "Last Updated:13/09/2018 18:11" - suggests it was a late cancellation.

Just turned up on JourneyCheck ten minutes after service was due to depart:

Pretty much a cancellation:

Although, as has been mentioned, the service seems to be getting better, over the last couple of weeks, more cancellations and amendments have been appearing in the morning peak service towards London. Today's example being:


From experience of previous years, it's as we get into October, and poor rail conditions start to become an issue, that the service starts to deteriorate significantly.

This one is an IET (and going to be cosy for a Friday as far as it goes):

Passengers on the 15:22 Paddington to Great Malvern got to experience the benefits of the resignalling this afternoon.

As a result of a fault at the north end of Oxford station, the 15:22 was diverted onto platform 3, and then ran down to Wolvercote Junction on the up main (or whatever the correct terminology is!). Meanwhile, the 15:22 WOS:PAD ran towards Oxford on the up relief.

However, putting the Great Malvern train onto platform 3 at roughly the time the Paddington service was due did have an unfortunate but predictable consequence - there was an announcement on the 15:22 PAD:GMV advising passengers who thought they were on the Paddington train to change at Hanborough!

[edit to change one word]

A couple this morning:


and the return


edit to change return from starting from Oxford to full cancellation.

Which starts to get a little tedious for those "affected" who use it for their regular commute when it becomes a weekly or twice weekly event!

Another of GWR's regular easy "fixes":


Third time in 8 days this service has failed to run along the Cotswold Line.

From Realtime Trains:

Not on JourneyCheck as at 16:00 but National Rail Enquiries has the 16:22 Paddington to Great Malvern showing as cancelled. @GWRHelp on Twitter says it's "not running because of a fault on board".

So that's another faulty IET cancellation on the Cotswold Line today.