Train NS 7680 Zutphen – Nijmegen

Zutphen 21:37 → Nijmegen 22:29 Daily 0 h 52 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:37 from Zutphen · Thu 5 Nov

Full trip card
Next departure 21:37 today · Zutphen
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 9 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 27 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

  • Fri 23 Oct Max en route +8 min · last fix heading to — +7 min
  • Fri 9 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 50% F n=4
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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
Zutphen
21:37on time on time
Brummen
21:42≈ on time ≈ on time
Dieren
21:47 / 21:50≈ on time ≈ on time
Rheden
21:55≈ on time ≈ on time
Velp
21:59≈ on time ≈ +1 min
Arnhem Presikhaaf
22:02≈ on time ≈ +1 min
Arnhem Velperpoort
22:05≈ on time ≈ +1 min
Arnhem Centraal
22:08 / 22:11≈ on time ≈ +1 min
Arnhem Zuid
22:16≈ on time ≈ +1 min
Elst
22:20≈ on time ≈ +1 min
Nijmegen Lent
22:25≈ on time ≈ +1 min
Nijmegen
22:29on 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
Wed 4 Nov— 22:290 min—
Mon 2 Nov— 22:290 min—
Sun 1 NovNijmegen Lent 22:390 min—
Sat 31 OctNijmegen Lent 22:390 min—
Fri 30 Oct— 22:300 min—
Thu 29 Oct— 22:30+1 min+1 min
Wed 28 Oct— 22:30No data—
Tue 27 Oct— 22:310 min—
Mon 26 Oct— 22:300 min—
Sun 25 OctNijmegen Lent 22:46No data—
Sat 24 OctNijmegen Lent 22:40No data—
Fri 23 Oct— 22:44+7 min+8 min
Thu 22 Oct— 22:31No data—
Wed 21 Oct— 22:30No data—
Tue 20 Oct— 21:53No data—
Mon 19 Oct— 22:310 min—
Sun 18 OctNijmegen Lent 22:40+1 min+1 min
Sat 17 OctNijmegen Lent 22:400 min—
Fri 16 Oct— 22:31+1 min+1 min
Thu 15 Oct— 22:31No data—
Wed 14 Oct— 22:30No data—
Tue 13 Oct— 22:30No data—
Mon 12 Oct— 22:300 min—
Sun 11 OctNijmegen Lent 22:400 min—
Sat 10 OctArnhem Velperpoort 22:31+1 min+1 min
Fri 9 Oct— 22:38+6 min+6 min
Thu 8 Oct— 22:31+1 min+1 min
Wed 7 Oct— 22:300 min—
Tue 6 Oct— 22:300 min+2 min
Mon 5 Oct— 22:300 min—