Train NS 5967 Dordrecht – Roosendaal
It has not run yet today
Last recorded run: Friday 6 November +11 min
Next service: today 18:23 from Dordrecht · Sat 7 Nov
Last 30 days
Arrival delay at Roosendaal, 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 29 Oct Max en route +31 min · last fix heading to — +31 min
- Fri 6 Nov Max en route +11 min · last fix heading to Oudenbosch +11 min
- Sun 18 Oct Max en route +8 min · last fix heading to Oudenbosch +8 min
- Sat 31 Oct Max en route +5 min · last fix heading to Oudenbosch +4 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 82% · 18
- 3–10 min 9% · 2
- 10–30 min 5% · 1
- 30+ min 5% · 1
On-time by weekday
- 100% M n=3
- 100% T n=3
- 100% W n=5
- 50% T n=2
- 75% F n=4
- 50% S n=2
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 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:23 | on time | on time | |
| 18:26 | ≈ on time | ≈ +2 min | |
| 18:34 | ≈ on time | ≈ +4 min | |
| 18:40 | ≈ on time | ≈ +6 min | |
| 18:46 | ≈ on time | ≈ +7 min | |
| 18:53 | on time | +9 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 | Oudenbosch 19:04Partial coverage | +11 min | +11 min |
| Thu 5 Nov | — 18:54 | No data | — |
| Wed 4 Nov | — 18:49 | 0 min | — |
| Tue 3 Nov | — 18:54 | No data | — |
| Mon 2 Nov | Lage Zwaluwe 18:54Partial coverage | 0 min | — |
| Sun 1 Nov | Oudenbosch 18:59Partial coverage | 0 min | — |
| Sat 31 Oct | Oudenbosch 19:05Partial coverage | +4 min | +5 min |
| Fri 30 Oct | Oudenbosch 19:00Partial coverage | 0 min | — |
| Thu 29 Oct | — 19:57 | +31 min | +31 min |
| Wed 28 Oct | — 18:53 | 0 min | — |
| Tue 27 Oct | — 18:55 | 0 min | — |
| Mon 26 Oct | — 18:59 | No data | — |
| Sun 25 Oct | Oudenbosch 19:01 | No data | — |
| Sat 24 Oct | Oudenbosch 19:00 | No data | — |
| Fri 23 Oct | Oudenbosch 19:00Partial coverage | 0 min | — |
| Thu 22 Oct | Zevenbergen 18:57 | No data | — |
| Wed 21 Oct | Zevenbergen 18:55Partial coverage | 0 min | — |
| Tue 20 Oct | Oudenbosch 18:55Partial coverage | 0 min | — |
| Mon 19 Oct | Zevenbergen 18:55 | No data | — |
| Sun 18 Oct | Oudenbosch 19:07Partial coverage | +8 min | +8 min |
| Sat 17 Oct | Oudenbosch 19:19 | No data | — |
| Fri 16 Oct | Oudenbosch 19:00 | No data | — |
| Thu 15 Oct | Dordrecht Zuid 18:56 | No data | — |
| Wed 14 Oct | Oudenbosch 19:00Partial coverage | 0 min | — |
| Tue 13 Oct | Zevenbergen 18:54 | No data | — |
| Mon 12 Oct | Zevenbergen 18:55Partial coverage | 0 min | — |
| Sun 11 Oct | Oudenbosch 19:00Partial coverage | 0 min | — |
| Sat 10 Oct | Oudenbosch 19:01Partial coverage | 0 min | +1 min |
| Fri 9 Oct | Lage Zwaluwe 18:54Partial coverage | 0 min | — |
| Thu 8 Oct | — 18:55 | 0 min | — |