Train NS 3653 Zwolle – 's-Hertogenbosch

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

✓ Today’s run finished

Today, last fix heading to Oss at 17:09 0 min

  1. Zwolle15:20
  2. Olst15:36
  3. Deventer15:44
  4. Dieren16:07
  5. Arnhem Centraal16:19
  6. Oss16:53
  7. 's-Hertogenbosch17:07

Next service: tomorrow 15:20 from Zwolle · Mon 9 Nov

Next departure 15:20 tomorrow · Zwolle
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 18 full · 2 partial · 8 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 23 full · 2 partial · 62 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: +2 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 +9 min · last fix heading to Krabbendijke +9 min
  • Sat 31 Oct Max en route +9 min · last fix heading to Vlissingen Souburg +7 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Vlissingen Souburg +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 88% · 22
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 80% F n=5
  • 33% 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, 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
15:20on time on time
15:29≈ on time ≈ on time
15:36≈ on time ≈ +1 min
15:44 / 15:45≈ on time ≈ +1 min
15:56 / 15:58≈ on time ≈ +1 min
16:07≈ on time ≈ +2 min
16:19 / 16:23≈ on time ≈ +2 min
16:35 / 16:38≈ on time ≈ +3 min
16:53 / 16:54≈ on time ≈ +3 min
17: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
Sun 8 NovOss 17:09Partial coverage0 min—
Sat 7 NovOss 17:08Partial coverage0 min—
Fri 6 NovKapelle-Biezelinge 19:120 min—
Thu 5 NovRoosendaal 18:39No data—
Wed 4 NovRoosendaal 19:140 min—
Tue 3 NovRoosendaal 19:12No data—
Mon 2 NovRoosendaal 19:240 min—
Sun 1 NovVlissingen Souburg 19:190 min—
Sat 31 OctVlissingen Souburg 19:28+7 min+9 min
Fri 30 OctGoes 19:150 min—
Thu 29 OctEtten-Leur 19:13+1 min+3 min
Wed 28 OctRoosendaal 19:120 min—
Tue 27 OctEtten-Leur 19:130 min—
Mon 26 OctEtten-Leur 19:460 min—
Fri 23 OctVlissingen Souburg 19:22+2 min+2 min
Thu 22 OctKapelle-Biezelinge 19:13No data—
Wed 21 OctArnhem Centraal 19:16No data—
Tue 20 OctKapelle-Biezelinge 18:50No data—
Mon 19 OctKapelle-Biezelinge 18:570 min—
Sun 18 OctVlissingen Souburg 19:200 min—
Sat 17 OctVlissingen Souburg 19:20No data—
Fri 16 OctVlissingen Souburg 19:350 min—
Thu 15 OctRilland-Bath 19:130 min—
Wed 14 OctVlissingen Souburg 19:22No data—
Tue 13 OctKruiningen-Yerseke 19:13No data—
Mon 12 OctKapelle-Biezelinge 18:570 min+2 min
Sun 11 OctVlissingen Souburg 19:200 min—
Sat 10 OctVlissingen Souburg 19:25+4 min+5 min
Fri 9 OctKrabbendijke 19:22+9 min+9 min
Thu 8 OctEtten-Leur 19:12+1 min+1 min