| ISO week | Dates | Hours caught | Comparable | Weekday | 7–10 a.m. | 4–7 p.m. | Stopped | Weekend | Moving only | Buses | Scheduled | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||||||
data/summary/, data/route-history/ and data/daily/ in the
repo; raw snapshots are on its bus-data branch.
How collection runs. One long-running GitHub Actions job polls the MTA BusTime feed about a dozen times over six minutes at 9 and 39 minutes past every hour, 6 a.m. to 11 p.m. Eastern, and saves every bus the feed reports in service. Before its six-hour time limit it starts its own successor. Until October 2026 each burst was a separately scheduled run, and GitHub skipped many of them; from Oct. 1 to Oct. 6, 2026, only three to five bursts a day were caught. The bar strip at the top of this tray shows the last three weeks, and the daily processor fails loudly when a day comes in under 12 of 17 hours. No bus position is interpolated. Weekly figures may fill in up to two missed hours per day type, as the methodology describes, and the weekly table lists which.
How speed is computed (collector/process.js and collector/rollup.js, method version 2). See the methodology note in the sidebar and the data dictionary. Every day since April 22, 2026, was reprocessed from the raw snapshots when the method changed, so the whole series is computed one way.
Known limits.