The outward journey, 1W01 09:52 London Paddington to Hereford (12:46) was on time until Ledbury, but arrived Hereford +27.

The second return trip, 1W02 11:52 London Paddington to Hereford (14:44) was cancelled after Worcester Shrub Hill "due to a fault with lineside cabling (II)".


Later:

But even later:

The 17:34 Paddington - Hereford is still operating.

 

Yet another great day for the Hereford service

 

That seems more likely! 

 
Internal notes suggest it was overnight cabling works which overran.  Perhaps someone in the dead of night misread that as overhead cabling works?

That set stables overnight in the Down Siding at Hereford.  The one that comes up from Stoke Gifford now forms the 07:13 GMV-PAD.

 
Suspect no wires at Hereford - might be those at Stoke Gifford, if that's where the stock originates?

 

 

 
And after a good day on Monday March 31, today there are problems with the overhead wires at Hereford:

Having departed +67, this train was further delayed at Ledbury (+75) and Foregate St (+81). Cutting out the stops helped - it arrived Charlbury +62, but had to wait for the single line and it left +73. Arrived Paddington +67.

 
Saturday March 29

1P27 1320 Hereford to London Paddington : held Didcot (+36), arrived +42.
1W03 1650 London Paddington to Hereford : departed +30, arrived Worcester Shrub Hill +27 and cancelled thereafter.
1P41 20:20 Hereford to London Paddington : started from Worcester Shrub Hill.

Sunday March 30


The 10:50 departed +25, was held at Wolvercote (+40) and Evesham (+54). It arrived Foregate St +54 and was cancelled thereafter.

1W03 1250 London Paddington to Hereford departed +25, was held at Wolvercote and arrived +37.

The 15:50 and 16:50 have now disappeared from the list of changes.

19:20 :

Later:
Departed Paddington +22. Delayed at Radley (+35) and Oxford (+53). Arrived Shrub Hill +30.

 
A few from yesterday:

1P16 0753 Oxford to London Paddington - This service was cancelled between Worcester Shrub Hill and Oxford due to an issue with the train crew (TG).
1P38 1632 Great Malvern to London Paddington - was diverted between Worcester Shrub Hill & Didcot Parkway missing out the north Cotswolds.
1W03 1734 London Paddington to Ledbury - This service was cancelled between Ledbury and Hereford due to a person hit by a train (XC).

 
Monday March 24


The 22:00 from Hereford is only going as far as Shrub Hill this week - there's overnight engineering work, described at https://www.nationalrail.co.uk/engineering-works/oxford-and-worcester-shrub-hill-20250324/.

Later:
In the end, the 17:53 made it to Hereford, and the 22:00 return didn't have to be cancelled.

 
Saturday March 22

Starting the Hereford from Oxford doesn't count:

10:30:

In the evening, there was an incident at Twyford, and delays at Oxford:
1P39 20:03 Worcester Foregate Street to Paddington (22:23) : delayed after leaving Oxford, and cancelled after arriving Reading +44 due to an issue with the train crew (TH).
1P41 20:20 Hereford to London Paddington (23:38) : held Shrub Hill (+15), delayed before Oxford (+26), arrived +42.
2E98 22:44 Great Malvern to Evesham (23:22) : cancelled throughout.

1W37 18:52 London Paddington to Great Malvern (21:13) : cancelled throughout.
1W39 19:52 London Paddington to Worcester Shrub Hill : started from Reading (+87), cancelled after arriving Shrub Hill +85.
1W43 21:53 London Paddington to Worcester Shrub Hill : held at Oxford (+31), arrived +41.

 
Friday March 21


Later:
Does not bode well for tomorrow's 1P13 06:18 Hereford to London Paddington.

 
Thursday March 20

A day of points failures in the Thames Valley.

1W02 11:52 London Paddington to Hereford (14:44) : departed +16, delayed before Oxford (+45), arrived Worcester Shrub Hill +57 and cancelled thereafter.
1W29 14:53 London Paddington to Worcester Foregate Street : cancelled throughout due to trespassers.
1W30 15:23 London Paddington to Worcester Foregate Street (17:47) : started from Oxford (+31), arrived Shrub Hill +27 and cancelled thereafter.
1W31 15:52 London Paddington to Great Malvern : departed +21, held Oxford (+36) and Shrub Hill (+47). Arrived Worcester Foregate Street +48 and cancelled thereafter.
1W03 17:34 London Paddington to Hereford (20:25) : departed +20, arrived +29.
1W34 17:57 London Paddington to Worcester Foregate Street (20:11) : held Wolvercote and Shrub Hill (+34).

1P24 09:55 Great Malvern to London Paddington (12:23): delayed after Reading, arrived +27.
1P26 10:59 Great Malvern to London Paddington (13:25) : delayed after Reading, arrived +24.
1P28 11:57 Great Malvern to London Paddington (14:23) : delayed after Reading, arrived +72.
1P30 13:16 Worcester Shrub Hill to London Paddington (15:22) : delayed after Reading, arrived +24.
1P04 13:18 Hereford to London Paddington (16:24) : delayed after Reading, arrived +30.
1P05 16:17 Hereford to London Paddington (18:29) : started from Worcester Shrub Hill, delayed after Reading, arrived +17.
1P39 17:26 Worcester Foregate Street to London Paddington : cancelled throughout.
1P44 19:45 Great Malvern to London Paddington : departed +10, held Henwick (+18),

 
The rest of the day had late running and truncations:

Wednesday March 19

1P02 05:23 Hereford to London Paddington : 5-car. Held Charlbury (+18), as described above, arrived +20.
1P22 08:56 Great Malvern to London Paddington : started from Worcester Shrub Hill
1P28 11:57 Great Malvern to London Paddington : started from Worcester Shrub Hill (+9), arrived +12.
1P44 19:45 Worcester Shrub Hill to London Paddington : started from Shrub Hill.

1W11 05:53 London Paddington to Great Malvern : delayed at Oxford (+19), held Evesham (+38), cancelled after arriving +44 at Worcester Shrub Hill.
1W17 08:51 London Paddington to Great Malvern : delayed near Acton, Reading +19, held Wolvercote (+35), arrived Worcester Shrub Hill +36 and cancelled thereafter.
1W02 11:52 London Paddington to Hereford : delayed before Reading +17, arrived +19.
1W33 16:58 London Paddington to Great Malvern : departed +24, Oxford +38, arrived Worcester Shrub Hill +43 and cancelled thereafter.
1W03 17:34 London Paddington to Hereford : delayed Reading - Oxford (+28), held Wolvercote (+32), arrived +31.
1W34 17:57 London Paddington to Worcester Foregate Street : held Wolvercote (+13) and Evesham (+33), arrived +35.

 
Once again


This is becoming quite a regular occurrence recently. This service was also held Charlbury for 18 minutes due to the late running 06:50 Paddington to Great Malvern service. It departed Hanborough at roughly the time the following 06:43 Worcester Shrub Hill to Paddington train was supposed to arrive, leaving a very full platform of passengers who decided to wait for that train (or, quite possibly, simply couldn't board the crush loaded HFD:PAD short-form).

 
Monday March 17


Later:


Later still:
1P42 1904 Great Malvern to Paddington was cancelled after Worcester Shrub Hill "due to a problem with the train (M8)" [RTT].
The stock ran empty to Paddington and from there to North Pole.

 
Sunday March 16


17:30:

18:00: Additional 17:15 departed Shrub Hill +19, but was held at Norton (+35).

19:00 : Bad News for tomorrow morning - this evening's 1W08 18:50 London Paddington to Hereford is a five-car set, so tomorrow morning's 1P02 05:23 Hereford to London Paddington (08:23) will be crowded.

 
Saturday March 15

1P13 06:18 Hereford to London Paddington was started from Worcester Shrub Hill due to an issue with the train crew (TH).

1W25 1253 London Paddington to Foregate St was terminated at Reading due to a person hit by a train (XC).

15:42 : still at Paddington.
17:10 : RTT reporting as cancelled. Forms 1P35 1748 Great Malvern to London Paddington.

 
Thursday March 13

Morning 'halts' train, 2E80 07:00 Shrub Hill to Didcot Parkway, started from Oxford.

 

What a way to run a railroad!

 

BPW lost Newport Hereford Malvern Wells in May 2022, all ECS moves from Stoke Gifford going via Charfield.

No idea whether it is DaFT or GWR behind it, or possibly both?

Other losses of route knowledge including BTM HSS saying goodbye to Lydney and Kemble. It has been predicted, the tunnel will shut after a London service has left Newport and when the BTM driver is asked to go the scenic way it will be a "Sorry but no. I could have last week but railway politics trumps common sense".

 
So.....aren't the early trains that start at HFD driven by drivers from BPW? If not, how do they get from Hitachi to their starting point? At least one starts at Hitachi....

And 'who' is doing the forcing? GWR? DfT?

 

And it's going to get worse from May when 30 or so drivers at BPW are forced to remove their route knowledge from Didcot to Malvern Wells via Evesham. Also BPW loosing Cheltenham to Worcester.

Other reductions are taking place as well.

 

The "service" on the OWW and chocolate fireguards have things in common

 

Very likely.  For example, some of the Bristol-Worcesters today are 9-car IETs instead of 3-car 165s, and this looks to be the pattern for the other three days of the races.

 

Was the 9-car set sacrificed on this service to make it available for the Cheltenham gee-gees extra traffic today?

Doesn't bode well for the rest of the week

Gone are the days of direct D1000 hauled 10-car trains of all first class trains between Paddington and Cheltenham Racecourse (In addition to originating from Cardiff and Wolverhampton)

 
Tuesday March 11

Unadvertised on JourneyCheck, the 05:23 from Hereford to Paddington (arrive 08:23) is formed of a five-car set.

Later:

 
Sunday March 9


Later:

 
Train failed in the platform possibly?

 


Posted 8 minutes before the planned departure from Paddington time

 

with the following 17:34 London Paddington to Hereford service running 16 minutes late and a five car short formation. Not surprisingly the GWR app is showing no unoccupied seats.

 

 



OWW, and the GW mainline services in general, not exactly covering itself in glory today.  Thanks to a pesky S&T fault that appears to have taken most of the morning to fix

 

The corresponding down service, the 0715 from Paddington, was caped earlier in the morning, thanks to the signalling fault that disrupted the timetable in the Thames Valley

 


11:57 Great Malvern to London Paddington due 14:23 will be started from Worcester Shrub Hill.

 
Hmm. That looks as though it could have been more unpleasant than it was.

Mark

 
Short runs on Paddington - Hereford services today and cancellations for LM services between Worcester and Hereford because of this bridge strike in Herefordshire

https://www.herefordtimes.com/news/24976248.pictures-show-a4103-lorry-crash-herefordshire/

 
Friday February 28

Points failure in the Slough area.

Reading +26, held Oxford (+32), held Evesham (+52), arrived Shrub Hill +47, Foregate St +43.

 
Thursday February 27

What a surprise:

Later:

1W27 13:50 London Paddington to Great Malvern (16:15) : arrived Worcester Shrub Hill +9 and was cancelled thereafter "due to a problem with the traction equipment (MD)" (RTT).

 
Wednesday February 26

 
Tuesday February 26

Disruption due to a points failure at Maidenhead.

1W27 13:50 London Paddington to Great Malvern (16:15) : departed +17, Oxford +23, held Wolvercote and Evesham, arrived Worcester Shrub Hill +60 and cancelled thereafter.
1W29 14:53 London Paddington to Worcester Foregate Street (17:04) : held Evesham (+14), arrived +12.
1W30 15:23 London Paddington to Worcester Foregate Street (17:47) : started from Oxford.
1W34 17:57 London Paddington to Worcester Foregate Street (20:11) : delayed Maidenhead (+31), Oxford +40, arrived +45.

1P38 16:32 Great Malvern to London Paddington (19:29) : started from Shrub Hill (+13), stands for 16 at Moreton.
2E16 18:51 Evesham to Oxford (19:50) : held Charlbury for 1W34 (+21), arrived +14.

 
Sunday February 24


Later:
1W02 11:45 London Paddington to Hereford (15:03) : departed +21, benefits from a 15-minute stand at Great Malvern, arrived +6.
1W03 12:45 London Paddington to Hereford (16:04) : delayed at Didcot, Shrub Hill +15, benefits from a 16-minute stand at Ledbury.
1W49 15:45 London Paddington to Great Malvern (18:15) : departed +12, arrived +26.
1W51 16:45 London Paddington to Great Malvern (19:15) : departed +20, arrived Shrub Hill +37 and cancelled therafter "due to an issue with the train crew" (RTT).
1W59 17:45 London Paddington to Great Malvern (20:14) : delayed before Reading (+27), delayed at Shrub Hill (+34), arrived +36.
1W73 19:45 London Paddington to Great Malvern (22:16) : departed +25, held Wolvercote (+42), arrived Worcester Shrub Hill +44 and cancelled thereafter "due to the planned train being replaced with a slower train (MS)" (RTT).
1W79 21:45 London Paddington to Worcester Shrub Hill (23:59) : departed +24, arrived +14

1P59 13:58 Great Malvern to London Paddington (16:30) : held Norton (?), arrived +21. Forms 1W51.
1P73 16:59 Great Malvern to London Paddington (19:30) : held Henwick (+11) and Charlbury (+24), arrived +34.
1P81 18:58 Great Malvern to London Paddington (21:30) : held Shrub Hill (+29), arrived +34.
1P85 19:58 Great Malvern to London Paddington (22:29) : started from Worcester Shrub Hill (+14), arrived +20.

 
Saturday February 22


Later:

 
Seems GWR were making up for earlier cancellations.



I'm imagining what the Journey Check message would have said?

"Facilities on the 1518 Worcester Foregate to London Paddington due 1729. This train will be formed of 18 coaches instead of 9. We apologise for any inconvenience."

 

There are other hints at the tightness - such as the suspension of the Bristol - Oxford Saturday trial in the summer while an IET is going to Newquay.  As the new^(*) 175 units enter service, it will be very interesting^(*) to see whether / how much they are used to relieve the tension on the IET fleet, how much they are used to relieve the tension on other fleets such as the 158s, and how much they are used to displace the other very oldest trans on the fleet rather than adding any extra robustness into the fleet.

 
That answer is public - held within the contract for IETs by GWR. There is a specified number of units on standby to cover failed units, and I can't remember the number  but I recall that they are in low single digit numbers per day,

 
It would be very interesting to know what suggested availability of these IEP units was, at the time of acquisition, compared to what is achieved.  It looks as if there is an extremely thin amount of cover for failed units.  In a lot of cases, it seems to me, no cover at all.  A breakdown means a cancelled diagram, and that's that.  And to hell with the passengers' plans

 
Later:

The 18:02 is formed of the stock of this morning's failed 08:56.

 

A cancellation in all but name for most who would have wished to join this train

 

 
Thursday February 20

Originally posted at 06:05 as starting from Reading "due to train crew being delayed". Stock ran empty from Paddington to Reading. Departed Reading +33, Oxford +20, held Wolvercote.

 

The 08:56 is a five-car set and is carrying the passengers from the cancelled 08:15.

 

 

 
Tuesday February 18 was a very good day.

Wednesday February 19

A couple of early warnings, which may yet change:

 

Glad to hear this. I wonder why National Rail gave it the hashtag of #Charlbury, rather than #Evesham. And that disruption was extended to at least 1230

 
The second up train has been diverted via Swindon, but the previous delayed one is pretty much running in its path to Didcot anyway.

 

Not quite.  Somebody jumped from a bridge in the Evesham area and had to be stretchered off in an ambulance.  Reported at 08:50 with normal working resumed at 09:30, but that delayed the first London bound service by an hour and will no doubt have a knock on effect for a little while.

 
Seems to be a farality at Charlbury this morning with line blocked until lunchtime, so maybe declared suspicious by BTP

 
Saturday February 15

A very good day. Attached screenshot is the RTT report for Evesham, with only one train in red, and that's five late.

 

 

 
Friday February 14

and after a good day yesterday, today we have a signals failure at Gloucester. This has resulted in

1L66 07:25 Worcester Shrub Hill to London Paddington (10:00) via Gloucester : re-routed via Cotswold line, running non-stop from Shrub hill to Didcot.
1P20 08:15 Worcester Shrub Hill to London Paddington (10:23) : cancelled throughout. This train arrives from Swindon via Gloucester.

Not sure why the 07:25 didn't get cancelled and the stock used for the 08:15.

 

 
Monday February 10


The stock for both of these comes in from Stoke Gifford.
Leaves a gap in the up direction at Shrub Hill between the 'halts' train at 07:00 and the next at 09:15.

Later:

 
Sunday February 9

The problems with the track continue:


In the evening:
1W08 18:45 London Paddington to Hereford (21:55) : departed +17, arrived +13.
1W73 19:45 London Paddington to Great Malvern (22:16) : departed +46, arrived Worcester Shrub Hill +65 and cancelled thereafter.
1W77 20:45 London Paddington to Worcester Shrub Hill (23:00) : departed +9, Reading +20, arrived +23.
1W79 21:45 London Paddington to Worcester Shrub Hill (23:59) : departed +31, arrived +32

 
Saturday February 8



In the evening, there were problems with the track between Ealing Broadway and Paddington.

1W03 16:50 London Paddington to Hereford was cancelled after Worcester Shrub Hill "due to a problem with the train (M8)" - RTT.
1W35 17:52 London Paddington to Worcester Foregate Street due 20:10 was cancelled as above.
1W37 18:52 London Paddington to Great Malvern (21:13), departed +41, was held at Evesham (+61), arrived Worcester Shrub Hill +59 and was cancelled thereafter.
1W39 19:52 London Paddington to Great Malvern (22:23) departed +44, arrived Worcester Shrub Hill +40 and was cancelled thereafter.

1P33 17:00 Great Malvern to London Paddington (19:24) arrived +54.
1P35 17:48 Great Malvern to London Paddington (20:23) arrived +37.
1P37 19:00 Great Malvern to London Paddington (21:24) arrived +36.
1P39 20:03 Worcester Foregate Street to London Paddington (22:23) arrived +25.
1P41 20:20 Hereford to London Paddington (23:38) was started from Worcester Shrub Hill and arrived +22.

 

It still is......


I think it is - the train only reached GMV on the down service owing to the train in front having a fault. Therefore it bas to start back from the same place for the same reason - it got stopped on the down....

 

and, inevitably


The train with the fault was in front of a down service.  So the reason/excuse for this cancellation is not really a proper explanation

 

A cancellation for some of the Malverns part of what BR InterCity used to call The Cotswolds and Malverns line

 
And this afternoon, we have

 
So, no 0534 first down train from Evesham this morning, with the next one being three hours later at 0839.  Followed by another gap, of 80+ minutes, until the next one, which departed at 0951.

I'm not sure how much help the X50 "express" bus can be for commuters who need to be in Worcester to start work or school/college, when the trans go missing.  That bus journey takes almost an hour

 
Wednesday February 6

Late running in the evening, caused by faulty doors, by delays in the Thames Valley and (round 23:00) problems with a WMR train at Foregate St:

1W29 14:53 London Paddington to Worcester Foregate Street (17:04) : OK until Norton but arrived Shrub Hill +16 and cancelled thereafter "due to a problem with the doors (M7)" [RTT].
1W30 15:23 London Paddington to Worcester Foregate Street (17:47) : held Parkway, arrived Shrub Hill and Foregate St +19.
1W31 15:52 London Paddington to Great Malvern (18:26) : held Evesham (+15), arrived +22.
1W33 16:58 London Paddington to Great Malvern (19:25) : delayed before Reading (+18), held Shrub Hill (+19), arrived +17.
1W03 17:34 London Paddington to Hereford (20:25) : delayed before Reading (+20), held Wolvercote (+25), arrived +27.
1W34 17:57 London Paddington to Worcester Foregate Street (20:11) : delayed before Reading (+11), arrived +21.

1P39 17:30 Worcester Foregate St to London Paddington (19:52) : started from Shrub Hill +16 but 10-minute stand at  Moreton meant on-time from Oxford.

1W41 20:52 London Paddington to Great Malvern (23:13) : arrived Shrub Hill +7, but departed +28, arrived Malvern +31.
1P06 22:00 Hereford to London Paddington (01:15) : held Henwick (+36), arrived +26.

Thursday February 6


Later:

1W11 05:53 London Paddington to Great Malvern (08:38) was +4 at Charlbury but arrived Moreton-in-Marsh +25 and was cancelled thereafter "due to a problem with the train (M8)" [RTT].

 
And after some good days, when I've been hesitant to post anything, for fear of something going wrong...

Though yesterday the afternoon 'halts' train was cancelled.

 
Given that the 15:52 left Oxford at 17:23, the scheduled departure time of the 'halts' train, did the 15:52 get given the job of doing the halts calls (instead of the 16:58)? Can't really tell from the RTT reports.

[Later] Looking in more detail at RTT, the 15:52 took 28 minutes from Hanborough to Moreton (scheduled for 24). The 16:58 took 37 (scheduled for 27).  So I think the 16:58 did the halts calls.

Meanwhile, we have the right size of train doing the 'halts' today.

 

And the following service, the 1552 London Paddington to Worcester Shrub Hill train departed Paddington 28 minutes late and left Oxford 38 late.

 

 

Yes, though I think Ascott is OK for a 3-car in that direction.  Shipton, Combe and Finstock definitely aren't.

With local door controls fitted, there's no reason why the TM couldn't do it from a local door if the method of working is altered in a similar fashion to Avoncliffe and others, but it happens so rarely that I don't suppose it's deemed worth it.

 

Certainly does, without selective door opening.

 
Problems between Paddington and Reading this morning.

1W13 06:50 London Paddington to Worcester Shrub Hill (09:04) was +25 at Reading, +17 at Oxford, held at Wolvercote  and Evesham (+52), arrived +58.
Fortunately this one goes out of service at Shrub Hill. It returns to Paddington at 16:53.

1W15 07:50 London Paddington to Worcester Shrub Hill (09:58) was +6 at Oxford but arrived +17.
This one returns to Paddington at 10:16.

 
Tuesday January 28

An odd one this morning - the 'halts' train is running, but not stopping at the halts. The halts stops are on the train behind.


Looking at RTT, there's a three-car Turbo allocated to the 07:00 - does that make it too big for the halts?

 



The Journey Checker obviously read you and added the report at 05:58 

 
Monday January 27

This week there are no trains west of Foregate Street until Saturday.

Today, RTT is reporting that 1P02 0605 Worcester Foregate Street to London Paddington (which normally starts at Hereford) is cancelled throughout this morning, though this is not reported on JourneyCheck. RTT has it running ECS from Shrub Hill (06:10) to Paddington (08:24).

 
Sunday January 26


... leaves a three-hour gap in the service.

 

 
Saturday January 25

1W13 06:52 London Paddington to Great Malvern : departed +34, held Wolvercote, arrived Worcester Shrub Hill +24 and cancelled thereafter.

1P17 08:50 Great Malvern to London Paddington : held Norton (+14), arrived +19.

 
Later:
1W33 16:58 London Paddington to Great Malvern (19:25) : arrived Honeybourne 18:41 (+5), cancelled thereafter. Stock ran ECS to Shrub Hill, departing Honeybourne 20:15, arriving 20:50.
1W03 17:34 London Paddington to Hereford : arrived Moreton 19:05 (+7), departed 20:20 (+81), arrived Great Malvern +83 and cancelled thereafter.
1W34 17:57 Paddington to Worcester Foregate St : Started from Reading, Shipton 19:24 (+7), Kingham 20:21 (+59), arrived Shrub Hill +63 and cancelled thereafter.
1W36 18:57 London Paddington to Great Malvern : Arrived Oxford 19:45 (on time), cancelled thereafter.
1W05 19:53 London Paddington to Hereford : held south of Shrub Hill, arrived Shrub Hill 22:36 (+37), Hereford +33.
1W41 20:52 London Paddington to Great Malvern : held before Norton, arrived Shrub Hill 23:28 (+31), Great Malvern +33.

Stock appears to have run ECS from Shrub Hill (21:18) to Paddington.


Held at Foregate St 22:55-23:22 (+33), arrived +31.

Updated Saturday 12:36.

 
Friday January 24

Storm Eowyn forced a couple of changes to the first trains this morning:

 
Monday to Wednesday January 20-22 were good days.

But today has started with

 
Saturday January 18 was a very good day.

Sunday January 19

It's on RTT as 1W15 08:48 Oxford to Great Malvern, and departed +4.

Arrived +15.

Departed +27, held Wolvercote (+45) and Evesham (+59). Arrived Foregate St +60 and cancelled thereafter.

Reported on RTT as cancelled throughout - "This service was cancelled due to unknown cause (ZW)."

Held Henwick (+10), arrived +25.

 
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!

 

And it caused a lot of disruption further west. RTT 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 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.

 
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.

 
Arrived Oxford on time. Departed +32.


Departed Hereford on time.

 

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.

 
Wednesday January 15

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

 
Morning hassles today because of a broken down train between Worcester Foregate Street and Great Malvern

 
Tuesday January 14

 
Monday January 13 was going well until

1W27 13:50 London Paddington to Great Malvern departed +12, arrived Worcester Shrub Hill +22 and was cancelled thereafter.

 
Sunday January 12

Held at Wolvercote (+31) and Evesham (+53). Arrived Shrub Hill +59 and cancelled thereafter.

Arrived +30.

Held Shrub Hill (+26), arrived +17.

Held Charlbury, arrived +30.



11:40 : updated
14:00 : updated