Train NS 3665 Zwolle – 's-Hertogenbosch

Zwolle 18:20 → 's-Hertogenbosch 20:07 Daily 1 h 47 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +3 min

Next service: today 18:20 from Zwolle · Sun 8 Nov

Next departure 18:20 today · Zwolle
On-time · 30 days
75%
15/20 runs under 3 min
RT coverage: 19 full · 1 partial · 6 no data
On-time · 90 days
68%
17/25 runs under 3 min
RT coverage: 24 full · 1 partial · 42 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 's-Hertogenbosch, 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 9 Oct Max en route +11 min · last fix heading to Olst +10 min
  • Sat 31 Oct Max en route +8 min · last fix heading to Vlissingen Souburg +8 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Oss +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 17
  • 3–10 min 28% · 7
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 33% W n=3
  • 100% T n=2
  • 60% F n=5
  • 25% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 25 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
18:20on time on time
18:29≈ on time ≈ on time
18:36≈ on time ≈ +1 min
18:44 / 18:45≈ on time ≈ +1 min
18:56 / 18:58≈ on time ≈ +1 min
19:07≈ on time ≈ +2 min
19:19 / 19:23≈ on time ≈ +2 min
19:35 / 19:38≈ on time ≈ +3 min
19:53 / 19:54≈ on time ≈ +3 min
20:07on 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 NovOss 20:14Partial coverage+3 min+4 min
Fri 6 NovDeventer 22:120 min—
Thu 5 Nov— 22:14No data—
Wed 4 Nov— 22:18+4 min+4 min
Mon 2 NovOlst 22:12+1 min—
Sun 1 NovVlissingen Souburg 22:22+2 min+2 min
Sat 31 OctVlissingen Souburg 22:35+8 min+8 min
Fri 30 OctDeventer 18:590 min—
Thu 29 Oct— 22:130 min+1 min
Wed 28 Oct— 22:110 min—
Tue 27 Oct— 19:400 min—
Mon 26 Oct— 22:110 min—
Fri 23 OctArnhem Centraal 22:16+3 min+3 min
Thu 22 Oct— 22:12No data—
Wed 21 Oct— 22:17No data—
Tue 20 Oct— 22:120 min—
Mon 19 OctOlst 18:500 min—
Sun 18 OctVlissingen Souburg 22:210 min—
Sat 17 OctVlissingen Souburg 22:370 min—
Fri 16 OctOss 22:17+4 min+5 min
Thu 15 OctWijhe 20:46No data—
Wed 14 OctNijmegen 22:17No data—
Tue 13 OctOlst 22:12No data—
Mon 12 OctDeventer 19:390 min—
Sun 11 OctVlissingen Souburg 22:210 min—
Sat 10 OctMiddelburg 22:18+3 min+4 min
Fri 9 OctOlst 22:31+10 min+11 min
Thu 8 Oct— 22:17+1 min+3 min
Wed 7 Oct— 22:17+4 min+4 min
Tue 6 Oct— 22:17+4 min+4 min