Train NS 7616 Zutphen – Nijmegen

Zutphen 05:37 → Nijmegen 06:28 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 05:37 from Zutphen · Mon 23 Nov

Next departure 05:37 Monday · Zutphen
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 2 full · 17 partial · 2 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 7 full · 25 partial · 32 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: +3 min

Last 30 days

Arrival delay at Nijmegen, 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 10 Nov Max en route +8 min · last fix heading to Nijmegen Lent +8 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Nijmegen Lent +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 86% T n=7
  • 100% W n=7
  • 100% T n=7
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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
05:37on time on time
05:42≈ on time ≈ on time
05:47 / 05:48≈ on time ≈ +1 min
05:53≈ on time ≈ +1 min
05:57≈ on time ≈ +2 min
06:00≈ on time ≈ +2 min
06:03≈ on time ≈ +2 min
06:06 / 06:11≈ on time ≈ +2 min
06:16≈ on time ≈ +3 min
06:20≈ on time ≈ +3 min
06:25≈ on time ≈ +4 min
06:28on 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
Fri 20 NovNijmegen Lent 06:39Partial coverage0 min—
Thu 19 NovNijmegen Lent 06:39Partial coverage0 min—
Wed 18 NovNijmegen Lent 06:39Partial coverage0 min—
Tue 17 NovNijmegen Lent 06:39Partial coverage+2 min+2 min
Mon 16 NovNijmegen Lent 06:39Partial coverage+2 min+2 min
Fri 13 NovNijmegen Lent 06:42Partial coverage+4 min+4 min
Thu 12 NovNijmegen Lent 06:39Partial coverage+1 min+1 min
Wed 11 NovNijmegen Lent 06:39Partial coverage0 min—
Tue 10 NovNijmegen Lent 06:44+8 min+8 min
Mon 9 NovNijmegen Lent 06:39Partial coverage+1 min+1 min
Fri 6 NovNijmegen Lent 06:39No data—
Thu 5 NovNijmegen Lent 06:39Partial coverage0 min—
Wed 4 NovNijmegen Lent 06:39Partial coverage0 min—
Tue 3 NovNijmegen Lent 06:39Partial coverage+1 min+1 min
Mon 2 NovNijmegen Lent 06:39No data—
Fri 30 OctNijmegen Lent 06:39Partial coverage0 min—
Thu 29 OctNijmegen Lent 06:39Partial coverage0 min—
Wed 28 OctNijmegen Lent 06:39Partial coverage0 min—
Tue 27 OctNijmegen Lent 06:39Partial coverage0 min—
Mon 26 OctNijmegen Lent 06:39Partial coverage+1 min+1 min
Fri 23 OctNijmegen Lent 06:41+1 min+1 min
Thu 22 OctNijmegen Lent 06:410 min—
Wed 21 OctNijmegen Lent 06:41+1 min—
Tue 20 OctNijmegen Lent 06:410 min—
Mon 19 OctNijmegen Lent 06:39Partial coverage0 min—
Fri 16 OctNijmegen Lent 06:390 min—
Thu 15 OctNijmegen Lent 06:39Partial coverage0 min—
Wed 14 OctNijmegen Lent 06:39Partial coverage0 min—
Tue 13 OctNijmegen Lent 06:39Partial coverage0 min—
Mon 12 OctNijmegen Lent 06:390 min—