This tool runs the same model as the bus stop proposal, on the stops you choose. Close the stops the model suggests and you get that page’s numbers for the route.
- Saved on boardEach stop closed saves a bus 11 seconds, for every rider aboard as it passes (the default; the assumptions menu has the others). 11 s is what the Bronx redesign of 2022 actually gained; Queens (2025) got about 4 s, the MTA plans on 20 s. Riders aboard at any point = the route’s weekday boardings × 2 miles (an average bus trip) ÷ route length.
- Extra walkingPeople at a closed stop, boarding and getting off, walk to the nearest open stop at 3 mph. They are spread evenly along the street between the stop’s neighbours, so some live closer to the next stop already. Walking counts double in the net, the usual weight for time out of the vehicle.
- Riders at a stopThe MTA does not publish boardings by stop. We split a route’s weekday boardings (data.ny.gov, March to August 2026) between its two directions by scheduled trips, then evenly over its stops. A busy stop will cost more walking than shown, a quiet one less. The control above the result sets the closed stops at half the route’s average, the case the bus stop proposal rests on (quiet stops), or at the average.
- The model’s picksSuggest stops repeats the rule from the bus stop proposal: close the stop that leaves spacing most even, until no gap is under the minimum. It never closes the end of a line, a stop within 100 m of a subway station, or one where two other routes cross, and never leaves a gap over twice the minimum. Express routes are left out.
Caveats: the net counts rider-hours only. It leaves out what a faster bus saves the MTA, and what a longer walk costs older riders and riders with disabilities, which no average captures. Stops you close are not checked against that: you can close one the model would keep, or leave a gap the model would not. The stop timetable is the usual weekday pattern of ; a route’s real stops on a given day can differ.