Train NS 5615 Amersfoort Centraal – Zwolle

Amersfoort Centraal 06:12 → Zwolle 07:06 Mon, Tue, Wed, Thu, Fri, Sat 0 h 54 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 06:12 from Amersfoort Centraal · Mon 9 Nov

Next departure 06:12 tomorrow · Amersfoort Centraal
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 19 full · 4 partial · 2 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 23 full · 4 partial · 48 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: +4 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 14 Oct Max en route +21 min · last fix heading to Ermelo +21 min
  • Mon 19 Oct Max en route +5 min · last fix heading to Wezep +5 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Wezep +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 24
  • 3–10 min 7% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 80% W n=5
  • 80% T n=5
  • 100% F n=4
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 27 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:12on time on time
06:16≈ on time ≈ on time
06:19≈ on time ≈ +1 min
06:24≈ on time ≈ +1 min
06:29≈ on time ≈ +1 min
06:34≈ on time ≈ +2 min
06:38≈ on time ≈ +2 min
06:46≈ on time ≈ +3 min
06:52≈ on time ≈ +3 min
06:59≈ on time ≈ +4 min
07:06on 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
Sat 7 NovWezep 07:14Partial coverage0 min—
Fri 6 NovWezep 07:14No data—
Thu 5 NovWezep 07:140 min—
Wed 4 NovWezep 07:140 min—
Tue 3 NovWezep 07:14No data—
Mon 2 NovWezep 07:140 min—
Sat 31 OctWezep 07:15Partial coverage0 min—
Fri 30 OctWezep 07:140 min—
Thu 29 OctWezep 07:140 min—
Wed 28 OctHarderwijk 07:440 min+19 min
Tue 27 OctWezep 07:16+2 min+2 min
Mon 26 OctWezep 07:140 min—
Sat 24 OctWezep 07:14Partial coverage0 min—
Fri 23 OctWezep 07:140 min—
Thu 22 OctWezep 07:140 min—
Wed 21 OctWezep 07:140 min—
Tue 20 OctWezep 07:140 min—
Mon 19 OctWezep 07:19+5 min+5 min
Sat 17 OctWezep 07:140 min—
Fri 16 OctWezep 07:120 min—
Thu 15 OctWezep 07:15+5 min+5 min
Wed 14 OctErmelo 07:57+21 min+21 min
Tue 13 OctWezep 07:120 min—
Mon 12 OctWezep 07:120 min—
Sat 10 OctWezep 07:14Partial coverage0 min—
Fri 9 OctWezep 07:140 min—
Thu 8 OctWezep 07:15+1 min+1 min
Wed 7 OctWezep 07:140 min—
Tue 6 OctWezep 07:140 min+1 min
Mon 5 OctWezep 07:15No data—