1
To Manchester Piccadilly Rail Station
Bee Network · BU75WKZ
CompletedRefreshed 16:36:04
Vehicle information
BU75WKZ
- 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-08. Changing the date opens the parent service timetable.
Calling points
Journey schedule
- 1Manchester Piccadilly Rail Stationp1800EB07051Plan11:05Actual11:04
- 2Piccadilly1800EB06161Plan11:06Actual11:06
- 3Charlotte Street1800SB04791Plan11:08Actual11:08
- 4Hart Street1800SB04961Plan11:09Actual11:09
- 5Palace Theatre1800SB09171Plan11:11Actual11:11
- 6Oxford Road Station1800SB12101Plan11:12Actual11:11
- 7Gloucester Street1800SB05911Plan11:13Actual11:12
- 8Deansgate Station1800SB12261Plan11:15Actual11:15
- 9Barton Street1800NB29921Plan11:16Actual11:16
- 10Science Museum1800SB09201Plan11:18Actual11:18
- 11Lower Byrom Street1800SB09671Plan11:19Actual11:19
- 12Manchester Crown Court1800SB10121Plan11:21Actual11:20
- 13Deansgate1800NB03521Plan11:23Actual11:20
- 14St James Square1800SB05781Plan11:24Actual11:23
- 15Cheapside1800SB05801Plan11:26Actual11:24
- 16George Street1800SB17081Plan11:29Actual11:27
- 17Chorlton Street Coach Station1800SB04801Plan11:31Actual11:29
- 18Sheena Simon Campus1800SB04811Plan11:32Actual11:29
- 19Minshull Street1800SB12411Plan11:33Actual11:30
- 20Manchester Piccadilly Rail Stations1800EB00011Plan11:35Actual11:31
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 11:31.
- When did it begin?
- Observed at 11:04
- When should it finish?
- Observed at 11:31
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 11:34. The page checks for updated journey data every 15 seconds.