Train NS 3640 Roosendaal – Zwolle

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

Running now · updated 14:01

Heading to Zwolle 0 min

Estimated arrival at Zwolle 15:40 · 104 km/h

  1. Roosendaal12:57
  2. Breda13:15
  3. 's-Hertogenbosch13:49
  4. Arnhem Centraal14:37
  5. Zutphen15:02
  6. Olst15:23
  7. Zwolle15:40

Today it is running no worse than usual: typical arrival delay is 0 min; 87% of the last 15 runs arrived on time.

On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 11 full · 4 partial · 13 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 17 full · 6 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 4 Nov Max en route +9 min · last fix heading to Wijhe +8 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Wijhe +4 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Arnhem Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 75% W n=4
  • 50% T n=2
  • 100% F n=3
  • 67% S n=3
  • 100% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 stops).

Last 90 days, 23 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
12:57on time on time
13:07≈ on time ≈ on time
13:15 / 13:19≈ on time ≈ on time
13:32 / 13:34≈ on time ≈ +1 min
13:49 / 13:55≈ on time ≈ +1 min
14:06≈ on time ≈ +1 min
14:23 / 14:24≈ on time ≈ +2 min
14:37 / 14:41≈ on time ≈ +2 min
14:52 / 14:53≈ on time ≈ +2 min
15:02 / 15:03≈ on time ≈ +3 min
15:15 / 15:16≈ on time ≈ +3 min
15:23≈ on time ≈ +3 min
15:29≈ on time ≈ +3 min
15:40on 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 13 Nov's-Hertogenbosch 13:59Partial coverage0 min—
Thu 12 NovWijhe 15:44+1 min—
Wed 11 NovWijhe 15:440 min—
Tue 10 NovWijhe 15:430 min—
Mon 9 NovWijhe 15:440 min—
Sun 8 NovWijhe 15:440 min—
Sat 7 NovWijhe 15:430 min—
Fri 6 NovWijhe 15:44No data—
Thu 5 NovWijhe 15:44No data—
Wed 4 NovWijhe 15:59+8 min+9 min
Tue 3 NovWijhe 15:44No data—
Mon 2 NovWijhe 15:44No data—
Sun 1 NovWijhe 15:45Partial coverage+1 min—
Sat 31 OctArnhem Zuid 15:47+3 min+4 min
Fri 30 OctWijhe 15:45No data—
Thu 29 OctArnhem Zuid 14:52No data—
Wed 28 OctArnhem Zuid 14:530 min—
Tue 27 OctArnhem Zuid 14:53No data—
Mon 26 OctArnhem Zuid 14:520 min—
Fri 23 OctNijmegen 14:41No data—
Thu 22 OctNijmegen 14:40No data—
Wed 21 OctNijmegen 14:41No data—
Tue 20 OctNijmegen 14:42No data—
Mon 19 OctWijhe 15:450 min—
Sun 18 OctWijhe 15:46Partial coverage+1 min+3 min
Sat 17 OctWijhe 15:47No data—
Fri 16 OctWijhe 15:44Partial coverage0 min—
Thu 15 OctWijhe 15:47No data—
Wed 14 OctWijhe 15:45No data—
Tue 13 OctWijhe 15:44No data—