1
To Manchester_Piccadilly_Rail_Station
Bee Network · BU75WKP
CompletedRefreshed 00:07:38
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 Stationp1800EB07051Plan12:35Actual12:34
- 2Piccadilly1800EB06161Plan12:36Actual12:37
- 3Charlotte Street1800SB04791Plan12:38Actual12:40
- 4Hart Street1800SB04961Plan12:39Actual12:41
- 5Palace Theatre1800SB09171Plan12:41Actual12:42
- 6Oxford Road Station1800SB12101Plan12:42Actual12:43
- 7Gloucester Street1800SB05911Plan12:43Actual12:45
- 8Deansgate Station1800SB12261Plan12:45Actual12:47
- 9Barton Street1800NB29921Plan12:46Actual12:49
- 10Science Museum1800SB09201Plan12:48Actual12:51
- 11Lower Byrom Street1800SB09671Plan12:49Actual12:52
- 12Manchester Crown Court1800SB10121Plan12:51Actual12:53
- 13Deansgate1800NB03521Plan12:53Actual12:54
- 14St James Square1800SB05781Plan12:54Actual12:56
- 15Cheapside1800SB05801Plan12:56Actual12:59
- 16George Street1800SB17081Plan12:58Actual13:00
- 17Chorlton Street Coach Station1800SB04801Plan13:00Actual13:02
- 18Sheena Simon Campus1800SB04811Plan13:01Actual13:02
- 19Minshull Street1800SB12411Plan13:02Actual13:03
- 20Manchester Piccadilly Rail Stations1800EB00011Plan13:04Actual13:04
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:04.
- When did it begin?
- Observed at 12:34
- When should it finish?
- Observed at 13:04
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 13:04. The page checks for updated journey data every 15 seconds.