Train NS 3623 Zwolle – 's-Hertogenbosch

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

✓ Today’s run finished

Today, last fix heading to Oss at 09:38 +1 min

  1. Zwolle07:50
  2. Olst08:06
  3. Deventer08:14
  4. Dieren08:37
  5. Arnhem Centraal08:49
  6. Oss09:23
  7. 's-Hertogenbosch09:37

Next service: tomorrow 07:50 from Zwolle · Sun 8 Nov

Next departure 07:50 tomorrow · Zwolle
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 7 no data
On-time · 90 days
92%
22/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
+2min
9 in 10 runs arrive with less than this
30 days: +1 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 +22 min · last fix heading to Etten-Leur +22 min
  • Wed 4 Nov Max en route +16 min · last fix heading to Etten-Leur +15 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 92% · 22
  • 3–10 min 0% · 0
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 75% W n=4
  • 100% T n=2
  • 75% F n=4
  • 100% 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, 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
07:50on time on time
07:59≈ on time ≈ on time
08:06≈ on time ≈ on time
08:14 / 08:15≈ on time ≈ on time
08:26 / 08:28≈ on time ≈ +1 min
08:37≈ on time ≈ +1 min
08:49 / 08:53≈ on time ≈ +1 min
09:05 / 09:08≈ on time ≈ +2 min
09:23 / 09:24≈ on time ≈ +2 min
09:37on time +2 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 09:38Partial coverage+1 min+1 min
Fri 6 NovEtten-Leur 10:39No data—
Thu 5 NovEtten-Leur 10:39No data—
Wed 4 NovEtten-Leur 10:54+15 min+16 min
Tue 3 NovEtten-Leur 10:400 min—
Mon 2 NovEtten-Leur 10:390 min—
Sun 1 NovEtten-Leur 10:400 min—
Sat 31 OctEtten-Leur 10:390 min—
Fri 30 OctEtten-Leur 10:390 min—
Thu 29 OctEtten-Leur 10:39No data—
Wed 28 OctEtten-Leur 10:390 min—
Tue 27 OctEtten-Leur 10:39No data—
Mon 26 OctEtten-Leur 10:390 min—
Fri 23 OctEtten-Leur 10:400 min—
Thu 22 OctEtten-Leur 10:540 min—
Wed 21 OctEtten-Leur 10:40No data—
Tue 20 OctEtten-Leur 10:400 min—
Mon 19 OctEtten-Leur 10:390 min—
Sun 18 OctEtten-Leur 10:400 min—
Sat 17 OctEtten-Leur 10:400 min—
Fri 16 OctEtten-Leur 10:390 min—
Thu 15 OctOss 10:58No data—
Wed 14 OctEtten-Leur 10:390 min—
Tue 13 OctEtten-Leur 10:39No data—
Mon 12 OctEtten-Leur 10:390 min—
Sun 11 OctEtten-Leur 10:400 min—
Sat 10 OctEtten-Leur 10:400 min—
Fri 9 OctEtten-Leur 11:03+22 min+22 min
Thu 8 OctEtten-Leur 10:390 min—
Wed 7 OctBreda 12:000 min—