Also very true from a Cotswold point-of-view. The GWR superfasts absolutely trashed the commuter service between Reading and the Cotswolds, with just one direct train between 1630 and 2000. I'm very pleased to see them added to the "let's just forget that happened, shall we?" pile.
Edit: I presume that applies to the Stroud/Cheltenham line too - right now there's a 1553 departure from Reading to Cheltenham, then two running through fast, meaning the next direct service is 1855.
But there will still be a gap in direct trains from Reading to the Cotswold Line in key commuter time between 16.19 and 18.00, with the only options on offer being the 16.48 to Oxford and a change to the halts train (so no use to anyone going to Worcestershire) or the 17.15 XC to Oxford, changing on to the 16.58 from Paddington to Great Malvern.
If XC is still going to turn out a pair of Voyagers for the 17.15 service, that would not be too bad from a passenger loading post of view (the wider passenger experience on a Voyager these days is another matter), but if the extension of this service from Birmingham to Manchester from May is accompanied by the resumption of operation with a single set, then it will again become the full and standing scrum it was prior to March 2020.
And having used the 17.15 & change at Oxford combination this Monday, I couldn't help thinking that making the 16.58 from Paddington pick up only at Reading - backed up by a wave of full ticket checks straight after departure from Paddington to deter any smart alec Reading commuters - might be the way forward, as the IET reached Oxford with seats to spare. I assume it is a bit busier with Tuesday to Thursday commuters and 'weekend away' travel on Fridays, but I haven't used it on any of those days recently.
And before anyone says 'headway behind the 387 semi-fast to Didcot and following Bristol service means you cannot stop at Reading' - one of the excuses used in 2019 - let's look at what will happen from May:
- The 387 running in front of the 16.58 on the main line as far as Maidenhead leaves at 16.50, with the Bristol departure at 17.00, instead of the current 17.02.
- The 17.57 departure will call at Reading after leaving Paddington just six minutes behind the 17.51 to Didcot, while the following Bristol service leaves at 18.01.
- Then the 18.57, also calling at Reading, will be preceded by an 18.50 to Didcot, while the Bristol departure is at 19.02.
The West Country departures following the Bristol services also jump around by a minute or two.
I would be interested to know whether anyone can provide an explanation for these variations in a supposedly standard timetable pattern.
Cheltenham-bound services will indeed call at Reading at xx.5x through the late afternoon and early evening peak period.