Train NS 3619 Zwolle – Roosendaal

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

Running now · updated 08:12

Heading to Roosendaal No data

Estimated arrival at Roosendaal 09:33 · 43 km/h

  1. Zwolle06:50
  2. Olst07:06
  3. Zutphen07:26
  4. Nijmegen08:05
  5. 's-Hertogenbosch08:37
  6. Breda09:10
  7. Roosendaal09:33
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 17 full · 6 partial · 6 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 17 full · 8 partial · 63 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 17 Oct Max en route +9 min · last fix heading to Etten-Leur +9 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Etten-Leur +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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