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