409
To Ashton_under_Lyne_Interchange
Bee Network · MF26ECW
CompletedRefreshed 21:51:06
Vehicle information
MF26ECW
- 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-10. Changing the date opens the parent service timetable.
Calling points
Journey schedule
- 1Oldham Bus Stationp1800OMWS0K1Plan07:26Actual07:25
- 2Barn Street1800ED15361Plan07:27Actual07:26
- 3Primrose Bank1800ED28301Plan07:29Actual07:30
- 4Lee Street1800ED28321Plan07:30Actual07:31
- 5Villa Road1800ED28351Plan07:31Actual07:32
- 6Honeywell Lane1800ED28361Plan07:32Live—
- 7Hathershaw Lane1800ED28551Plan07:33Actual07:32
- 8Bellfield Avenue1800ED27851Plan07:33Actual07:33
- 9Pelham Street1800ED28571Plan07:35Actual07:35
- 10Park Lane1800ED28581Plan07:35Actual07:35
- 11Coal Pit Lane1800ED28611Plan07:36Actual07:36
- 12Keb Lane1800ED28631Plan07:36Live—
- 13Victoria Street1800ED28651Plan07:37Actual07:37
- 14Oldham Road1800EH21561Plan07:38Actual07:38
- 15Tree House Avenue1800EH21531Plan07:39Live—
- 16Downshaw Road1800EH21521Plan07:39Actual07:39
- 17Anglesey Road1800EH20991Plan07:40Actual07:40
- 18Wilshaw Lane1800EH20971Plan07:41Actual07:41
- 19Atlas Street1800EH20961Plan07:41Actual07:41
- 20Christ Church1800EH20931Plan07:42Actual07:42
- 21Taunton Road1800EH20911Plan07:42Actual07:43
- 22Ashton-under-Lyne Interchanges1800ANINAR1Plan07:44Actual07: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
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 07:43.
- When did it begin?
- Observed at 07:25
- When should it finish?
- Observed at 07:43
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 07:43. The page checks for updated journey data every 15 seconds.