Metro-North 842 Poughkeepsie – Grand Central
Alerts for train 842
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Metro-North.
✓ Today’s run finished
Today, last fix heading to Grand Central at 09:46 No data
- Poughkeepsie08:01
- Beacon08:18
- Cold Spring08:25
- Peekskill08:41
- Cortlandt08:46
- Harlem-125 St09:33
- Grand Central09:46
Next service: Monday 08:01 from Poughkeepsie · Mon 9 Nov
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
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 50% · 3
- 3–10 min 33% · 2
- 10–30 min 17% · 1
- 30+ min 0% · 0
On-time by weekday
- 33% M n=3
- 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, 6 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 08:01 | on time | +2 min | |
| 08:10 | ≈ +1 min | ≈ +2 min | |
| 08:18 | ≈ +1 min | ≈ +3 min | |
| 08:25 | ≈ +1 min | ≈ +4 min | |
| 08:30 | ≈ +1 min | ≈ +5 min | |
| 08:41 | ≈ +2 min | ≈ +6 min | |
| 08:46 | ≈ +2 min | ≈ +7 min | |
| 08:55 | ≈ +2 min | ≈ +8 min | |
| 09:33 | ≈ +3 min | ≈ +14 min | |
| 09:46 | +3 min | +16 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Grand Central 09:46 | No data | — |
| Thu 5 Nov | Grand Central 09:43 | No data | — |
| Wed 4 Nov | Grand Central 09:43 | No data | — |
| Tue 3 Nov | Grand Central 09:43 | No data | — |
| Mon 2 Nov | Grand Central 09:42 | No data | — |
| Fri 30 Oct | Grand Central 09:36 | No data | — |
| Thu 29 Oct | Grand Central 09:42 | No data | — |
| Wed 28 Oct | Grand Central 09:44 | No data | — |
| Tue 27 Oct | Grand Central 09:42 | No data | — |
| Mon 26 Oct | Grand Central 09:42 | No data | — |
| Fri 23 Oct | Grand Central 09:43 | No data | — |
| Thu 22 Oct | Grand Central 09:41 | No data | — |
| Wed 21 Oct | Grand Central 09:42 | No data | — |
| Tue 20 Oct | Grand Central 09:44 | No data | — |
| Mon 19 Oct | septa-rail:1 16:52 | +4 min | +4 min |
| Sun 18 Oct | septa-rail:90007 15:37 | 0 min | +9 min |
| Fri 16 Oct | Grand Central 09:43 | No data | — |
| Thu 15 Oct | Grand Central 09:43 | No data | — |
| Wed 14 Oct | Grand Central 09:41 | +1 min | +1 min |
| Tue 13 Oct | septa-rail:1 10:57 | +24 min | +24 min |
| Mon 12 Oct | Grand Central 09:47 | +3 min | +3 min |
| Fri 9 Oct | Grand Central 09:42 | No data | — |
| Thu 8 Oct | Grand Central 09:44 | No data | — |
| Wed 7 Oct | Grand Central 09:44 | No data | — |
| Tue 6 Oct | Grand Central 09:46 | No data | — |
| Mon 5 Oct | septa-rail:90205 21:16 | 0 min | +11 min |