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 6 November No data

Next service: tomorrow 05:37 from Zutphen · Mon 9 Nov

Next departure 05:37 tomorrow · Zutphen
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 6 full · 12 partial · 2 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 6 full · 16 partial · 41 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 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 10
05:37on time on time
05:42≈ on time ≈ on time
05:47 / 05:48≈ on time ≈ on time
05:53≈ on time ≈ on time
05:57≈ on time ≈ on time
06:00≈ on time ≈ +1 min
06:03≈ on time ≈ +1 min
06:06 / 06:11≈ on time ≈ +1 min
06:16≈ on time ≈ +1 min
06:20≈ on time ≈ +1 min
06:25≈ on time ≈ +1 min
06:28on time +1 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 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—
Fri 9 OctNijmegen Lent 06:39Partial coverage0 min—
Thu 8 OctNijmegen Lent 06:40Partial coverage0 min—
Wed 7 OctNijmegen Lent 06:39Partial coverage0 min—
Tue 6 OctNijmegen Lent 06:39Partial coverage0 min—
Mon 5 OctNijmegen Lent 06:40No data—
Fri 2 OctNijmegen Lent 06:39No data—
Thu 1 OctNijmegen Lent 06:39No data—
Wed 30 SeptNijmegen Lent 06:39No data—
Tue 29 SeptNijmegen Lent 06:39No data—
Mon 28 SeptNijmegen Lent 06:43No data—