Metro-North 842 Poughkeepsie – Grand Central

View line Metro-North

Poughkeepsie 08:01 → Grand Central 09:46 Mon, Tue, Wed, Thu, Fri 1 h 45 min · 10 stops MTA Metro-North

Running now · updated 08:24

Between Beacon and Cold Spring No data

Estimated arrival at Grand Central 09:46 · 0 km/h

  1. Poughkeepsie08:01
  2. Beacon08:18
  3. Cold Spring08:25
  4. Peekskill08:41
  5. Cortlandt08:46
  6. Harlem-125 St09:33
  7. Grand Central09:46
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 3 full · 0 partial · 20 no data
On-time · 90 days
57%
4/7 runs under 3 min
RT coverage: 7 full · 0 partial · 24 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+12min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Grand Central, 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 13 Oct Max en route +24 min · last fix heading to septa-rail:1 +24 min
  • Mon 19 Oct Max en route +4 min · last fix heading to septa-rail:1 +4 min
  • Mon 12 Oct Max en route +3 min · last fix heading to Grand Central +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 57% · 4
  • 3–10 min 29% · 2
  • 10–30 min 14% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=4
  • 0% T n=1
  • 100% W n=1
  • — T n=0
  • — F n=0
  • — 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, 7 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
08:01on time +5 minPassed
08:10≈ +2 min ≈ +6 minPassed
08:18≈ +2 min ≈ +6 minPassed
08:25≈ +2 min ≈ +7 minNext
08:30≈ +2 min ≈ +7 min
08:41≈ +2 min ≈ +8 min
08:46≈ +2 min ≈ +8 min
08:55≈ +2 min ≈ +9 min
09:33≈ +2 min ≈ +12 min
09:46+2 min +14 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 13 NovBeacon 08:19Partial coverageNo data—
Thu 12 NovGrand Central 09:49No data—
Wed 11 NovGrand Central 09:43No data—
Tue 10 NovGrand Central 09:42No data—
Mon 9 Novsepta-rail:90007 23:380 min+23 min
Fri 6 NovGrand Central 09:46No data—
Thu 5 NovGrand Central 09:43No data—
Wed 4 NovGrand Central 09:43No data—
Tue 3 NovGrand Central 09:43No data—
Mon 2 NovGrand Central 09:42No data—
Fri 30 OctGrand Central 09:36No data—
Thu 29 OctGrand Central 09:42No data—
Wed 28 OctGrand Central 09:44No data—
Tue 27 OctGrand Central 09:42No data—
Mon 26 OctGrand Central 09:42No data—
Fri 23 OctGrand Central 09:43No data—
Thu 22 OctGrand Central 09:41No data—
Wed 21 OctGrand Central 09:42No data—
Tue 20 OctGrand Central 09:44No data—
Mon 19 Octsepta-rail:1 16:52+4 min+4 min
Sun 18 Octsepta-rail:90007 15:370 min+9 min
Fri 16 OctGrand Central 09:43No data—
Thu 15 OctGrand Central 09:43No data—
Wed 14 OctGrand Central 09:41+1 min+1 min
Tue 13 Octsepta-rail:1 10:57+24 min+24 min
Mon 12 OctGrand Central 09:47+3 min+3 min
Fri 9 OctGrand Central 09:42No data—
Thu 8 OctGrand Central 09:44No data—
Wed 7 OctGrand Central 09:44No data—
Tue 6 OctGrand Central 09:46No data—