Train NS 3656 Roosendaal – Zwolle

Roosendaal 16:57 → Zwolle 19:40 Daily 2 h 43 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 16:57 from Roosendaal · Sat 14 Nov

Next departure 16:57 today · Roosendaal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 15 full · 5 partial · 7 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 21 full · 7 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Fri 6 Nov Max en route +10 min · last fix heading to Arnhem Centraal +9 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Wijhe +4 min

Distribution · 90 days

28 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=4
  • 100% T n=3
  • 80% F n=5
  • 100% S n=4
  • 75% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 stops).

Last 90 days, 28 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.

StopSched.Usually 9 days in 10
16:57on time on time
17:07≈ on time ≈ on time
17:15 / 17:19≈ on time ≈ on time
17:32 / 17:34≈ on time ≈ +1 min
17:49 / 17:55≈ on time ≈ +1 min
18:06≈ on time ≈ +1 min
18:23 / 18:24≈ on time ≈ +1 min
18:37 / 18:41≈ on time ≈ +1 min
18:52 / 18:53≈ on time ≈ +2 min
19:02 / 19:03≈ on time ≈ +2 min
19:15 / 19:16≈ on time ≈ +2 min
19:23≈ on time ≈ +2 min
19:29≈ on time ≈ +2 min
19:40on 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

DateLast stopFinalMax
Fri 13 NovDieren 20:09Partial coverage0 min+15 min
Thu 12 NovOss 18:190 min—
Wed 11 NovOss 19:47+2 min+4 min
Tue 10 NovOss 19:47+2 min+4 min
Mon 9 NovOss 19:420 min—
Sun 8 NovWijhe 19:430 min—
Sat 7 NovWijhe 19:440 min+2 min
Fri 6 NovArnhem Centraal 19:59Partial coverage+9 min+10 min
Thu 5 NovOss 19:44No data—
Wed 4 NovOss 18:19No data—
Tue 3 NovOss 19:44No data—
Mon 2 NovOss 19:420 min—
Sun 1 NovDeventer 19:59Partial coverage0 min+14 min
Sat 31 OctWijhe 19:44+1 min—
Fri 30 OctEtten-Leur 19:42No data—
Thu 29 OctRoosendaal 18:440 min—
Wed 28 OctEtten-Leur 18:46+1 min—
Tue 27 Oct's-Hertogenbosch 19:400 min—
Mon 26 Oct's-Hertogenbosch 18:420 min—
Fri 23 OctNijmegen 18:400 min—
Thu 22 OctNijmegen 18:43No data—
Wed 21 OctNijmegen 18:45No data—
Tue 20 OctBreda 18:55No data—
Mon 19 OctArnhem Centraal 18:550 min—
Sun 18 OctWijhe 19:50Partial coverage+4 min+5 min
Sat 17 OctWijhe 19:430 min—
Fri 16 OctWijhe 19:47Partial coverage0 min—
Thu 15 OctNijmegen 19:46No data—
Wed 14 OctTilburg 19:480 min—
Tue 13 OctNijmegen 19:41No data—