Train NS 3659 Zwolle – Roosendaal

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:50 from Zwolle · Thu 5 Nov

Next departure 16:50 today · Zwolle
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 12 full · 5 partial · 10 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 12 full · 7 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Fri 23 Oct Max en route +8 min · last fix heading to Etten-Leur +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 67% F n=3
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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:50on time on time
16:59≈ on time ≈ on time
17:06≈ on time ≈ on time
17:14 / 17:15≈ on time ≈ on time
17:26 / 17:28≈ on time ≈ +1 min
17:37≈ on time ≈ +1 min
17:49 / 17:53≈ on time ≈ +1 min
18:05 / 18:09≈ on time ≈ +1 min
18:24 / 18:25≈ on time ≈ +2 min
18:37 / 18:41≈ on time ≈ +2 min
18:56 / 18:58≈ on time ≈ +2 min
19:10 / 19:15≈ on time ≈ +2 min
19:22≈ on time ≈ +3 min
19:33on time +3 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
Wed 4 NovNijmegen 19:34No data—
Tue 3 NovNijmegen 19:34No data—
Mon 2 NovNijmegen 19:34Partial coverage0 min—
Sun 1 NovEtten-Leur 19:39+1 min+1 min
Sat 31 OctEtten-Leur 19:400 min—
Fri 30 Oct's-Hertogenbosch 18:55No data—
Thu 29 OctElst 19:34+1 min+1 min
Wed 28 OctNijmegen 19:340 min—
Tue 27 OctElst 20:39No data—
Mon 26 OctNijmegen 19:360 min—
Fri 23 OctEtten-Leur 19:50+8 min+8 min
Thu 22 Oct's-Hertogenbosch 19:35No data—
Wed 21 OctOss 19:35No data—
Tue 20 Oct's-Hertogenbosch 19:350 min—
Mon 19 Oct's-Hertogenbosch 18:55Partial coverage0 min—
Sun 18 OctEtten-Leur 19:400 min—
Sat 17 OctEtten-Leur 19:40No data—
Fri 16 OctEtten-Leur 19:360 min—
Thu 15 OctOss 18:52No data—
Wed 14 OctEtten-Leur 19:36No data—
Tue 13 OctOss 19:35No data—
Mon 12 Oct's-Hertogenbosch 19:34Partial coverage0 min—
Sun 11 OctEtten-Leur 19:39+1 min+1 min
Sat 10 OctEtten-Leur 19:41+3 min+3 min
Fri 9 OctOss 19:350 min—
Thu 8 OctArnhem Centraal 19:34Partial coverage0 min—
Wed 7 OctNijmegen 19:34Partial coverage0 min—
Tue 6 OctArnhem Centraal 19:34Partial coverage0 min—
Mon 5 OctNijmegen 19:34Partial coverage0 min—
Sun 4 OctEtten-Leur 19:41No data—