1
To Manchester_Piccadilly_Rail_Station
Bee Network · BU75WKV
CompletedRefreshed 18:21:19
Vehicle information
BU75WKV
- 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 Stationp1800EB07051Plan14:15Actual14:14
- 2Piccadilly1800EB06161Plan14:16Actual14:18
- 3Charlotte Street1800SB04791Plan14:18Actual14:20
- 4Hart Street1800SB04961Plan14:19Actual14:22
- 5Palace Theatre1800SB09171Plan14:21Actual14:22
- 6Oxford Road Station1800SB12101Plan14:22Actual14:23
- 7Gloucester Street1800SB05911Plan14:23Actual14:24
- 8Deansgate Station1800SB12261Plan14:25Actual14:26
- 9Barton Street1800NB29921Plan14:26Actual14:26
- 10Science Museum1800SB09201Plan14:28Actual14:28
- 11Lower Byrom Street1800SB09671Plan14:29Actual14:31
- 12Manchester Crown Court1800SB10121Plan14:30Actual14:32
- 13Deansgate1800NB03521Plan14:32Actual14:35
- 14St James Square1800SB05781Plan14:33Actual14:36
- 15Cheapside1800SB05801Plan14:35Actual14:37
- 16George Street1800SB17081Plan14:37Actual14:39
- 17Chorlton Street Coach Station1800SB04801Plan14:39Actual14:41
- 18Sheena Simon Campus1800SB04811Plan14:40Actual14:42
- 19Minshull Street1800SB12411Plan14:41Actual14:42
- 20Manchester Piccadilly Rail Stations1800EB00011Plan14:43Actual14:45
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 14:45.
- When did it begin?
- Observed at 14:14
- When should it finish?
- Observed at 14:45
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 14:45. The page checks for updated journey data every 15 seconds.