GWR Bristol - Oxford service

[jimm]

Nothing official, from what I’ve seen, other than GWR have applied to run the services on weekdays+Saturdays. Per my understanding, they’re meant to be 2-hourly, at least to begin with.

As mikestone1952 noticed upthread, RTT does now show ECS moves for this service, at either end of the route, but the actual journey isn’t (yet?) shown.

It’s been mentioned earlier on that this service depends on the introduction of Class 175s elsewhere on the GWR network, because that’s meant to free up some IETs. Don’t know if that’s still the case and/or whether that’s still delaying these Oxford-Bristol services’ introduction.

The current situation is that, as noted above, GWR got the nod from the Department for Transport to bid for the paths needed for a two-houry frequency on weekdays and Saturdays.

The application is with the ORR but its decision is still awaited.

Plus as many 175s as possible need to be in service and operating reliably by May in the South West, to release the IETs needed for this service to start then.

I guess that if that does not happen, a Bristol-Oxford start date may get pushed to September, to ensure the summer timetable is delivered in Devon and Cornwall and that Bristol-Oxford does not go off at half-cock, with multiple cancellations due to lack of IETs.

 

[Railtok]

It feels like we’ve now passed the point where a May timetable launch would realistically be announced. By this stage, you’d normally expect some level of public confirmation if the service was going ahead as planned.

Do people think September is now the more likely target for the Bristol–Oxford service, or could it slip further to the December timetable change? I suppose the key milestone will ultimately be confirmation from the ORR before anything is set in stone.

 

[DelW]

It feels like we’ve now passed the point where a May timetable launch would realistically be announced. By this stage, you’d normally expect some level of public confirmation if the service was going ahead as planned.

Do people think September is now the more likely target for the Bristol–Oxford service, or could it slip further to the December timetable change? I suppose the key milestone will ultimately be confirmation from the ORR before anything is set in stone.

The discussion of the 175's introduction in the Traction forum suggests that it's very unlikely that more than a small handful of those will be in service this summer. GWR is likely to have trouble finding enough stock even to maintain existing services at adequate lengths, so I'd have thought there's almost no chance of any additional services being introduced this summer. I wouldn't put much money on the autumn either, come to that.

 

[John R]

Well some weekday services are starting to appear in the timetable, including this one surprisingly starting at Exeter.

Realtime Trains | 1Z52 0547 Exeter St Davids to Oxford | 27/05/2026

Real-time train running information for 1Z52 0547 departure from Exeter St Davids to Oxford on 27/05/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

(Link is to an early morning service from Exeter St David’s to Oxford on Wed 27th May. )

 

[zwk500]

Well some weekday services are starting to appear in the timetable, including this one surprisingly starting at Exeter.

Realtime Trains | 1Z52 0547 Exeter St Davids to Oxford | 27/05/2026

Real-time train running information for 1Z52 0547 departure from Exeter St Davids to Oxford on 27/05/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

(Link is to an early morning service from Exeter St David’s to Oxford on Wed 27th May. )

1Z Train ID would indicate that's unlikely to be the normal pattern. May well be in the same path from Bristol to Oxford though.

A quick glance at RTT suggests that is an Exeter-Cardiff service amended to terminate at Bristol due to engineering works that weekend and then stuck on to a Bristol-Oxford path.

Notably the next week, the 0547 from Exeter to Bristol just terminates at Temple Meads. https://www.realtimetrains.co.uk/service/gb-nr:G15493/2026-06-04/detailed

 

[John R]

1Z Train ID would indicate that's unlikely to be the normal pattern. May well be in the same path from Bristol to Oxford though.

A quick glance at RTT suggests that is an Exeter-Cardiff service amended to terminate at Bristol due to engineering works that weekend and then stuck on to a Bristol-Oxford path.

Notably the next week, the 0547 from Exeter to Bristol just terminates at Temple Meads. https://www.realtimetrains.co.uk/service/gb-nr:G15493/2026-06-04/detailed

Agree, but either way it’s surely a good sign that Bristol to Oxford paths are starting to appear?

 

[zwk500]

Agree, but either way it’s surely a good sign that Bristol to Oxford paths are starting to appear?

It is and it isn't. It's good that some services are starting to be published. But the base plan is still 2tpd on Saturdays only beyond May.

 

[The exile]

1Z Train ID would indicate that's unlikely to be the normal pattern. May well be in the same path from Bristol to Oxford though.

A quick glance at RTT suggests that is an Exeter-Cardiff service amended to terminate at Bristol due to engineering works that weekend and then stuck on to a Bristol-Oxford path.

Unless there’s some big event on in Oxford that week, it does beg the question as to why there is suddenly a Bristol - Oxford service for that week and no other. Combining 2 existing part services during engineering work is one thing - creating a service that doesn’t exist (and isn’t a diversion) over about 70 miles is another. Useful route retention run, perhaps?

 

[zwk500]

Unless there’s some big event on in Oxford that week, it does beg the question as to why there is suddenly a Bristol - Oxford service for that week and no other. Combining 2 existing part services during engineering work is one thing - creating a service that doesn’t exist (and isn’t a diversion) over about 70 miles is another. Useful route retention run, perhaps?

At a guess, given they're running 2tpd all week, the strategy for managing the reduced capacity caused by the engineering works is to run a plan based on the saturday plan.

 

[John R]

At a guess, given they're running 2tpd all week, the strategy for managing the reduced capacity caused by the engineering works is to run a plan based on the saturday plan.

I don’t understand how that in any way manages reduced capacity through the Severn Tunnel?

 

[zwk500]

I don’t understand how that in any way manages reduced capacity through the Severn Tunnel?

Trains are terminating early at Temple Meads and Parkway in response to the block, which means there's less platform capacity available at those stations. Running the slightly less intense Saturday service helps give a bit more room to flex.
Alterations are still necessary - The Exeter train linked is missing normal stops at Parson Street and Bedminster to meet the Oxford path, for instance - and there will presumably be GWR diversions via Gloucester causing changes at that end, so any services that pass through Cheltenham/Gloucester and Bristol may need flexing at both points.

 

[Laserbeam31]

Does anybody know what it is about this particular route that seems to make the train’s onboard computer struggle when it comes to the reservation/information displays?

I think every time I’ve been on this service (today being no exception) the seat reservation displays have been blank, even though reservations are available on the GWR website. Also for most of the first year they ran it, the destination displays for the Oxford-bound services would always read “Reading”.

Is it something to do with the train using the Didcot West curve, which isn’t normally used for passenger traffic?

 

[Snow1964]

Does anybody know what it is about this particular route that seems to make the train’s onboard computer struggle when it comes to the reservation/information displays?

I think every time I’ve been on this service (today being no exception) the seat reservation displays have been blank, even though reservations are available on the GWR website. Also for most of the first year they ran it, the destination displays for the Oxford-bound services would always read “Reading”.

Is it something to do with the train using the Didcot West curve, which isn’t normally used for passenger traffic?

This question has come up before. It seems that when the IETs were specified, a list of routes was specified, this was fixed in the software, and this would have to be updated (expensively) to add the route.

Seems someone thought it would be good idea to define limited route options (without provision for updating at no cost) for a train with about 40 year life that might move routes. Why is a mystery to me.

 

[Siemens Staines]

165136 is currently allocated on RTT to work todays Bristol to Oxford diagram

1N58 1018 Bristol Temple Meads to Oxford
1N61 1202 Oxford to Bristol Temple Meads
1N68 1518 Bristol Temple Meads to Oxford
1N71 1712 Oxford to Bristol Temple Meads

 

[officewalla]

Only 1 link at Paddington and 1 Link at Oxford sign the West Curve at Didcot, the majority of those drivers have in their T and C’s the ability to throw in their Sunday’s hence staff coverage is the main problem

Not quite true as there are no HSS drivers at Oxford (all on committed Sundays) and all drivers should sign the west curve as there is a weekly diagram to maintain competency and it it is assessed during pass out.

 

[800301]

Not quite true as there are no HSS drivers at Oxford (all on committed Sundays) and all drivers should sign the west curve as there is a weekly diagram to maintain competency and it it is assessed during pass out.

Yeah sorry my bad, all Oxford divers sign the curve but only 1 link sign Swindon so the other drivers aren’t much help, I knew the Sunday agreement was different at Oxford but not exactly what it it, if you were at Paddington pre GWR harmonisation regardless of being HSS or LTV you can still throw your Sundays in

 

[II]

Does anybody know what it is about this particular route that seems to make the train’s onboard computer struggle when it comes to the reservation/information displays?

I think every time I’ve been on this service (today being no exception) the seat reservation displays have been blank, even though reservations are available on the GWR website. Also for most of the first year they ran it, the destination displays for the Oxford-bound services would always read “Reading”.

Is it something to do with the train using the Didcot West curve, which isn’t normally used for passenger traffic?

I believe the next software update for the TMS (v96.4) being rolled out to the fleet over the coming weeks should solve this issue.

Not a huge issue with only two trains each way per week at the moment, but when the full service commences it would be and will hopefully be resolved by then.

 

[Nicholas43]

There are no through trains Bristol<>Oxford, on any day of the week, in the published timetables from 17 May 2026.

 

[TheLastMinute]

There are no through trains Bristol<>Oxford, on any day of the week, in the published timetables from 17 May 2026.

GWR is still waiting for ORR to approve allocation of the paths.

 

[John R]

GWR is still waiting for ORR to approve allocation of the paths.

Maybe they will approve them but only as empty stock moves…

 

[brad465]

There are no through trains Bristol<>Oxford, on any day of the week, in the published timetables from 17 May 2026.

There are quite a few services on Saturday 13th June, although more in the down direction (towards Bristol) than the Up. However, I couldn't find anything obvious beyond that on any other day.

Realtime Trains | 1N54 0811 Bristol Temple Meads to Oxford | 13/06/2026

Real-time train running information for 1N54 0811 departure from Bristol Temple Meads to Oxford on 13/06/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Realtime Trains | 1N61 1202 Oxford to Bristol Temple Meads | 13/06/2026

Real-time train running information for 1N61 1202 departure from Oxford to Bristol Temple Meads on 13/06/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Realtime Trains | 1N65 1401 Oxford to Bristol Temple Meads | 13/06/2026

Real-time train running information for 1N65 1401 departure from Oxford to Bristol Temple Meads on 13/06/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Realtime Trains | 1N69 1602 Oxford to Bristol Temple Meads | 13/06/2026

Real-time train running information for 1N69 1602 departure from Oxford to Bristol Temple Meads on 13/06/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Realtime Trains | 1N73 1802 Oxford to Bristol Temple Meads | 13/06/2026

Real-time train running information for 1N73 1802 departure from Oxford to Bristol Temple Meads on 13/06/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

Realtime Trains | 1N78 1855 Exeter St Davids to Oxford | 13/06/2026

Real-time train running information for 1N78 1855 departure from Exeter St Davids to Oxford on 13/06/2026. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

 

[Snow1964]

The ORR has now published its response

Rather lot of caveats, that seem to allow a temporary limited two hourly service subject to work on 13 level crossings. Seems Network Rail wanted £1.75m to update existing crossings used by other trains. (Shades of Network Rail expecting paid for crossing upgrades in Go-Op application).

Why these level crossings are acceptable now, and don't need improvement unless there is same type of train going to different destination is a mystery to me.

Summary section 41 basically says

We will direct the parties to enter into a supplementary agreement (SA), however based on the evidence provided the additional two hourly GWR service should only be introduced once the reasonably practical measures identified by Network Rail in its representations or alternatives achieving an equivalent effect have been implemented

https://www.orr.gov.uk/sites/default/files/2026-05/gwr-section-22a-301st-supplemental-agreement-directions-letter-2026-05-05.pdf

 

[Benjwri]

Why these level crossings are acceptable now, and don't need improvement unless there is same type of train going to different destination is a mystery to me.

Higher frequency of trains crossing will have changed the risk assessment and mean that they are deemed unsafe.

Of course I’m sure there might be some wiggle room that’s normally used not being so here, where someone else is paying.

 

[-Colly405-]

Surely, its no higher frequency that the short-lived Dec 2019 timetable with its superfasts?

 

[zwk500]

Surely, its no higher frequency that the short-lived Dec 2019 timetable with its superfasts?

Presumably road traffic has also risen in the meantime?

 

[Snow1964]

Presumably road traffic has also risen in the meantime?

More like a risk assessor has moved the goalposts.

And Network Rail is quite happy to continue the current condition of those crossings , although if it can get someone else to pay for an upgrade, that NR hasn't deemed necessary until now, then it is misusing and chancing it as a reason to object

 

[fishwomp]

Rather lot of caveats, that seem to allow a temporary limited two hourly service subject to work on 13 level crossings. Seems Network Rail wanted £1.75m to update existing crossings used by other trains. (Shades of Network Rail expecting paid for crossing upgrades in Go-Op application).

[..]

So no chance of happening for the start of the timetable, looks like they're installing warning devices at several crossings first.

 

[43074]

More like a risk assessor has moved the goalposts.

And Network Rail is quite happy to continue the current condition of those crossings , although if it can get someone else to pay for an upgrade, that NR hasn't deemed necessary until now, then it is misusing and chancing it as a reason to object

Shocking allegation, as if Network Rail would use tenuous reasons to explain why something shouldn't be done (/sarcasm)

 

[GilfachFargoed]

Surely, its no higher frequency that the short-lived Dec 2019 timetable with its superfasts?

The half-hourly 'superfast' services were timetabled to run via Bristol Parkway and Hullavington and would therefore have interacted with a different subset of crossings (many of the 13 must be foot crossings, or at least I can only recall road crossings at Steventon and just south of Appleford on this route).

 

[Wychwood93]

The half-hourly 'superfast' services were timetabled to run via Bristol Parkway and Hullavington and would therefore have interacted with a different subset of crossings (many of the 13 must be foot crossings, or at least I can only recall road crossings at Steventon and just south of Appleford on this route).

The road crossings are Causeway and Stocks Lane, just west of Steventon and Appleford.