Train NS 7686 Zutphen – Nijmegen

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:07 from Zutphen · Fri 6 Nov

Full trip card
Next departure 23:07 today · Zutphen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 17 full · 4 partial · 6 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 19 full · 5 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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 16 Oct Max en route +8 min · last fix heading to — +7 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Nijmegen Lent +5 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 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, 24 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
23:07on time on time
Brummen
23:12≈ on time ≈ +1 min
Dieren
23:17 / 23:18≈ on time ≈ +1 min
Rheden
23:23≈ on time ≈ +2 min
Velp
23:27≈ on time ≈ +2 min
Arnhem Presikhaaf
23:30≈ on time ≈ +2 min
Arnhem Velperpoort
23:33≈ on time ≈ +3 min
Arnhem Centraal
23:36 / 23:41≈ on time ≈ +3 min
Arnhem Zuid
23:46≈ on time ≈ +2 min
Elst
23:50≈ on time ≈ +2 min
Nijmegen Lent
23:55≈ on time ≈ +3 min
Nijmegen
23:59on time +3 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
Thu 5 Nov— 23:59No data—
Wed 4 Nov— 23:590 min—
Mon 2 Nov— 23:59+2 min+2 min
Sun 1 NovNijmegen Lent 00:09Partial coverage0 min+2 min
Sat 31 OctZutphen 00:03Partial coverage0 min—
Fri 30 Oct— 00:010 min—
Thu 29 Oct— 00:010 min—
Tue 27 Oct— 00:000 min—
Mon 26 Oct— 00:000 min—
Sun 25 OctNijmegen Lent 00:11No data—
Sat 24 Oct— 00:010 min—
Fri 23 Oct— 00:150 min+8 min
Thu 22 Oct— 00:000 min—
Wed 21 Oct— 00:00No data—
Tue 20 Oct— 00:330 min—
Mon 19 Oct— 00:000 min—
Sun 18 OctNijmegen Lent 00:10Partial coverage0 min—
Sat 17 OctNijmegen Lent 00:11No data—
Fri 16 Oct— 00:10+7 min+8 min
Thu 15 Oct— 00:01No data—
Wed 14 Oct— 00:000 min—
Tue 13 Oct— 00:23No data—
Mon 12 Oct— 00:000 min—
Sun 11 OctNijmegen Lent 00:09Partial coverage0 min—
Sat 10 Oct— 00:01+1 min—
Fri 9 Oct— 00:09+5 min+5 min
Thu 8 Oct— 00:00+2 min+2 min
Wed 7 Oct— 00:01+2 min+3 min
Tue 6 Oct— 00:000 min—
Mon 5 OctNijmegen Lent 00:08Partial coverage+5 min+5 min