Thought London’s strikes were limited to our train network? Think again. Alongside the industrial action planned for the capital’s rail services in May (read more about that here), today (April 29) more strikes have just been announced for London’s bus network.
Several bus routes, primarily in southwest London, will be affected by strike action from control rooms workers employed by Transport UK (previously known as Abellio). The 40 controllers, whose job it is to instruct drivers on accidents and traffic jams, ensuring buses run on time, work in Battersea and Twickenham.
The strikes follow six dates of action by the same workers in January and February, and eight days in March. The next round of strikes will take place in May 2024 – here’s everything you need to know.
When are the London bus strikes?
The strikes will take place on May 8, 9 and 10 and then from May 13-17.
Which bus routes will be affected?
Quite a few routes are set to be disrupted, all based at Battersea and Twickenham bus garages. The most notable routes likely to be impacted are the 24, 27, 111, 156, 159, 267, 285, 322, 344, 345, 415, 490, 969, H20, H25, H26, R68 and R70.
TfL says that these routes will be running on strike days, but that they will likely be busier than usual.
Why are bus control room staff striking?
Workers are striking as part of an ongoing pay dispute. According to Unite, Transport UK (FKA Abellio) control room staff were offered just a 5 percent pay rise for 2023, which the union called a ‘substantial real-terms pay cut’.
Unite also says these workers already earn up to £10,000 less a year than similar staff at other bus companies.
Are there other public transport strikes planned in London?
Yep, there most certainly are. Further strikes are set to take place on train networks across the UK from May 7-9 (you can find out more about those strikes here) and there are currently strikes by border force staff at Heathrow.
Stay in the loop: sign up for our free Time Out London newsletter for the best of the city, straight to your inbox.
0 Comments