Train NS 3616 Roosendaal – Zwolle

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

Running now · updated 09:12

Heading to Zwolle No data

Estimated arrival at Zwolle 09:40

  1. Roosendaal06:57
  2. Breda07:15
  3. 's-Hertogenbosch07:50
  4. Arnhem Centraal08:37
  5. Zutphen09:02
  6. Olst09:23
  7. Zwolle09:40
On-time · 30 days
88%
23/26 runs under 3 min
RT coverage: 21 full · 5 partial · 2 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 21 full · 6 partial · 60 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: +3 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

  • Sun 18 Oct Max en route +8 min · last fix heading to Wijhe +7 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Wijhe +5 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Wijhe +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 24
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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 10Today
06:57on time on time
07:07≈ on time ≈ on time
07:15 / 07:19≈ on time ≈ on time
07:32 / 07:34≈ on time ≈ on time
07:50 / 07:54≈ on time ≈ +1 min
08:05≈ on time ≈ +1 min
08:22 / 08:24≈ on time ≈ +1 min
08:37 / 08:41≈ on time ≈ +1 min
08:52 / 08:53≈ on time ≈ +1 min
09:02 / 09:03≈ on time ≈ +2 min
09:15 / 09:16≈ on time ≈ +2 min
09:23≈ on time ≈ +2 min
09:29≈ on time ≈ +2 min
09: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
Thu 5 NovZutphen 09:09No data—
Wed 4 NovWijhe 09:49Partial coverage+5 min+5 min
Tue 3 NovWijhe 09:53Partial coverage0 min—
Mon 2 NovWijhe 09:52No data—
Sun 1 NovWijhe 09:49+1 min+1 min
Sat 31 OctWijhe 09:48+3 min+5 min
Fri 30 OctWijhe 09:530 min—
Thu 29 OctArnhem Zuid 08:560 min—
Wed 28 OctArnhem Zuid 08:520 min—
Tue 27 OctArnhem Zuid 08:540 min—
Mon 26 OctArnhem Zuid 08:520 min—
Fri 23 OctNijmegen 08:420 min—
Thu 22 OctNijmegen 08:470 min—
Wed 21 OctNijmegen 08:410 min—
Tue 20 OctNijmegen 08:410 min—
Mon 19 OctWijhe 09:44Partial coverage0 min—
Sun 18 OctWijhe 09:51+7 min+8 min
Sat 17 OctWijhe 09:47+2 min+3 min
Fri 16 OctWijhe 09:440 min—
Thu 15 OctWijhe 10:580 min—
Wed 14 OctWijhe 09:510 min—
Tue 13 OctWijhe 09:470 min—
Mon 12 OctWijhe 09:440 min—
Sun 11 OctWijhe 09:440 min+1 min
Sat 10 OctWijhe 09:44+1 min—
Fri 9 OctWijhe 09:450 min+1 min
Thu 8 OctWijhe 09:43Partial coverage0 min—
Wed 7 OctWijhe 09:44Partial coverage+1 min—
Tue 6 OctWijhe 09:44Partial coverage+1 min—
Mon 5 OctWijhe 09:48No data—