Train NS 3676 's-Hertogenbosch – Zwolle

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

Running now · updated 00:29

Heading to Zwolle 0 min

Estimated arrival at Zwolle 00:40 · 94 km/h

  1. 's-Hertogenbosch22:53
  2. Nijmegen23:22
  3. Arnhem Centraal23:37
  4. Zutphen00:02
  5. Deventer00:15
  6. Wijhe00:29
  7. Zwolle00:40

Today it is running no worse than usual: typical arrival delay is 0 min; 78% of the last 18 runs arrived on time.

On-time · 30 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 7 no data
On-time · 90 days
73%
16/22 runs under 3 min
RT coverage: 22 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Mon 12 Oct Max en route +32 min · last fix heading to — +31 min
  • Wed 7 Oct Max en route +7 min · last fix heading to — +7 min
  • Fri 16 Oct Max en route +6 min · last fix heading to — +6 min
  • Thu 8 Oct Max en route +6 min · last fix heading to — +5 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Wijhe +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 16
  • 3–10 min 23% · 5
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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 10Today
22:53on time on time
23:06≈ on time ≈ +1 min
23:22 / 23:25≈ on time ≈ +2 min
23:37 / 23:41≈ on time ≈ +3 min
23:52 / 23:53≈ on time ≈ +4 min
00:02 / 00:03≈ on time ≈ +4 min
00:15 / 00:16≈ on time ≈ +5 min
00:23≈ on time ≈ +5 min
00:29≈ on time ≈ +6 min
00:40on time +6 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
Fri 6 Nov— 00:240 min—
Thu 5 Nov— 01:09No data—
Wed 4 Nov— 00:420 min—
Tue 3 Nov— 00:390 min—
Sun 1 NovWijhe 00:44+1 min+2 min
Sat 31 Oct's-Hertogenbosch 23:090 min—
Thu 29 Oct— 23:46+1 min—
Wed 28 Oct— 23:46No data—
Tue 27 Oct— 23:46No data—
Mon 26 Oct— 23:460 min—
Fri 23 Oct— 23:45+3 min+6 min
Thu 22 Oct— 23:40No data—
Wed 21 Oct— 23:41No data—
Tue 20 Oct— 23:420 min—
Mon 19 Oct— 23:33No data—
Sun 18 OctWijhe 00:54+5 min+6 min
Sat 17 OctNijmegen 00:470 min—
Fri 16 Oct— 00:54+6 min+6 min
Thu 15 Oct— 00:490 min—
Wed 14 Oct— 00:460 min+10 min
Tue 13 Oct— 01:02No data—
Mon 12 Oct— 01:42+31 min+32 min
Sun 11 OctWijhe 00:50+3 min+3 min
Sat 10 OctRoosendaal 00:460 min—
Fri 9 Oct— 00:51+4 min+5 min
Thu 8 Oct— 00:50+5 min+6 min
Wed 7 Oct— 00:54+7 min+7 min
Tue 6 Oct— 00:410 min+2 min
Mon 5 Oct— 22:380 min—
Sun 4 OctWijhe 00:43No data—