LIRR 6417
Alerts for train 6417
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line LIRR.
Train 6417: final delay under 3 min on 10 of its 10 runs with data in the last 90 days (100%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 10:08 (GMT-5).
An alert on this phone or computer when the 6417 is 5 min or more late, every day it runs. No account, no email.
Not running right now
Last recorded run: Saturday 3 October −1 min
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
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 10% · 1
- On time 90% · 9
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 100% S n=5
- 100% S n=4
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 3 Oct | 349 10:20 | −1 min | +2 min |
| Sun 27 Sept | 349 10:19 | 0 min | +3 min |
| Sat 26 Sept | 349 10:32 | +1 min | +4 min |
| Sun 20 Sept | 349 10:19 | 0 min | +3 min |
| Sat 19 Sept | 349 10:20 | +3 min | +3 min |
| Mon 7 Sept | 349 10:20 | +2 min | +4 min |
| Sun 6 Sept | 349 10:20 | +2 min | +3 min |
| Sat 5 Sept | 349 10:20 | +2 min | +2 min |
| Sun 30 Aug | 349 10:20 | 0 min | +4 min |
| Sat 29 Aug | 349 10:20 | +1 min | +5 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.