Train NS 3668 Roosendaal – Zwolle

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

It has not run yet today

Last recorded run: Thursday 12 November +2 min

Next service: today 19:57 from Roosendaal · Fri 13 Nov

Next departure 19:57 today · Roosendaal
On-time · 30 days
69%
11/16 runs under 3 min
RT coverage: 16 full · 0 partial · 8 no data
On-time · 90 days
71%
17/24 runs under 3 min
RT coverage: 24 full · 0 partial · 28 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +8 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 +18 min · last fix heading to Wijhe +17 min
  • Fri 23 Oct Max en route +10 min · last fix heading to — +10 min
  • Wed 4 Nov Max en route +9 min · last fix heading to — +6 min
  • Mon 9 Nov Max en route +6 min · last fix heading to — +5 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Wijhe +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 17
  • 3–10 min 25% · 6
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 67% T n=3
  • 50% W n=2
  • 100% T n=3
  • 50% F n=4
  • 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, 24 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
19:57on time on time
20:07≈ on time ≈ on time
20:15 / 20:19≈ on time ≈ +1 min
20:32 / 20:34≈ on time ≈ +1 min
20:49 / 20:55≈ on time ≈ +2 min
21:07≈ on time ≈ +2 min
21:23 / 21:24≈ on time ≈ +3 min
21:37 / 21:41≈ +1 min ≈ +3 min
21:52 / 21:53≈ +1 min ≈ +4 min
22:02 / 22:03≈ +1 min ≈ +4 min
22:15 / 22:16≈ +1 min ≈ +5 min
22:23≈ +1 min ≈ +5 min
22:29≈ +1 min ≈ +5 min
22:40+1 min +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

DateLast stopFinalMax
Thu 12 Nov— 22:44+2 min+3 min
Tue 10 Nov— 22:47+3 min+4 min
Mon 9 Nov— 22:48+5 min+6 min
Sun 8 NovWijhe 22:44+1 min+2 min
Sat 7 NovWijhe 22:43+1 min—
Fri 6 Nov— 22:390 min—
Thu 5 Nov— 22:42No data—
Wed 4 Nov— 22:49+6 min+9 min
Mon 2 Nov— 22:39+1 min—
Sun 1 NovWijhe 22:44+2 min+3 min
Sat 31 OctWijhe 22:430 min—
Fri 30 Oct— 22:17No data—
Thu 29 Oct— 21:45+1 min+1 min
Wed 28 Oct— 21:46No data—
Mon 26 Oct— 22:090 min—
Fri 23 Oct— 21:51+10 min+10 min
Thu 22 Oct— 21:41No data—
Wed 21 Oct— 21:41No data—
Tue 20 Oct— 21:400 min—
Mon 19 Oct— 20:50No data—
Sun 18 OctWijhe 23:05+17 min+18 min
Sat 17 OctWijhe 22:45No data—
Fri 16 Oct— 22:47+4 min+4 min
Thu 15 Oct— 22:41No data—
Wed 14 Oct— 22:44No data—
Tue 13 Oct— 22:46No data—
Mon 12 Oct— 22:42+1 min—
Sun 11 OctWijhe 22:47+4 min+4 min
Sat 10 OctZutphen 22:42+1 min+2 min
Fri 9 Oct— 21:490 min+1 min