1
To Manchester_Piccadilly_Rail_Station
Bee Network · BU75WLA
CompletedRefreshed 21:03:18
Vehicle information
BU75WLA
- 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 Stationp1800EB07051Plan07:15Actual07:18
- 2Piccadilly1800EB06161Plan07:16Actual07:21
- 3Charlotte Street1800SB04791Plan07:18Actual07:23
- 4Hart Street1800SB04961Plan07:19Actual07:24
- 5Palace Theatre1800SB09171Plan07:21Actual07:25
- 6Oxford Road Station1800SB12101Plan07:22Actual07:25
- 7Gloucester Street1800SB05911Plan07:23Actual07:26
- 8Deansgate Station1800SB12261Plan07:25Actual07:28
- 9Barton Street1800NB29921Plan07:26Actual07:29
- 10Science Museum1800SB09201Plan07:27Actual07:30
- 11Lower Byrom Street1800SB09671Plan07:28Actual07:32
- 12Manchester Crown Court1800SB10121Plan07:29Actual07:33
- 13Deansgate1800NB03521Plan07:31Actual07:34
- 14St James Square1800SB05781Plan07:32Actual07:35
- 15Cheapside1800SB05801Plan07:33Actual07:37
- 16George Street1800SB17081Plan07:35Actual07:39
- 17Chorlton Street Coach Station1800SB04801Plan07:37Actual07:41
- 18Sheena Simon Campus1800SB04811Plan07:37Actual07:41
- 19Minshull Street1800SB12411Plan07:38Actual07:43
- 20Manchester Piccadilly Rail Stations1800EB00011Plan07:40Actual07:46
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 07:46.
- When did it begin?
- Observed at 07:18
- When should it finish?
- Observed at 07:46
- How much time remains?
- No time remains; the final stop has been observed.
- When was it last mapped?
- 07:46. The page checks for updated journey data every 15 seconds.