TRE 404
View line TRE
Alerts for train 404
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line TRE.
The mini-map returns when the train runs
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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
Worst days
- Thu 8 Oct Max en route +9 min · last fix heading to Patchogue +6 min
Distribution · 90 days
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 14% · 1
- On time 71% · 5
- 3–10 min 14% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=1
- 100% W n=1
- 0% T n=1
- 100% F n=1
- 100% S n=1
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 9 Oct | septa-rail:1 07:10 | +2 min | +3 min |
| Thu 8 Oct | Patchogue 19:44 | +6 min | +9 min |
| Wed 7 Oct | Oyster Bay 17:46 | −2 min | +10 min |
| Tue 6 Oct | Patchogue 23:40 | +2 min | +23 min |
| Mon 5 Oct | Speonk 22:07 | 0 min | +4 min |
| Sun 4 Oct | 198 01:15 | +2 min | +12 min |
| Sat 3 Oct | 163 18:46 | +1 min | +1 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.