Train NS 3636 's-Hertogenbosch – Zwolle

's-Hertogenbosch 12:53 → Zwolle 14:40 Daily 1 h 47 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 12:53 from 's-Hertogenbosch · Sun 8 Nov

Next departure 12:53 today · 's-Hertogenbosch
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 15 full · 1 partial · 11 no data
On-time · 90 days
86%
18/21 runs under 3 min
RT coverage: 20 full · 1 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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 +8 min · last fix heading to Wijhe +5 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Wijhe +5 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Wijhe +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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