CR-Newburyport 1809 North Station – Salem

View line CR-Newburyport

North Station 15:40 → Salem 16:17 Sun 0 h 37 min · 5 stops MBTA

It does not run today

Last recorded run: Saturday 7 November No data

On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 3 no data
On-time · 90 days
95%
54/57 runs under 3 min
RT coverage: 57 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Salem, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 15 Oct Max en route +12 min · last fix heading to North Station +8 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Bradford +4 min
  • Fri 23 Oct Max en route +12 min · last fix heading to Haverhill +3 min

Distribution · 90 days

57 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 16% · 9
  • On time 79% · 45
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=9
  • 89% W n=9
  • 91% T n=11
  • 91% F n=11
  • 100% S n=5
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 stops).

Last 90 days, 57 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.

StopSched.Usually 9 days in 10
15:40on time on time
15:50≈ on time ≈ on time
16:02≈ on time ≈ on time
16:05≈ on time ≈ on time
16:17on time on time

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

DateLast stopFinalMax
Sat 7 NovRockport 00:38Partial coverageNo data—
Fri 6 NovWachusett 18:24−1 min+23 min
Thu 5 NovWachusett 00:030 min+12 min
Wed 4 NovBradford 23:36+4 min+5 min
Tue 3 NovReading 21:14−4 min+4 min
Mon 2 NovReading 21:16−4 min+8 min
Fri 30 OctHaverhill 23:33−3 min+13 min
Thu 29 OctWachusett 00:02−2 min+7 min
Wed 28 OctNorth Station 22:35+1 min+14 min
Tue 27 OctRockport 00:21−4 min+16 min
Mon 26 OctLowell 23:30−1 min+2 min
Fri 23 OctHaverhill 00:55+3 min+12 min
Thu 22 OctNewburyport 22:560 min+12 min
Wed 21 OctWachusett 01:250 min+2 min
Tue 20 OctLowell 00:33+2 min+3 min
Mon 19 OctHaverhill 22:49−4 min+2 min
Sun 18 OctNorth Station 19:04No data—
Sat 17 OctNorth Station 20:02No data—
Fri 16 OctNorth Station 20:02−5 min—
Thu 15 OctNorth Station 18:48+8 min+12 min
Wed 14 OctNorth Station 00:29−4 min—
Mon 5 Oct— 06:18No data—
Fri 2 Oct— 17:110 min—
Wed 30 Sept— 12:570 min—
Tue 29 Sept— 19:590 min—
Sun 27 Sept— 01:570 min—
Sat 26 Sept— 19:590 min—
Fri 25 Sept— 18:160 min—
Thu 24 Sept— 19:190 min—
Tue 22 Sept— 11:030 min—