CR-Worcester 1031 Ronkonkoma – Penn Station

View line CR-Worcester

Ronkonkoma 07:45 → Penn Station 09:05 Mon, Tue, Wed, Thu, Fri 1 h 20 min · 10 stops MBTA

It does not run today

Last recorded run: Tuesday 6 October −3 min

Next service: Monday 07:45 from Ronkonkoma · Mon 16 Nov

Next departure 07:45 Monday · Ronkonkoma
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
94%
34/36 runs under 3 min
RT coverage: 35 full · 1 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Penn 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 25 Sept Max en route +5 min · last fix heading to 237 +4 min
  • Fri 28 Aug Max en route +9 min · last fix heading to 237 +4 min

Distribution · 90 days

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

  • Early 8% · 3
  • On time 86% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 100% W n=7
  • 100% T n=7
  • 71% F n=7
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Last 90 days, 36 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
07:45on time +2 min
07:54≈ on time ≈ +2 min
07:57≈ on time ≈ +2 min
08:02≈ on time ≈ +2 min
08:07≈ on time ≈ +2 min
08:12≈ on time ≈ +2 min
08:17≈ on time ≈ +2 min
08:22≈ on time ≈ +2 min
08:45 / 08:46≈ on time ≈ +2 min
09:05on time +2 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
Tue 6 OctGrafton 04:38Partial coverage−3 min—
Mon 5 OctRoute 128 07:28−1 min—
Fri 2 OctKB-0351-S 18:280 min+23 min
Thu 1 Oct237 09:56−1 min+4 min
Wed 30 SeptKB-0351-S 18:300 min+5 min
Tue 29 SeptKB-0351-S 18:270 min+4 min
Mon 28 SeptKB-0351-S 18:280 min+4 min
Fri 25 Sept237 09:56+4 min+5 min
Thu 24 SeptKB-0351-S 18:290 min+5 min
Wed 23 Sept237 09:56+3 min+4 min
Tue 22 SeptKB-0351-S 18:270 min+7 min
Mon 21 SeptKB-0351-S 18:300 min+4 min
Fri 18 Sept237 09:58+1 min+6 min
Thu 17 SeptKB-0351-S 18:280 min+5 min
Wed 16 SeptKB-0351-S 18:280 min+4 min
Tue 15 SeptKB-0351-S 18:350 min—
Sun 13 SeptKB-0351-S 18:290 min—
Fri 11 SeptKB-0351-S 18:280 min+7 min
Thu 10 Sept237 09:55−4 min+5 min
Wed 9 SeptKB-0351-S 18:280 min—
Tue 8 SeptKB-0351-S 18:340 min+4 min
Fri 4 Sept237 09:57−1 min+5 min
Thu 3 SeptKB-0351-S 18:280 min+7 min
Wed 2 SeptKB-0351-S 18:290 min+7 min
Tue 1 Sept237 09:56+2 min+6 min
Mon 31 AugKB-0351-S 18:290 min+5 min
Fri 28 Aug237 09:55+4 min+9 min
Thu 27 AugKB-0351-S 18:280 min+4 min
Wed 26 AugKB-0351-S 18:310 min+6 min
Tue 25 Aug237 09:580 min+5 min