CR-Greenbush 1808 Salem – North Station

View line CR-Greenbush

Salem 16:27 → North Station 17:06 Sat, Sun 0 h 39 min · 5 stops MBTA

Running now · updated 06:08

Heading to North Station No data

Estimated arrival at North Station 17:06 · 42 km/h

  1. Salem16:27
  2. Swampscott16:33
  3. Lynn Interim16:36
  4. Chelsea16:47
  5. North Station17:06
On-time · 30 days
70%
14/20 runs under 3 min
RT coverage: 20 full · 0 partial · 4 no data
On-time · 90 days
74%
17/23 runs under 3 min
RT coverage: 23 full · 0 partial · 6 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +7 min

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

  • Fri 23 Oct Max en route +13 min · last fix heading to Back Bay +13 min
  • Thu 15 Oct Max en route +9 min · last fix heading to Forge Park/495 +8 min
  • Mon 19 Oct Max en route +10 min · last fix heading to Providence +7 min
  • Fri 16 Oct Max en route +15 min · last fix heading to Worcester +5 min
  • Mon 26 Oct Max en route +21 min · last fix heading to Worcester +5 min

Distribution · 90 days

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

  • Early 43% · 10
  • On time 30% · 7
  • 3–10 min 22% · 5
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 100% T n=5
  • 100% W n=4
  • 50% T n=4
  • 33% F n=3
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 23 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 10Today
16:273 min early on time
16:33≈ 3 min early ≈ on time
16:36≈ 3 min early ≈ +1 min
16:47≈ 1 min early ≈ +2 min
17:06on time +6 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

DateLast stopFinalMax
Fri 6 NovGreenbush 06:03Partial coverageNo data—
Thu 5 NovKingston 18:33+1 min+7 min
Wed 4 NovKingston 20:540 min+35 min
Tue 3 NovNeedham Heights 00:38−1 min+12 min
Mon 2 NovKingston 17:020 min+8 min
Fri 30 OctGreenbush 18:09No data—
Thu 29 OctProvidence 01:06No data—
Wed 28 OctFall River Depot 20:20No data—
Tue 27 OctNeedham Heights 00:42+3 min+24 min
Mon 26 OctWorcester 19:00+5 min+21 min
Fri 23 OctBack Bay 13:28+13 min+13 min
Thu 22 OctWorcester 18:59+5 min+18 min
Wed 21 OctSouth Station 00:16−2 min+8 min
Tue 20 OctSouth Station 00:37−5 min+15 min
Mon 19 OctProvidence 21:50+7 min+10 min
Fri 16 OctWorcester 18:51+5 min+15 min
Thu 15 OctForge Park/495 17:46+8 min+9 min
Wed 14 OctSouth Station 00:35−6 min+11 min
Tue 13 OctProvidence 01:05−6 min+5 min
Mon 12 OctNew Bedford 01:32−5 min+7 min
Sun 11 OctProvidence 01:10+2 min+6 min
Sat 10 OctForge Park/495 01:080 min+78 min
Fri 9 OctFall River Depot 20:19−5 min+10 min
Thu 8 OctNeedham Heights 00:36−2 min+7 min
Wed 7 OctFramingham 17:52−1 min+31 min
Tue 6 OctProvidence 01:07−4 min+18 min
Mon 5 OctNeedham Heights 00:36−2 min+25 min
Sun 4 OctFB-0095-04 23:42No data—
Sat 3 OctFB-0303-S 01:12No data—