Train NS 6669 Arnhem Centraal – Dordrecht
It has not run yet today
Last recorded run: Friday 6 November 0 min
Next service: today 18:27 from Arnhem Centraal · Sat 7 Nov
Last 30 days
Arrival delay at Dordrecht, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 9 Oct Max en route +11 min · last fix heading to Elst +11 min
- Fri 16 Oct Max en route +8 min · last fix heading to Tilburg Reeshof +8 min
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 20
- 3–10 min 5% · 1
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=3
- 100% W n=3
- 100% T n=2
- 50% F n=4
- 100% S n=2
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (23 stops).
Last 90 days, 22 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 18:27 | on time | on time | |
| 18:32 | ≈ on time | ≈ on time | |
| 18:36 | ≈ on time | ≈ +1 min | |
| 18:40 | ≈ on time | ≈ +1 min | |
| 18:45 / 18:48 | ≈ on time | ≈ +1 min | |
| 18:51 | ≈ on time | ≈ +1 min | |
| 18:54 | ≈ on time | ≈ +1 min | |
| 18:58 | ≈ on time | ≈ +1 min | |
| 19:04 | ≈ on time | ≈ +1 min | |
| 19:10 | ≈ on time | ≈ +1 min | |
| 19:13 | ≈ on time | ≈ +1 min | |
| 19:20 | ≈ on time | ≈ +1 min | |
| 19:24 | ≈ on time | ≈ +1 min | |
| 19:28 / 19:31 | ≈ on time | ≈ +1 min | |
| 19:45 / 19:47 | ≈ on time | ≈ +1 min | |
| 19:50 | ≈ on time | ≈ +1 min | |
| 19:54 | ≈ on time | ≈ +1 min | |
| 19:58 | ≈ on time | ≈ +1 min | |
| 20:05 / 20:09 | ≈ on time | ≈ +1 min | |
| 20:13 | ≈ on time | ≈ +1 min | |
| 20:20 | ≈ on time | ≈ +2 min | |
| 20:28 | ≈ on time | ≈ +2 min | |
| 20:32 | on time | +2 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 11 July 2026.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Nijmegen Lent 19:34Partial coverage | 0 min | — |
| Thu 5 Nov | — 20:34 | No data | — |
| Wed 4 Nov | — 20:34 | 0 min | — |
| Mon 2 Nov | Nijmegen 20:39 | 0 min | — |
| Sun 1 Nov | Dordrecht Zuid 20:42 | 0 min | — |
| Sat 31 Oct | Dordrecht Zuid 20:42 | 0 min | — |
| Fri 30 Oct | Nijmegen Dukenburg 20:33 | No data | — |
| Thu 29 Oct | — 20:24 | 0 min | +2 min |
| Wed 28 Oct | — 20:40 | 0 min | — |
| Tue 27 Oct | — 20:01 | 0 min | — |
| Mon 26 Oct | Tilburg Universiteit 20:33 | 0 min | — |
| Sun 25 Oct | Dordrecht Zuid 20:42 | No data | — |
| Sat 24 Oct | Dordrecht Zuid 20:42 | No data | — |
| Fri 23 Oct | 's-Hertogenbosch Oost 20:33 | 0 min | — |
| Thu 22 Oct | Nijmegen Lent 20:34 | No data | — |
| Wed 21 Oct | Nijmegen Lent 20:33 | No data | — |
| Tue 20 Oct | Nijmegen Lent 20:42 | 0 min | — |
| Mon 19 Oct | Nijmegen Lent 19:15 | 0 min | — |
| Sun 18 Oct | Dordrecht Zuid 20:44 | +2 min | +2 min |
| Sat 17 Oct | Dordrecht Zuid 20:51 | No data | — |
| Fri 16 Oct | Tilburg Reeshof 20:48 | +8 min | +8 min |
| Thu 15 Oct | Arnhem Centraal 20:33 | No data | — |
| Wed 14 Oct | Tilburg 20:33 | No data | — |
| Tue 13 Oct | Nijmegen Lent 20:34 | No data | — |
| Mon 12 Oct | Nijmegen Lent 20:33 | 0 min | — |
| Sun 11 Oct | Dordrecht Zuid 20:42 | 0 min | — |
| Sat 10 Oct | Dordrecht Zuid 20:42 | 0 min | — |
| Fri 9 Oct | Elst 20:54 | +11 min | +11 min |
| Thu 8 Oct | — 20:56 | 0 min | — |
| Wed 7 Oct | — 20:55 | 0 min | — |