Train NS 3604 Zutphen – Zwolle

Zutphen 06:03 → Zwolle 06:40 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:03 from Zutphen · Mon 9 Nov

Next departure 06:03 Monday · Zutphen
On-time · 30 days
58%
7/12 runs under 3 min
RT coverage: 4 full · 8 partial · 1 no data
On-time · 90 days
60%
9/15 runs under 3 min
RT coverage: 4 full · 11 partial · 41 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Wed 4 Nov Max en route +7 min · last fix heading to Wijhe +7 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Wijhe +6 min
  • Tue 3 Nov Max en route +6 min · last fix heading to Wijhe +6 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Wijhe +4 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Wijhe +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 60% · 9
  • 3–10 min 40% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 67% T n=3
  • 33% W n=3
  • 67% T n=3
  • 33% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 15 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:03on time on time
06:15 / 06:16— —
06:23— —
06:29— —
06:40— —

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 NovWijhe 06:47No data—
Thu 5 NovWijhe 06:53Partial coverage+1 min+1 min
Wed 4 NovWijhe 06:49Partial coverage+7 min+7 min
Tue 3 NovWijhe 06:49Partial coverage+6 min+6 min
Mon 2 NovWijhe 06:44Partial coverage0 min—
Fri 30 OctWijhe 06:48Partial coverage+4 min+4 min
Mon 19 OctWijhe 06:450 min—
Fri 16 OctWijhe 06:44+1 min—
Thu 15 OctWijhe 06:46Partial coverage+3 min+3 min
Wed 14 OctWijhe 06:47+4 min+4 min
Tue 13 OctWijhe 06:44Partial coverage+1 min—
Mon 12 OctWijhe 06:46+2 min+2 min
Fri 9 OctWijhe 06:49Partial coverage+4 min+4 min
Thu 8 OctWijhe 06:53Partial coverage+6 min+6 min
Wed 7 OctWijhe 06:44Partial coverage+1 min+1 min
Tue 6 OctWijhe 06:45Partial coverage+2 min+2 min
Mon 5 OctWijhe 06:45No data—
Fri 2 OctWijhe 06:45No data—
Thu 1 OctWijhe 06:45No data—
Wed 30 SeptWijhe 06:43No data—
Tue 29 SeptWijhe 06:45No data—
Mon 28 SeptWijhe 06:43No data—
Fri 25 SeptWijhe 06:44No data—
Thu 24 SeptWijhe 06:46No data—
Wed 23 SeptWijhe 06:44No data—
Tue 22 SeptWijhe 06:44No data—
Mon 21 SeptWijhe 06:44No data—
Fri 18 SeptWijhe 06:44No data—
Thu 17 SeptWijhe 06:46No data—
Wed 16 SeptWijhe 06:47No data—