Metro-North 745
View line Metro-North
Alerts for train 745
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.
On-time · 30 days
—
Too little data (2/3 runs with data)
RT coverage: 2 full · 0 partial · 1 no data
On-time · 90 days
—
Too little data (2/3 runs with data)
RT coverage: 2 full · 0 partial · 1 no data
Typical delay
—
Needs at least 5 runs with data (2 so far)
P90
—
Needs at least 5 runs with data (2 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
- Sun 4 Oct Max en route +47 min · last fix heading to San Jose +35 min
- Sat 3 Oct Max en route +26 min · last fix heading to San Jose +14 min
Distribution · 90 days
2 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 0% · 0
- 3–10 min 0% · 0
- 10–30 min 50% · 1
- 30+ min 50% · 1
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 0% S n=1
- 0% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 5 Oct | Croton-Harmon 17:07 | No data | — |
| Sun 4 Oct | San Jose 22:56 | +35 min | +47 min |
| Sat 3 Oct | San Jose 22:34 | +14 min | +26 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.