Train NS 3612 Roosendaal – Zwolle

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

It has not run yet today

Last recorded run: Wednesday 4 November +13 min

Next service: today 05:57 from Roosendaal · Thu 5 Nov

Next departure 05:57 today · Roosendaal
On-time · 30 days
85%
23/27 runs under 3 min
RT coverage: 20 full · 7 partial · 0 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 21 full · 7 partial · 55 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Sat 17 Oct Max en route +13 min · last fix heading to Wijhe +13 min
  • Wed 4 Nov Max en route +13 min · last fix heading to Wijhe +13 min
  • Mon 12 Oct Max en route +8 min · last fix heading to Wijhe +8 min
  • Sun 1 Nov Max en route +4 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 86% · 24
  • 3–10 min 7% · 2
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 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, 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
05:57on time on time
06:07≈ on time ≈ on time
06:15 / 06:19≈ on time ≈ on time
06:32 / 06:34≈ on time ≈ +1 min
06:50 / 06:54≈ on time ≈ +1 min
07:05≈ on time ≈ +1 min
07:22 / 07:24≈ on time ≈ +1 min
07:37 / 07:41≈ +1 min ≈ +2 min
07:52 / 07:53≈ +1 min ≈ +2 min
08:02 / 08:03≈ +1 min ≈ +2 min
08:15 / 08:16≈ +1 min ≈ +2 min
08:23≈ +1 min ≈ +3 min
08:29≈ +1 min ≈ +3 min
08:40+1 min +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 NovWijhe 08:58Partial coverage+13 min+13 min
Tue 3 NovWijhe 08:57Partial coverage0 min—
Mon 2 NovWijhe 08:58Partial coverage0 min—
Sun 1 NovWijhe 08:46+4 min+4 min
Sat 31 OctWijhe 08:430 min—
Fri 30 OctWijhe 08:50+2 min+3 min
Thu 29 OctArnhem Zuid 07:53+1 min—
Wed 28 OctArnhem Zuid 07:520 min—
Tue 27 OctArnhem Zuid 07:520 min—
Mon 26 OctArnhem Zuid 07:55+2 min+3 min
Fri 23 OctNijmegen 07:43+2 min+2 min
Thu 22 OctNijmegen 07:430 min—
Wed 21 OctNijmegen 07:41+1 min—
Tue 20 OctNijmegen 07:410 min—
Mon 19 OctWijhe 08:47Partial coverage0 min—
Sun 18 OctZutphen 08:47+3 min+4 min
Sat 17 OctWijhe 09:08+13 min+13 min
Fri 16 OctWijhe 08:430 min—
Thu 15 OctWijhe 08:49Partial coverage0 min—
Wed 14 OctWijhe 08:44Partial coverage0 min—
Tue 13 OctWijhe 08:490 min—
Mon 12 OctWijhe 08:47Partial coverage+8 min+8 min
Sun 11 OctWijhe 08:44+1 min—
Sat 10 OctWijhe 08:440 min+1 min
Fri 9 OctWijhe 08:48+3 min+4 min
Thu 8 OctWijhe 08:47+2 min+4 min
Wed 7 OctWijhe 08:45+1 min—
Tue 6 OctWijhe 08:47+2 min+3 min
Mon 5 OctWijhe 08:53No data—
Sun 4 OctWijhe 08:46No data—