Train NS 3608 Nijmegen – Zwolle

Nijmegen 06:24 → Zwolle 07:40 Daily 1 h 16 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Wijhe at 07:44 +2 min

  1. Nijmegen06:24
  2. Arnhem Centraal06:37
  3. Dieren06:52
  4. Deventer07:15
  5. Olst07:23
  6. Wijhe07:29
  7. Zwolle07:40

Next service: tomorrow 06:24 from Nijmegen · Sat 21 Nov

Next departure 06:24 tomorrow · Nijmegen
On-time · 30 days
52%
13/25 runs under 3 min
RT coverage: 12 full · 13 partial · 3 no data
On-time · 90 days
66%
27/41 runs under 3 min
RT coverage: 23 full · 18 partial · 42 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +3 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Tue 17 Nov Max en route +10 min · last fix heading to Wijhe +10 min
  • Wed 4 Nov Max en route +9 min · last fix heading to Wijhe +9 min
  • Wed 18 Nov Max en route +9 min · last fix heading to Wijhe +9 min
  • Tue 10 Nov Max en route +9 min · last fix heading to Wijhe +9 min
  • Tue 3 Nov Max en route +8 min · last fix heading to Wijhe +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 66% · 27
  • 3–10 min 32% · 13
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 33% T n=6
  • 71% W n=7
  • 100% T n=6
  • 67% F n=6
  • 80% S n=5
  • 40% S n=5

Stops and timetable

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

Last 90 days, 41 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
06:24on time on time
06:37 / 06:41≈ on time ≈ +1 min
06:52 / 06:53≈ on time ≈ +2 min
07:02 / 07:03≈ on time ≈ +3 min
07:15 / 07:16≈ on time ≈ +3 min
07:23≈ on time ≈ +4 min
07:29≈ on time ≈ +4 min
07: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
Fri 20 NovWijhe 07:44Partial coverage+2 min+3 min
Thu 19 NovWijhe 07:44Partial coverage+2 min+2 min
Wed 18 NovWijhe 07:52Partial coverage+9 min+9 min
Tue 17 NovWijhe 07:54Partial coverage+10 min+10 min
Mon 16 NovWijhe 07:49Partial coverage+7 min+7 min
Sun 15 NovWijhe 07:47+6 min+6 min
Sat 14 NovWijhe 07:44+3 min+3 min
Fri 13 NovWijhe 07:48Partial coverage+4 min+5 min
Thu 12 NovWijhe 07:44Partial coverage+3 min+3 min
Wed 11 NovWijhe 07:44Partial coverage+1 min+2 min
Tue 10 NovWijhe 07:52Partial coverage+9 min+9 min
Mon 9 NovWijhe 07:47Partial coverage+4 min+4 min
Sun 8 NovWijhe 07:47+4 min+4 min
Sat 7 NovWijhe 07:44+1 min+2 min
Fri 6 NovWijhe 07:49No data—
Thu 5 NovOlst 08:29No data—
Wed 4 NovWijhe 07:54Partial coverage+9 min+9 min
Tue 3 NovWijhe 07:58Partial coverage+8 min+8 min
Mon 2 NovWijhe 07:48Partial coverage0 min—
Sun 1 NovWijhe 07:430 min—
Sat 31 OctWijhe 07:45+1 min+2 min
Fri 30 OctArnhem Zuid 07:52+5 min+5 min
Thu 29 OctArnhem Zuid 06:530 min+1 min
Wed 28 OctArnhem Zuid 06:530 min+1 min
Tue 27 OctArnhem Zuid 06:51No data—
Mon 26 OctArnhem Zuid 06:52+1 min—
Fri 23 OctNijmegen 06:410 min—
Thu 22 OctNijmegen 06:410 min—
Wed 21 OctNijmegen 06:410 min—
Tue 20 OctNijmegen 06:41+1 min—