82
To Sholver_Terminus
Bee Network · MX09AOY
CompletedRefreshed 19:46:41
Vehicle information
MX09AOY
- Operator
- Bee Network
- Vehicle
- Open vehicle profile
- Livery
- Bee Network
- Matched vehicle livery
- Live data provider
- Department for Transport Bus Open Data Service
This journey ID is fixed to 2026-09-07. Changing the date opens the parent service timetable.
Calling points
Journey schedule
- 1Oldham Bus Stationp1800OMBS0C1Plan12:40Actual12:39
- 2Fairbottom Street1800ED15041Plan12:45Actual12:43
- 3Scholes Street1800ED15081Plan12:46Actual12:44
- 4Oldham Mumps Interchange1800ED15151Plan12:48Actual12:47
- 5Castlemill Street1800ED15901Plan12:48Actual12:50
- 6Barry Street1800ED15941Plan12:49Actual12:51
- 7Hill Street1800ED18601Plan12:50Actual12:52
- 8Hill Stores1800ED03521Plan12:50Actual12:53
- 9Hill Stores1800ED10901Plan12:51Actual12:54
- 10Vulcan Street1800ED10931Plan12:52Live—
- 11Otago Street1800ED10951Plan12:53Actual12:56
- 12Counthill Road1800ED10961Plan12:53Actual12:57
- 13Radcliffe Road1800ED10971Plan12:54Live—
- 14Highfield Terrace1800ED11001Plan12:56Actual12:58
- 15Turf Pit Lane1800ED30521Plan12:57Actual12:59
- 16The Moorside1800ED12821Plan12:58Actual13:00
- 17Sholver Lane1800ED12781Plan12:59Actual13:01
- 18Wells Road1800ED12671Plan13:00Actual13:02
- 19St Thomas1800ED12701Plan13:01Actual13:03
- 20Stevenson Drive1800ED12721Plan13:02Actual13:04
- 21Wilkes Street1800ED12741Plan13:03Actual13:05
- 22Sholver Terminuss1800ED12771Plan13:05Actual13:05
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
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?
- Completed. The final calling point has an observed time of 13:05.
- When did it begin?
- Observed at 12:39
- When should it finish?
- Observed at 13:05
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 13:05. The page checks for updated journey data every 15 seconds.