PAO 282 Haverhill – North Station
Alerts for train 282
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line PAO.
It does not run today
Last recorded run: Tuesday 6 October +10 min
Next service: tomorrow 21:27 from Haverhill · Mon 12 Oct
Last 30 days
Arrival delay at North Station, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 6 Oct Max en route +10 min · last fix heading to septa-rail:90505 +10 min
- Mon 5 Oct Max en route +11 min · last fix heading to septa-rail:90203 +4 min
Distribution · 90 days
2 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 0% · 0
- 3–10 min 50% · 1
- 10–30 min 50% · 1
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- 0% T n=1
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
| Stop | Sched. |
|---|---|
| 21:27 | |
| 21:29 | |
| 21:36 | |
| 21:43 | |
| 21:48 | |
| 21:55 | |
| 22:02 | |
| 22:08 | |
| 22:11 | |
| 22:13 | |
| 22:15 | |
| 22:17 | |
| 22:19 | |
| 22:22 | |
| 22:38 |
Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 10 July 2026.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 6 Oct | septa-rail:90505 08:30Partial coverage | +10 min | +10 min |
| Mon 5 Oct | septa-rail:90203 23:37 | +4 min | +11 min |
| Sun 4 Oct | 1 22:03 | No data | — |
| Sat 3 Oct | 90203 22:12 | No data | — |