1
To Manchester_Piccadilly_Rail_Station
Bee Network · BU25YYG
CompletedRefreshed 12:37:09
Vehicle information
BU25YYG
- 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
- 1Manchester Piccadilly Rail Stationp1800EB07051Plan07:45Actual07:45
- 2Piccadilly1800EB06161Plan07:46Actual07:49
- 3Charlotte Street1800SB04791Plan07:48Actual07:50
- 4Hart Street1800SB04961Plan07:49Actual07:51
- 5Palace Theatre1800SB09171Plan07:51Actual07:52
- 6Oxford Road Station1800SB12101Plan07:52Actual07:53
- 7Gloucester Street1800SB05911Plan07:53Actual07:54
- 8Deansgate Station1800SB12261Plan07:55Actual07:56
- 9Barton Street1800NB29921Plan07:56Actual07:58
- 10Science Museum1800SB09201Plan07:58Actual07:59
- 11Lower Byrom Street1800SB09671Plan07:59Actual08:00
- 12Manchester Crown Court1800SB10121Plan08:01Actual08:02
- 13Deansgate1800NB03521Plan08:03Actual08:03
- 14St James Square1800SB05781Plan08:04Actual08:06
- 15Cheapside1800SB05801Plan08:06Actual08:07
- 16George Street1800SB17081Plan08:08Actual08:08
- 17Chorlton Street Coach Station1800SB04801Plan08:10Actual08:10
- 18Sheena Simon Campus1800SB04811Plan08:11Actual08:11
- 19Minshull Street1800SB12411Plan08:12Actual08:13
- 20Manchester Piccadilly Rail Stations1800EB00011Plan08:14Actual08:14
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 08:14.
- When did it begin?
- Observed at 07:45
- When should it finish?
- Observed at 08:14
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 08:14. The page checks for updated journey data every 15 seconds.