1
To Manchester Piccadilly Rail Station
Bee Network · BU75WKZ
CompletedRefreshed 18:13:06
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 Stationp1800EB07051Plan13:05Actual13:04
- 2Piccadilly1800EB06161Plan13:06Actual13:09
- 3Charlotte Street1800SB04791Plan13:08Actual13:11
- 4Hart Street1800SB04961Plan13:09Actual13:12
- 5Palace Theatre1800SB09171Plan13:11Actual13:13
- 6Oxford Road Station1800SB12101Plan13:12Actual13:14
- 7Gloucester Street1800SB05911Plan13:13Actual13:14
- 8Deansgate Station1800SB12261Plan13:15Actual13:16
- 9Barton Street1800NB29921Plan13:16Actual13:17
- 10Science Museum1800SB09201Plan13:18Actual13:18
- 11Lower Byrom Street1800SB09671Plan13:19Actual13:19
- 12Manchester Crown Court1800SB10121Plan13:20Actual13:21
- 13Deansgate1800NB03521Plan13:22Actual13:24
- 14St James Square1800SB05781Plan13:23Actual13:25
- 15Cheapside1800SB05801Plan13:25Actual13:28
- 16George Street1800SB17081Plan13:27Actual13:30
- 17Chorlton Street Coach Station1800SB04801Plan13:29Actual13:31
- 18Sheena Simon Campus1800SB04811Plan13:30Actual13:31
- 19Minshull Street1800SB12411Plan13:31Actual13:33
- 20Manchester Piccadilly Rail Stations1800EB00011Plan13:33Actual13:34
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 13:34.
- When did it begin?
- Observed at 13:04
- When should it finish?
- Observed at 13:34
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 13:34. The page checks for updated journey data every 15 seconds.