Train NS 3654 's-Hertogenbosch – Zwolle

's-Hertogenbosch 17:23 → Zwolle 19:10 Daily 1 h 47 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 17:23 from 's-Hertogenbosch · Sun 8 Nov

Next departure 17:23 today · 's-Hertogenbosch
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 16 full · 1 partial · 10 no data
On-time · 90 days
82%
18/22 runs under 3 min
RT coverage: 21 full · 1 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 6 Nov Max en route +12 min · last fix heading to Deventer +10 min
  • Sat 10 Oct Max en route +9 min · last fix heading to Wijhe +5 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Wijhe +5 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Wijhe +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 18
  • 3–10 min 14% · 3
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=1
  • 100% W n=3
  • 100% T n=1
  • 80% F n=5
  • 75% S n=4
  • 33% S n=3

Stops and timetable

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

Last 90 days, 22 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
17:23on time on time
17:36≈ on time ≈ +1 min
17:52 / 17:54≈ on time ≈ +1 min
18:07 / 18:11≈ on time ≈ +2 min
18:22 / 18:23≈ on time ≈ +3 min
18:32 / 18:33≈ on time ≈ +3 min
18:45 / 18:46≈ on time ≈ +4 min
18:53≈ on time ≈ +4 min
18:59≈ on time ≈ +5 min
19:10on time +5 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 19:13Partial coverage0 min—
Fri 6 NovDeventer 19:29+10 min+12 min
Thu 5 NovArnhem Centraal 19:12No data—
Wed 4 NovArnhem Centraal 19:140 min—
Tue 3 NovArnhem Centraal 19:09No data—
Mon 2 NovNijmegen 19:09+1 min—
Sun 1 NovWijhe 19:18+5 min+5 min
Sat 31 OctWijhe 19:14+1 min+1 min
Fri 30 OctOlst 19:070 min—
Thu 29 OctElst 18:16No data—
Wed 28 OctArnhem Zuid 18:20No data—
Tue 27 OctElst 18:23No data—
Mon 26 OctArnhem Zuid 18:200 min—
Fri 23 OctNijmegen 18:210 min—
Thu 22 OctNijmegen 18:11No data—
Wed 21 OctNijmegen 18:150 min—
Tue 20 OctNijmegen 18:10No data—
Mon 19 OctZutphen 18:470 min—
Sun 18 OctWijhe 19:19+5 min+5 min
Sat 17 OctWijhe 19:150 min—
Fri 16 OctWijhe 19:170 min—
Thu 15 OctDieren 19:11No data—
Wed 14 OctOss 19:12No data—
Tue 13 OctZutphen 19:14No data—
Mon 12 OctZutphen 19:120 min—
Sun 11 OctWijhe 19:16+3 min+3 min
Sat 10 OctWijhe 19:20+5 min+9 min
Fri 9 OctZutphen 19:110 min+1 min
Thu 8 OctNijmegen 19:12+1 min—
Wed 7 OctNijmegen 19:110 min+1 min