Train NS 7626 Zutphen – Nijmegen

Zutphen 08:07 → Nijmegen 08:59 Daily 0 h 52 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +1 min

Next service: today 08:07 from Zutphen · Mon 16 Nov

Next departure 08:07 today · Zutphen
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 21 full · 2 partial · 6 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 27 full · 3 partial · 56 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: +2 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 +11 min · last fix heading to Nijmegen Dukenburg +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 75% T n=4
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 30 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
08:07on time on time
08:12≈ on time ≈ on time
08:17 / 08:18≈ on time ≈ on time
08:23≈ on time ≈ on time
08:27≈ on time ≈ +1 min
08:30≈ on time ≈ +1 min
08:33≈ on time ≈ +1 min
08:36 / 08:41≈ on time ≈ +1 min
08:46≈ on time ≈ +1 min
08:50≈ on time ≈ +1 min
08:55≈ on time ≈ +1 min
08:59on 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
Sun 15 NovNijmegen Lent 09:09Partial coverage+1 min—
Sat 14 NovNijmegen Dukenburg 09:190 min—
Fri 13 NovNijmegen Dukenburg 09:24+3 min+3 min
Thu 12 NovNijmegen Dukenburg 09:22+2 min+2 min
Wed 11 NovNijmegen Dukenburg 09:190 min—
Tue 10 NovNijmegen Dukenburg 09:29+9 min+11 min
Mon 9 NovNijmegen Dukenburg 09:190 min—
Sun 8 NovNijmegen Lent 09:09Partial coverage+1 min+1 min
Sat 7 NovNijmegen Dukenburg 09:190 min—
Fri 6 NovNijmegen Dukenburg 09:39No data—
Thu 5 NovNijmegen Dukenburg 09:24No data—
Wed 4 NovNijmegen Dukenburg 09:19+1 min+1 min
Tue 3 NovNijmegen Dukenburg 09:190 min—
Mon 2 NovNijmegen Dukenburg 09:190 min—
Sun 1 NovNijmegen Lent 09:090 min—
Sat 31 OctNijmegen Dukenburg 09:210 min—
Fri 30 OctNijmegen Dukenburg 09:230 min—
Thu 29 OctNijmegen Dukenburg 09:220 min—
Wed 28 OctNijmegen Dukenburg 09:220 min—
Tue 27 OctNijmegen Dukenburg 09:22No data—
Mon 26 OctNijmegen Dukenburg 09:21No data—
Sun 25 OctNijmegen Lent 09:10No data—
Sat 24 OctNijmegen Dukenburg 09:220 min—
Fri 23 OctNijmegen Dukenburg 09:21No data—
Thu 22 OctNijmegen Dukenburg 09:220 min—
Wed 21 OctNijmegen Dukenburg 09:220 min—
Tue 20 OctNijmegen Dukenburg 09:210 min—
Mon 19 OctNijmegen Dukenburg 09:230 min—
Sun 18 OctNijmegen Lent 09:090 min—
Sat 17 OctNijmegen Dukenburg 09:210 min—