Train NS 3631 Zwolle – Roosendaal

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

It has not run yet today

Last recorded run: Wednesday 4 November +9 min

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

Next departure 09:50 today · Zwolle
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 15 full · 2 partial · 10 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 16 full · 3 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

  • Wed 4 Nov Max en route +9 min · last fix heading to Etten-Leur +9 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Etten-Leur +3 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 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 75% W n=4
  • 100% T n=2
  • 50% F n=2
  • 100% S n=3
  • 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
09:50on time on time
09:59≈ on time ≈ on time
10:06≈ on time ≈ on time
10:14 / 10:15≈ on time ≈ on time
10:26 / 10:28≈ on time ≈ on time
10:37≈ on time ≈ on time
10:49 / 10:53≈ on time ≈ +1 min
11:05 / 11:09≈ on time ≈ +1 min
11:24 / 11:25≈ on time ≈ +1 min
11:37 / 11:41≈ on time ≈ +1 min
11:56 / 11:58≈ on time ≈ +1 min
12:10 / 12:15≈ on time ≈ +1 min
12:22≈ on time ≈ +1 min
12:33on 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
Wed 4 NovEtten-Leur 12:49Partial coverage+9 min+9 min
Tue 3 NovEtten-Leur 12:39No data—
Mon 2 NovEtten-Leur 12:39No data—
Sun 1 NovEtten-Leur 12:42+1 min+1 min
Sat 31 OctEtten-Leur 12:400 min—
Fri 30 OctEtten-Leur 12:42No data—
Thu 29 OctEtten-Leur 12:39No data—
Wed 28 OctEtten-Leur 12:390 min—
Tue 27 OctEtten-Leur 12:390 min—
Mon 26 OctEtten-Leur 12:360 min—
Fri 23 OctEtten-Leur 12:40No data—
Thu 22 OctEtten-Leur 12:39No data—
Wed 21 OctEtten-Leur 12:430 min—
Tue 20 OctEtten-Leur 12:40No data—
Mon 19 OctEtten-Leur 12:390 min—
Sun 18 OctEtten-Leur 12:400 min—
Sat 17 OctEtten-Leur 12:400 min—
Fri 16 OctEtten-Leur 12:390 min—
Thu 15 OctEtten-Leur 12:410 min—
Wed 14 OctEtten-Leur 12:39No data—
Tue 13 OctEtten-Leur 12:40No data—
Mon 12 OctEtten-Leur 12:39No data—
Sun 11 OctEtten-Leur 12:40+1 min+1 min
Sat 10 OctEtten-Leur 12:40+2 min+2 min
Fri 9 OctEtten-Leur 12:40+3 min+3 min
Thu 8 OctEtten-Leur 12:40+1 min+1 min
Wed 7 OctEtten-Leur 12:39Partial coverage0 min—
Tue 6 OctEtten-Leur 12:39Partial coverage0 min—
Mon 5 OctEtten-Leur 12:39+1 min+1 min
Sun 4 OctEtten-Leur 12:40No data—