Train NS 3639 Zwolle – Roosendaal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 11: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
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 10 Oct Max en route +23 min · last fix heading to Tilburg +23 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 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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