Metro-North 894 Poughkeepsie – Croton-Harmon

View line Metro-North

Poughkeepsie 21:48 → Croton-Harmon 22:47 Mon, Tue, Wed, Thu, Fri 0 h 59 min · 8 stops MTA Metro-North

✓ Today’s run finished

Today, last fix heading to Cortlandt at 22:33 −2 min

  1. Poughkeepsie21:48
  2. New Hamburg21:58
  3. Beacon22:06
  4. Garrison22:18
  5. Peekskill22:29
  6. Cortlandt22:34
  7. Croton-Harmon22:47

Next service: tomorrow 21:48 from Poughkeepsie · Tue 17 Nov

Next departure 21:48 tomorrow · Poughkeepsie
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 6 full · 5 partial · 9 no data
On-time · 90 days
82%
9/11 runs under 3 min
RT coverage: 6 full · 5 partial · 16 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: −2 min
P90
+13min
9 in 10 runs arrive with less than this
30 days: +13 min

Last 30 days

Arrival delay at Croton-Harmon, 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 3 Nov Max en route +27 min · last fix heading to Cortlandt +15 min
  • Mon 9 Nov Max en route +27 min · last fix heading to Croton-Harmon +13 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 18% · 2
  • 3–10 min 0% · 0
  • 10–30 min 18% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 50% T n=2
  • 100% W n=2
  • 100% 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 (8 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:48+3 min +3 min
21:58— —
22:06— —
22:14— —
22:18— —
22:29— —
22:34— —
22:47— —

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 NovCortlandt 22:33Partial coverage−2 min+13 min
Fri 13 NovCroton-Harmon 22:42+3 min+11 min
Thu 12 Nov— 08:49−2 min+12 min
Wed 11 NovCroton-Harmon 23:58−6 min+13 min
Tue 10 NovCortlandt 22:34Partial coverage0 min+15 min
Mon 9 NovCroton-Harmon 22:42+13 min+27 min
Fri 6 NovCroton-Harmon 22:40−4 min+11 min
Thu 5 NovCortlandt 22:34Partial coverage−3 min+12 min
Wed 4 NovCortlandt 22:34Partial coverage−2 min+13 min
Tue 3 NovCortlandt 22:35Partial coverage+15 min+27 min
Mon 2 NovCroton-Harmon 22:45−5 min+10 min
Fri 30 OctCroton-Harmon 22:39No data—
Thu 29 OctCroton-Harmon 22:39No data—
Tue 27 OctCroton-Harmon 23:59No data—
Mon 26 OctCroton-Harmon 22:43No data—
Fri 23 OctCroton-Harmon 22:40No data—
Thu 22 OctCroton-Harmon 22:40No data—
Wed 21 OctCroton-Harmon 22:40No data—
Tue 20 OctCortlandt 22:36Partial coverageNo data—
Mon 19 OctCortlandt 22:34Partial coverageNo data—
Fri 16 OctCroton-Harmon 22:41No data—
Wed 14 OctCroton-Harmon 00:00No data—
Tue 13 OctCroton-Harmon 22:40No data—
Mon 12 OctCroton-Harmon 22:44No data—
Thu 8 OctCroton-Harmon 23:59No data—
Wed 7 OctCroton-Harmon 22:40No data—
Mon 5 OctCortlandt 23:59Partial coverageNo data—