Metro-North 514
View line Metro-North
Alerts for train 514
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.
The mini-map returns when the train runs
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 3 full · 0 partial · 1 no data
On-time · 90 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 1 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
Last 30 days
Delay at the end of each run, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 5 Oct Max en route +8 min · last fix heading to Oyster Bay +6 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 25% · 1
- On time 50% · 2
- 3–10 min 25% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- 100% S n=2
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 6 Oct | Grand Central 08:11 | No data | — |
| Mon 5 Oct | Oyster Bay 13:04 | +6 min | +8 min |
| Sun 4 Oct | 141 11:24 | −3 min | +9 min |
| Sun 13 Sept | NEC-2287 08:02 | 0 min | — |
| Mon 27 Jul | NEC-2287 07:58 | 0 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.