1
To Manchester_Piccadilly_Rail_Station
Bee Network · BU75WKP
CompletedRefreshed 06:29:32
Vehicle information
BU75WKP
- 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 Stationp1800EB07051Plan08:45Actual08:45
- 2Piccadilly1800EB06161Plan08:46Actual08:49
- 3Charlotte Street1800SB04791Plan08:48Actual08:51
- 4Hart Street1800SB04961Plan08:49Actual08:53
- 5Palace Theatre1800SB09171Plan08:51Actual08:55
- 6Oxford Road Station1800SB12101Plan08:52Actual08:56
- 7Gloucester Street1800SB05911Plan08:53Actual08:57
- 8Deansgate Station1800SB12261Plan08:55Actual08:59
- 9Barton Street1800NB29921Plan08:56Actual09:01
- 10Science Museum1800SB09201Plan08:58Actual09:02
- 11Lower Byrom Street1800SB09671Plan09:00Actual09:04
- 12Manchester Crown Court1800SB10121Plan09:02Actual09:06
- 13Deansgate1800NB03521Plan09:04Actual09:07
- 14St James Square1800SB05781Plan09:05Actual09:09
- 15Cheapside1800SB05801Plan09:08Actual09:10
- 16George Street1800SB17081Plan09:10Actual09:12
- 17Chorlton Street Coach Station1800SB04801Plan09:12Actual09:14
- 18Sheena Simon Campus1800SB04811Plan09:13Actual09:15
- 19Minshull Street1800SB12411Plan09:15Actual09:17
- 20Manchester Piccadilly Rail Stations1800EB00011Plan09:17Actual09:19
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 09:19.
- When did it begin?
- Observed at 08:45
- When should it finish?
- Observed at 09:19
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 09:23. The page checks for updated journey data every 15 seconds.