Train NS 3644 's-Hertogenbosch – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Wijhe at 16:44 0 min

  1. 's-Hertogenbosch14:53
  2. Nijmegen15:22
  3. Arnhem Centraal15:37
  4. Zutphen16:02
  5. Deventer16:15
  6. Wijhe16:29
  7. Zwolle16:40

Next service: tomorrow 14:53 from 's-Hertogenbosch · Sun 8 Nov

Next departure 14:53 tomorrow · 's-Hertogenbosch
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 16 full · 1 partial · 11 no data
On-time · 90 days
81%
17/21 runs under 3 min
RT coverage: 20 full · 1 partial · 66 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: +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 +5 min · last fix heading to Wijhe +5 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Wijhe +5 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Wijhe +4 min
  • Sun 18 Oct Max en route +5 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 81% · 17
  • 3–10 min 19% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 67% W n=3
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • 33% 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
14:53on time on time
15:06≈ on time ≈ +1 min
15:22 / 15:24≈ on time ≈ +1 min
15:37 / 15:41≈ on time ≈ +2 min
15:52 / 15:53≈ on time ≈ +3 min
16:02 / 16:03≈ on time ≈ +3 min
16:15 / 16:16≈ on time ≈ +3 min
16:23≈ on time ≈ +4 min
16:29≈ on time ≈ +4 min
16:40on 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 16:44Partial coverage0 min+1 min
Fri 6 NovWijhe 16:44No data—
Thu 5 NovWijhe 16:49No data—
Wed 4 NovWijhe 16:49+5 min+5 min
Tue 3 NovWijhe 16:440 min—
Mon 2 NovWijhe 16:440 min—
Sun 1 NovWijhe 16:48+4 min+4 min
Sat 31 OctWijhe 16:430 min—
Fri 30 OctWijhe 16:43No data—
Thu 29 OctArnhem Zuid 15:520 min—
Wed 28 OctArnhem Zuid 15:530 min—
Tue 27 OctArnhem Zuid 15:53No data—
Mon 26 OctArnhem Zuid 15:52No data—
Fri 23 OctNijmegen 15:510 min—
Thu 22 OctNijmegen 15:43No data—
Wed 21 OctNijmegen 15:41No data—
Tue 20 OctNijmegen 15:410 min—
Mon 19 OctWijhe 16:500 min—
Sun 18 OctWijhe 16:48+4 min+5 min
Sat 17 OctWijhe 16:46No data—
Fri 16 OctWijhe 16:440 min—
Thu 15 OctWijhe 16:43No data—
Wed 14 OctWijhe 16:48No data—
Tue 13 OctWijhe 16:46No data—
Mon 12 OctWijhe 16:46+3 min+3 min
Sun 11 OctWijhe 16:44+1 min—
Sat 10 OctWijhe 16:430 min—
Fri 9 OctWijhe 16:45+1 min+2 min
Thu 8 OctWijhe 16:44+1 min—
Wed 7 OctWijhe 16:44+1 min—