500
To Winnersh Triangle Railway Station
Reading Buses · YR14CFZ
Last observedRefreshed 23:12:54
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 Streetp039026690004Plan08:15Expected—
- 2St Marys Butts039027320004Plan08:17Seen at stop08:20
- 3Friar Street039026100005Plan08:19Expected—
- 4Blagrave Street039028150002Plan08:20Seen at stop08:27
- 5Market Place039026630003Plan08:21Seen at stop08:28
- 6Huntley and Palmers039026410004Plan08:22Seen at stop08:29
- 7Eldon Road039025980002Plan08:23Seen at stop08:31
- 8Reading College039027450002Plan08:24Seen at stop08:31
- 9Cemetery Junction039025480003Plan08:24Seen at stop08:33
- 10Cholmeley Road039025550001Plan08:25Seen at stop08:35
- 11Liverpool Road039026570001Plan08:26Seen at stop08:37
- 12Winnersh Triangle Railway Stations035087100001Plan08:37Seen at stop08:43
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 08:15
- When should it finish?
- Scheduled for 08:37
- How much time remains?
- A reliable remaining-time estimate is unavailable.
- When was it last mapped?
- 08:43. The page checks for updated journey data every 15 seconds.