500
To Winnersh Triangle Railway Station
Reading Buses · YR14CFZ
Last observedRefreshed 05:21:36
We don’t have a recent location for this bus. The marker shows where it was last reported, not where it is now.
Vehicle information
YR14CFZ
- Operator
- Reading Buses
- Vehicle
- Open vehicle profile
- Livery
- Winnersh Triangle Park & Ride
- Matched vehicle livery
- Live data provider
- Department for Transport Bus Open Data Service
Browse service date
This journey ID is fixed to 8 Sept 2026. Changing the date opens the parent service timetable.
Calling points
Journey schedule
- 1Minster Streetp039026690004Plan17:17Seen at stop17:25
- 2St Marys Butts039027320004Plan17:19Seen at stop17:28
- 3Friar Street039026100005Plan17:21Expected—
- 4Blagrave Street039028150002Plan17:22Seen at stop17:35
- 5Market Place039026630003Plan17:23Seen at stop17:39
- 6Huntley and Palmers039026410004Plan17:25Seen at stop17:41
- 7Eldon Road039025980002Plan17:25Seen at stop17:42
- 8Reading College039027450002Plan17:26Seen at stop17:43
- 9Cemetery Junction039025480003Plan17:27Seen at stop17:45
- 10Cholmeley Road039025550001Plan17:27Seen at stop17:46
- 11Liverpool Road039026570001Plan17:28Seen at stop17:47
- 12Winnersh Triangle Railway Stations035087100001Plan17:40Expected—
p “pick up only” – the bus will only stop to pick up passengers
s “set down only” – the bus will only stop to drop passengers off
Seen at stop is when the operator reported the bus at or near that stop, not its exact arrival time. Expected times are estimates. A dash means no time has been reported.
Planned, expected and observed values remain separate. Blank observations are never presented as on-time.
Journey status questions
What is happening?
- Is the bus running?
- Last observed. A previous vehicle observation is available, but it is not recent enough to call the bus live.
- When did it begin?
- Scheduled for 17:17
- When should it finish?
- Scheduled for 17:40
- How much time remains?
- A reliable remaining-time estimate is unavailable.
- When was it last mapped?
- 17:52. The page checks for updated journey data every 15 seconds.