Train NS 3655 Zwolle – Roosendaal
It has not run yet today
Last recorded run: Friday 13 November +4 min
Next service: today 15:50 from Zwolle · Sat 14 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 +11 min · last fix heading to Etten-Leur +10 min
- Sun 18 Oct Max en route +8 min · last fix heading to Etten-Leur +8 min
- Fri 23 Oct Max en route +6 min · last fix heading to Etten-Leur +6 min
- Sun 8 Nov Max en route +4 min · last fix heading to Oss +4 min
- Fri 13 Nov Max en route +4 min · last fix heading to Etten-Leur +4 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 81% · 21
- 3–10 min 19% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 67% T n=3
- 100% W n=4
- 100% T n=2
- 60% F n=5
- 100% S n=3
- 50% 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 |
|---|---|---|---|
| 15:50 | on time | on time | |
| 15:59 | ≈ on time | ≈ on time | |
| 16:06 | ≈ on time | ≈ +1 min | |
| 16:14 / 16:15 | ≈ on time | ≈ +1 min | |
| 16:26 / 16:28 | ≈ on time | ≈ +1 min | |
| 16:37 | ≈ on time | ≈ +2 min | |
| 16:49 / 16:53 | ≈ on time | ≈ +2 min | |
| 17:05 / 17:08 | ≈ on time | ≈ +3 min | |
| 17:23 / 17:24 | ≈ on time | ≈ +4 min | |
| 17:36 / 17:41 | ≈ on time | ≈ +4 min | |
| 17:56 / 17:58 | ≈ on time | ≈ +5 min | |
| 18:10 / 18:15 | ≈ on time | ≈ +5 min | |
| 18:22 | ≈ on time | ≈ +6 min | |
| 18:33 | on time | +6 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 | Etten-Leur 18:39Partial coverage | +4 min | +4 min |
| Thu 12 Nov | Etten-Leur 18:34 | 0 min | — |
| Wed 11 Nov | Tilburg 18:34 | 0 min | +1 min |
| Tue 10 Nov | Etten-Leur 18:54 | +10 min | +11 min |
| Mon 9 Nov | Tilburg 18:34 | 0 min | — |
| Sun 8 Nov | Oss 17:45 | +4 min | +4 min |
| Sat 7 Nov | Oss 17:39 | +1 min | +1 min |
| Fri 6 Nov | Etten-Leur 18:34Partial coverage | 0 min | — |
| Thu 5 Nov | Tilburg 18:34 | No data | — |
| Wed 4 Nov | Breda 18:29 | 0 min | — |
| Tue 3 Nov | Tilburg 18:34 | No data | — |
| Mon 2 Nov | Tilburg 18:12 | No data | — |
| Sun 1 Nov | Etten-Leur 18:39 | 0 min | — |
| Sat 31 Oct | Etten-Leur 18:42 | +2 min | +2 min |
| Fri 30 Oct | Etten-Leur 18:36 | No data | — |
| Thu 29 Oct | Tilburg 18:41 | No data | — |
| Wed 28 Oct | Tilburg 18:34 | 0 min | — |
| Tue 27 Oct | Tilburg 18:35 | No data | — |
| Mon 26 Oct | Tilburg 18:35 | 0 min | — |
| Fri 23 Oct | Etten-Leur 18:47 | +6 min | +6 min |
| Thu 22 Oct | Etten-Leur 18:37 | No data | — |
| Wed 21 Oct | Etten-Leur 18:35 | No data | — |
| Tue 20 Oct | Etten-Leur 18:37 | 0 min | — |
| Mon 19 Oct | Etten-Leur 18:36 | 0 min | — |
| Sun 18 Oct | Etten-Leur 18:49 | +8 min | +8 min |
| Sat 17 Oct | Etten-Leur 18:39 | No data | — |
| Fri 16 Oct | Etten-Leur 18:39Partial coverage | 0 min | — |
| Thu 15 Oct | Etten-Leur 18:56 | No data | — |
| Wed 14 Oct | Etten-Leur 18:37 | No data | — |
| Tue 13 Oct | Etten-Leur 18:36 | No data | — |