Train NS 3635 Zwolle – Roosendaal

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 10:50 from Zwolle · Sat 7 Nov

Next departure 10:50 today · Zwolle
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 11 full · 3 partial · 13 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 12 full · 6 partial · 68 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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