On November 1, 2026, the New York City subway recorded its busiest Sunday on record. Ridership reached 3.14 million trips, up 11% from the previous year’s marathon day. NYC Transit ran extra subway service and deployed additional staff at stations near the finish line and other popular viewing locations.
On a day like this, a typical Sunday average is a useful baseline for measuring how unusual the demand was. It’s a poor guide for deciding where to run extra trains or deploy staff. A station near the start might see a sharp morning peak, while stations near the finish could stay busy for hours. Even a record systemwide total can hide those differences.
That’s why data from previous marathon days is essential. Comparing several editions by station and time of day helps planners see which peaks recur, how long they last, and where demand is changing. Race schedules, route changes, and planned disruptions can help explain why one year looked different from another.
A post-event review could start with three questions:
– Where and when did demand peak? Compare station entries with previous marathon days, using a typical Sunday as a reference.
– Did extra service match those peaks? Compare planned and actual train frequencies at the busiest stations, and check for long gaps between trains.
– What would you change next time? Decide whether to start extra service earlier, run it longer, or move staff to a different station.
With Zightwise, transit teams can bring ridership, schedules, and actual service data into one view. That gives planners a way to compare what they expected with what happened and use those findings to prepare for the next event.
