Train NS 3671 Zwolle – Roosendaal
It has not run yet today
Last recorded run: Wednesday 11 November 0 min
Next service: today 19:50 from Zwolle · Fri 13 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
- Tue 10 Nov Max en route +21 min · last fix heading to — +21 min
- Wed 7 Oct Max en route +9 min · last fix heading to — +9 min
- Fri 23 Oct Max en route +5 min · last fix heading to — +3 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 21
- 3–10 min 8% · 2
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 67% T n=3
- 75% W n=4
- 100% T n=2
- 75% F n=4
- 100% S n=3
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 24 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 |
|---|---|---|---|
| 19:50 | on time | on time | |
| 19:59 | ≈ on time | ≈ on time | |
| 20:06 | ≈ on time | ≈ on time | |
| 20:14 / 20:15 | ≈ on time | ≈ +1 min | |
| 20:26 / 20:28 | ≈ on time | ≈ +1 min | |
| 20:37 | ≈ on time | ≈ +1 min | |
| 20:49 / 20:53 | ≈ on time | ≈ +2 min | |
| 21:05 / 21:08 | ≈ on time | ≈ +2 min | |
| 21:23 / 21:24 | ≈ on time | ≈ +3 min | |
| 21:36 / 21:41 | ≈ on time | ≈ +3 min | |
| 21:56 / 21:58 | ≈ on time | ≈ +3 min | |
| 22:10 / 22:15 | ≈ on time | ≈ +4 min | |
| 22:23 | ≈ on time | ≈ +4 min | |
| 22:33 | on time | +4 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 |
|---|---|---|---|
| Wed 11 Nov | — 22:34 | 0 min | — |
| Tue 10 Nov | — 22:54 | +21 min | +21 min |
| Mon 9 Nov | — 22:34 | 0 min | — |
| Sun 8 Nov | Oss 21:39 | 0 min | +1 min |
| Sat 7 Nov | Oss 21:39 | +2 min | +2 min |
| Fri 6 Nov | — 22:34 | 0 min | — |
| Thu 5 Nov | — 22:34 | No data | — |
| Wed 4 Nov | — 22:34 | 0 min | — |
| Mon 2 Nov | — 22:34 | +2 min | +2 min |
| Sun 1 Nov | Etten-Leur 22:39Partial coverage | +2 min | +2 min |
| Sat 31 Oct | Etten-Leur 22:37 | 0 min | — |
| Fri 30 Oct | — 23:11 | No data | — |
| Thu 29 Oct | — 22:34 | 0 min | — |
| Wed 28 Oct | — 22:34 | 0 min | — |
| Tue 27 Oct | — 22:35 | No data | — |
| Mon 26 Oct | — 22:41 | No data | — |
| Fri 23 Oct | — 22:40 | +3 min | +5 min |
| Thu 22 Oct | — 22:35 | No data | — |
| Wed 21 Oct | — 22:34 | No data | — |
| Tue 20 Oct | — 21:44 | 0 min | — |
| Mon 19 Oct | — 22:34 | No data | — |
| Sun 18 Oct | Etten-Leur 22:40Partial coverage | +1 min | +1 min |
| Sat 17 Oct | Etten-Leur 22:42 | No data | — |
| Fri 16 Oct | Zwolle 22:34Partial coverage | 0 min | — |
| Thu 15 Oct | — 22:13 | No data | — |
| Wed 14 Oct | — 22:34 | No data | — |
| Tue 13 Oct | — 22:35 | No data | — |
| Mon 12 Oct | — 22:34 | 0 min | — |
| Sun 11 Oct | Etten-Leur 22:40Partial coverage | 0 min | — |
| Sat 10 Oct | Tilburg 22:35Partial coverage | +1 min | +1 min |