Train NS 28516 Eindhoven Centraal – Zwijndrecht
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 1 full · 1 partial · 0 no data
On-time · 90 days
—
Too little data (2/9 runs with data)
RT coverage: 1 full · 1 partial · 7 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
Arrival delay at Zwijndrecht, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 7 Nov Max en route +5 min · last fix heading to Dordrecht +5 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 50% · 1
- 3–10 min 50% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=1
- 0% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 06:13 | |
| 06:35 / 06:37 | |
| 06:52 / 06:54 | |
| 07:15 / 07:22 | |
| 07:26 |
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 11 July 2026.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Dordrecht 07:39Partial coverage | +5 min | +5 min |
| Fri 16 Oct | Den Helder Zuid 08:21 | 0 min | — |
| Sun 20 Sept | Geldermalsen 08:08 | No data | — |
| Sat 19 Sept | Geldermalsen 08:08 | No data | — |
| Sat 12 Sept | Gouda 07:23 | No data | — |
| Thu 27 Aug | Delft 08:08 | No data | — |
| Wed 26 Aug | Delft 08:07 | No data | — |
| Tue 25 Aug | Delft 08:17 | No data | — |
| Sat 22 Aug | Amsterdam Zuid 07:30 | No data | — |