Train NS 3638 's-Hertogenbosch – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Wijhe at 15:14 0 min

  1. 's-Hertogenbosch13:23
  2. Nijmegen13:52
  3. Arnhem Centraal14:07
  4. Zutphen14:32
  5. Deventer14:45
  6. Wijhe14:59
  7. Zwolle15:10

Next service: tomorrow 13:23 from 's-Hertogenbosch · Mon 9 Nov

Next departure 13:23 tomorrow · 's-Hertogenbosch
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 9 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 23 full · 1 partial · 63 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: +4 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 +18 min · last fix heading to Wijhe +17 min
  • Sat 10 Oct Max en route +10 min · last fix heading to Wijhe +9 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Wijhe +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
13:23on time on time
13:36≈ on time ≈ on time
13:52 / 13:54≈ on time ≈ +1 min
14:07 / 14:11≈ on time ≈ +1 min
14:22 / 14:23≈ on time ≈ +2 min
14:32 / 14:33≈ on time ≈ +2 min
14:45 / 14:46≈ on time ≈ +2 min
14:53≈ on time ≈ +3 min
14:59≈ on time ≈ +3 min
15:10on 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
Sun 8 NovWijhe 15:14Partial coverage0 min+2 min
Sat 7 NovWijhe 15:14+1 min—
Fri 6 NovWijhe 15:14No data—
Thu 5 NovWijhe 15:14No data—
Wed 4 NovWijhe 15:29+17 min+18 min
Tue 3 NovWijhe 15:20No data—
Mon 2 NovWijhe 15:180 min—
Sun 1 NovWijhe 15:16+1 min+1 min
Sat 31 OctWijhe 15:140 min+3 min
Fri 30 OctWijhe 15:180 min—
Thu 29 OctArnhem Zuid 14:220 min—
Wed 28 OctArnhem Zuid 14:270 min—
Tue 27 OctArnhem Zuid 14:230 min—
Mon 26 OctArnhem Zuid 14:220 min—
Fri 23 OctNijmegen 14:190 min—
Thu 22 OctNijmegen 14:11No data—
Wed 21 OctNijmegen 14:11No data—
Tue 20 OctNijmegen 14:110 min—
Mon 19 OctWijhe 15:150 min—
Sun 18 OctWijhe 15:17+2 min+4 min
Sat 17 OctWijhe 15:16No data—
Fri 16 OctWijhe 15:160 min—
Thu 15 OctWijhe 15:150 min—
Wed 14 OctWijhe 15:15No data—
Tue 13 OctWijhe 15:14No data—
Mon 12 OctWijhe 15:17No data—
Sun 11 OctWijhe 15:17+2 min+4 min
Sat 10 OctWijhe 15:27+9 min+10 min
Fri 9 OctWijhe 15:18+3 min+5 min
Thu 8 OctWijhe 15:150 min+1 min