Metro-North 883 Grand Central – Poughkeepsie

View line Metro-North

Grand Central 21:04 → Poughkeepsie 22:58 Mon, Tue, Wed, Thu, Fri 1 h 54 min · 10 stops MTA Metro-North

✓ Today’s run finished

Today it reached Poughkeepsie at 23:06 +8 min

  1. Grand Central21:04
  2. Croton-Harmon21:53
  3. Cortlandt22:00
  4. Garrison22:17
  5. Cold Spring22:21
  6. New Hamburg22:38
  7. Poughkeepsie22:58

Next service: tomorrow 21:04 from Grand Central · Tue 17 Nov

Next departure 21:04 tomorrow · Grand Central
On-time · 30 days
73%
8/11 runs under 3 min
RT coverage: 11 full · 0 partial · 10 no data
On-time · 90 days
73%
8/11 runs under 3 min
RT coverage: 11 full · 0 partial · 20 no data
Typical delay
−8min
Median at arrival, 90 days
30 days: −8 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: +11 min

Last 30 days

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

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

Worst days

  • Wed 4 Nov Max en route +26 min · last fix heading to Poughkeepsie +14 min
  • Thu 5 Nov Max en route +21 min · last fix heading to Poughkeepsie +11 min
  • Mon 16 Nov Max en route +23 min · last fix heading to Poughkeepsie +8 min

Distribution · 90 days

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

  • Early 64% · 7
  • On time 9% · 1
  • 3–10 min 9% · 1
  • 10–30 min 18% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 50% W n=2
  • 50% T n=2
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 11 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
21:04on time +2 min
21:15— —
21:53— —
22:00— —
22:05— —
22:17— —
22:21— —
22:30— —
22:38— —
22:58— —

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
Mon 16 NovPoughkeepsie 22:46+8 min+23 min
Fri 13 NovPoughkeepsie 22:51−14 min+3 min
Thu 12 NovPoughkeepsie 22:43−9 min+5 min
Wed 11 NovPoughkeepsie 22:43−8 min+5 min
Tue 10 NovPoughkeepsie 22:43−7 min+7 min
Mon 9 NovPoughkeepsie 22:47−1 min+13 min
Fri 6 NovPoughkeepsie 22:43−10 min+4 min
Thu 5 NovPoughkeepsie 22:47+11 min+21 min
Wed 4 NovPoughkeepsie 22:43+14 min+26 min
Tue 3 NovPoughkeepsie 22:47−11 min+4 min
Mon 2 NovPoughkeepsie 22:49−12 min+2 min
Fri 30 OctPoughkeepsie 22:44No data—
Thu 29 OctPoughkeepsie 22:47No data—
Wed 28 OctPoughkeepsie 22:44No data—
Tue 27 OctPoughkeepsie 22:45No data—
Mon 26 OctPoughkeepsie 22:49No data—
Fri 23 OctPoughkeepsie 22:46No data—
Thu 22 OctPoughkeepsie 22:46No data—
Wed 21 OctPoughkeepsie 22:47No data—
Tue 20 OctPoughkeepsie 22:45No data—
Mon 19 OctPoughkeepsie 22:50No data—
Fri 16 OctPoughkeepsie 22:50No data—
Thu 15 OctPoughkeepsie 22:49No data—
Wed 14 OctPoughkeepsie 22:46No data—
Tue 13 OctPoughkeepsie 22:42No data—
Mon 12 OctPoughkeepsie 22:49No data—
Fri 9 OctPoughkeepsie 22:43No data—
Thu 8 OctPoughkeepsie 22:46No data—
Wed 7 OctPoughkeepsie 22:48No data—
Tue 6 OctPoughkeepsie 22:46No data—