CR-Newburyport 1716 North Station – Rockport
Alerts for train 1716
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line CR-Newburyport.
It has not run yet today
Last recorded run: Thursday 5 November +1 min
Next service: today 17:02 from North Station · Fri 6 Nov
Last 30 days
Arrival delay at Rockport, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 2 Nov Max en route +19 min · last fix heading to Newburyport +13 min
- Tue 3 Nov Max en route +4 min · last fix heading to Bradford +4 min
- Thu 3 Sept Max en route +4 min · last fix heading to 216 +4 min
Distribution · 90 days
56 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 11% · 6
- On time 84% · 47
- 3–10 min 4% · 2
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 89% T n=9
- 100% W n=9
- 89% T n=9
- 100% F n=10
- 100% S n=5
- 100% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 56 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 17:02 | on time | +1 min | |
| 17:12 | ≈ on time | ≈ +1 min | |
| 17:20 | ≈ on time | ≈ +1 min | |
| 17:25 | ≈ on time | ≈ +1 min | |
| 17:29 | ≈ on time | ≈ +1 min | |
| 17:37 | ≈ on time | ≈ +1 min | |
| 17:42 | ≈ on time | ≈ +1 min | |
| 17:46 | ≈ on time | ≈ +1 min | |
| 17:51 | ≈ on time | ≈ +1 min | |
| 17:57 | ≈ on time | ≈ +1 min | |
| 18:03 | ≈ on time | ≈ +1 min | |
| 18:09 | ≈ on time | ≈ +1 min | |
| 18:22 | on time | +1 min |
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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 5 Nov | Rockport 18:22 | +1 min | +27 min |
| Wed 4 Nov | mbta:BNT-0000-05 18:58 | −2 min | +10 min |
| Tue 3 Nov | Bradford 17:38 | +4 min | +4 min |
| Mon 2 Nov | Newburyport 20:02 | +13 min | +19 min |
| Fri 30 Oct | Rockport 00:26 | +1 min | +7 min |
| Thu 29 Oct | New Canaan 10:20 | No data | — |
| Wed 28 Oct | New Canaan 10:20 | No data | — |
| Tue 27 Oct | Talmadge Hill 10:19 | No data | — |
| Mon 26 Oct | New Canaan 10:21 | No data | — |
| Fri 23 Oct | New Canaan 10:19 | No data | — |
| Thu 22 Oct | New Canaan 10:19 | No data | — |
| Wed 21 Oct | New Canaan 10:19 | No data | — |
| Tue 20 Oct | Talmadge Hill 10:19 | No data | — |
| Mon 19 Oct | Talmadge Hill 10:20 | No data | — |
| Fri 16 Oct | Talmadge Hill 10:19 | No data | — |
| Thu 15 Oct | New Canaan 10:21 | No data | — |
| Wed 14 Oct | New Canaan 10:20 | No data | — |
| Tue 13 Oct | Talmadge Hill 10:24 | No data | — |
| Mon 12 Oct | Talmadge Hill 10:19 | No data | — |
| Fri 9 Oct | Newmarket 18:27 | 0 min | — |
| Thu 8 Oct | New Canaan 10:22 | No data | — |
| Wed 7 Oct | Talmadge Hill 10:19 | No data | — |
| Tue 6 Oct | New Canaan 10:21 | No data | — |
| Mon 5 Oct | Talmadge Hill 10:20 | No data | — |
| Fri 2 Oct | — 12:26 | 0 min | +3 min |
| Thu 1 Oct | — 19:58 | 0 min | +4 min |
| Wed 30 Sept | — 19:59 | 0 min | +2 min |
| Tue 29 Sept | 216 12:49 | −1 min | +2 min |
| Mon 28 Sept | — 00:26 | 0 min | — |
| Sun 27 Sept | — 19:59 | 0 min | — |