1
To Manchester_Piccadilly_Rail_Station
Bee Network · BU75WKP
CompletedRefreshed 04:30:52
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-09. Changing the date opens the parent service timetable.
Calling points
Journey schedule
- 1Manchester Piccadilly Rail Stationp1800EB07051Plan07:55Actual07:54
- 2Piccadilly1800EB06161Plan07:56Actual07:58
- 3Charlotte Street1800SB04791Plan07:58Actual08:00
- 4Hart Street1800SB04961Plan07:59Actual08:01
- 5Palace Theatre1800SB09171Plan08:01Actual08:02
- 6Oxford Road Station1800SB12101Plan08:02Actual08:03
- 7Gloucester Street1800SB05911Plan08:03Actual08:04
- 8Deansgate Station1800SB12261Plan08:05Actual08:06
- 9Barton Street1800NB29921Plan08:06Actual08:07
- 10Science Museum1800SB09201Plan08:08Actual08:09
- 11Lower Byrom Street1800SB09671Plan08:09Actual08:09
- 12Manchester Crown Court1800SB10121Plan08:11Actual08:12
- 13Deansgate1800NB03521Plan08:13Actual08:12
- 14St James Square1800SB05781Plan08:14Actual08:14
- 15Cheapside1800SB05801Plan08:16Actual08:16
- 16George Street1800SB17081Plan08:18Actual08:18
- 17Chorlton Street Coach Station1800SB04801Plan08:20Actual08:19
- 18Sheena Simon Campus1800SB04811Plan08:21Actual08:19
- 19Minshull Street1800SB12411Plan08:22Actual08:22
- 20Manchester Piccadilly Rail Stations1800EB00011Plan08:24Actual08:23
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:23.
- When did it begin?
- Observed at 07:54
- When should it finish?
- Observed at 08:23
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 08:23. The page checks for updated journey data every 15 seconds.