[bhuber]

This phenomenon consistently happened to my college bus system, but on an even worse scale. The main bus line did a loop around campus, which took ~20 min to complete and buses scheduled every 5 minutes. In reality, you got a caravan of 4 busses arriving every 20 minutes, with the first one totally full and the last practically empty.

[theluketaylor]

When I was a teen in Calgary the transit agency was really good at dealing with issues like this during peak periods. They would pair or triple busses together and alternate stops. If someone requested the stop the drivers would radio to coordinate. Sometimes both buses would have a requested stop, but they would work together so only one bus allowed new riders on. The non-loading bus would quickly drop off passengers and leave while the other stayed behind to handle new riders. Nearly all the stops had dedicated out of traffic space for the bus, so the leap-frog maneuver was really simple. A small amount of low cost infrastructure and some operational cooperation enabled much better service.

[a_e_k]

Another simple strategy that I've seen is simply for the loaded bus to allow the empty bus to overtake it and go on ahead (and just stay ahead).

[rvb]

This phenomenon is called "bus bunching". My friends, two profs from Georgia Tech and UChicago, came up with one solution for it. They wrote a paper about their solution[1], and then built a startup that has successfully implemented it at a bunch of places[2].

[1]: [A self-coördinating bus route to resist bus bunching](https://doi.org/10.1016%2Fj.trb.2011.11.001)

[2]: [NAU’s new bus system makes for shorter wait times for riders](https://news.nau.edu/nau-bus-schedules/)

[occz]

That's interesting.

Looking at the second link, it seems they implement it by having the buses pause at certain points. Does it do that with riders onboard? That seems like it could be a deterioration in experience for those riders that are on the bus pausing.