Train NS 3660 Roosendaal – Zwolle
It has not run yet today
Last recorded run: Friday 13 November 0 min
Next service: today 17:57 from Roosendaal · Sat 14 Nov
Last 30 days
Arrival delay at Zwolle, 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 12 Nov Max en route +24 min · last fix heading to Breda +24 min
- Fri 23 Oct Max en route +23 min · last fix heading to Nijmegen +23 min
- Tue 10 Nov Max en route +16 min · last fix heading to Breda +16 min
- Wed 4 Nov Max en route +11 min · last fix heading to Etten-Leur +10 min
- Sat 31 Oct Max en route +10 min · last fix heading to Wijhe +10 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 69% · 18
- 3–10 min 19% · 5
- 10–30 min 12% · 3
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 67% T n=3
- 75% W n=4
- 50% T n=2
- 60% F n=5
- 33% S n=3
- 75% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 26 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 |
|---|---|---|---|
| 17:57 | on time | on time | |
| 18:07 | ≈ on time | ≈ +1 min | |
| 18:15 / 18:19 | ≈ on time | ≈ +2 min | |
| 18:32 / 18:34 | ≈ on time | ≈ +5 min | |
| 18:49 / 18:55 | ≈ on time | ≈ +7 min | |
| 19:06 | ≈ on time | ≈ +8 min | |
| 19:23 / 19:24 | ≈ on time | ≈ +8 min | |
| 19:37 / 19:41 | ≈ +1 min | ≈ +9 min | |
| 19:52 / 19:53 | ≈ +1 min | ≈ +11 min | |
| 20:02 / 20:03 | ≈ +1 min | ≈ +11 min | |
| 20:15 / 20:16 | ≈ +1 min | ≈ +12 min | |
| 20:23 | ≈ +1 min | ≈ +13 min | |
| 20:29 | ≈ +1 min | ≈ +13 min | |
| 20:40 | +1 min | +14 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 13 Nov | 's-Hertogenbosch 20:23Partial coverage | 0 min | — |
| Thu 12 Nov | Breda 21:19 | +24 min | +24 min |
| Wed 11 Nov | Etten-Leur 20:44 | +2 min | +3 min |
| Tue 10 Nov | Breda 21:04 | +16 min | +16 min |
| Mon 9 Nov | Etten-Leur 18:19Partial coverage | 0 min | — |
| Sun 8 Nov | Wijhe 20:44 | +1 min | — |
| Sat 7 Nov | Wijhe 20:43 | 0 min | — |
| Fri 6 Nov | Tilburg 20:48 | +6 min | +8 min |
| Thu 5 Nov | Etten-Leur 20:45 | No data | — |
| Wed 4 Nov | Etten-Leur 20:52 | +10 min | +11 min |
| Tue 3 Nov | Etten-Leur 20:42 | No data | — |
| Mon 2 Nov | Etten-Leur 20:44 | No data | — |
| Sun 1 Nov | Wijhe 20:44 | +1 min | +2 min |
| Sat 31 Oct | Wijhe 20:52 | +10 min | +10 min |
| Fri 30 Oct | Tilburg 20:19 | No data | — |
| Thu 29 Oct | Roosendaal 18:11 | No data | — |
| Wed 28 Oct | Etten-Leur 19:46 | 0 min | — |
| Tue 27 Oct | Roosendaal 19:58 | No data | — |
| Mon 26 Oct | Etten-Leur 19:44 | 0 min | — |
| Fri 23 Oct | Nijmegen 20:26 | +23 min | +23 min |
| Thu 22 Oct | Tilburg 19:45 | No data | — |
| Wed 21 Oct | Tilburg 19:41 | No data | — |
| Tue 20 Oct | Tilburg 19:47 | 0 min | — |
| Mon 19 Oct | Tilburg 18:51 | 0 min | — |
| Sun 18 Oct | Wijhe 20:52 | +8 min | +9 min |
| Sat 17 Oct | Wijhe 20:55 | No data | — |
| Fri 16 Oct | Dieren 20:44 | +1 min | +1 min |
| Thu 15 Oct | Breda 18:55 | No data | — |
| Wed 14 Oct | Arnhem Centraal 20:46 | No data | — |
| Tue 13 Oct | Tilburg 20:42 | No data | — |