Train NS 7668 Zutphen – Nijmegen

Zutphen 18:37 → Nijmegen 19:28 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 18:37 from Zutphen · Sun 8 Nov

Next departure 18:37 today · Zutphen
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 11 full · 5 partial · 11 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 16 full · 5 partial · 44 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: +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

Worst days

  • Thu 8 Oct Max en route +5 min · last fix heading to — +4 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 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=3
  • 50% T n=2
  • 100% F n=3
  • 100% S n=4
  • 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
18:37on time on time
18:42≈ on time ≈ on time
18:47 / 18:48≈ on time ≈ on time
18:53≈ on time ≈ +1 min
18:57≈ on time ≈ +1 min
19:00≈ on time ≈ +1 min
19:03≈ on time ≈ +1 min
19:06 / 19:11≈ on time ≈ +1 min
19:16≈ on time ≈ +2 min
19:20≈ on time ≈ +2 min
19:25≈ on time ≈ +2 min
19:28on time +2 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
Sat 7 NovNijmegen Lent 19:39Partial coverage0 min—
Fri 6 NovBrummen 19:290 min—
Thu 5 Nov— 19:29No data—
Wed 4 Nov— 19:290 min—
Mon 2 Nov— 19:220 min—
Sun 1 NovNijmegen Lent 19:390 min—
Sat 31 OctNijmegen Lent 19:400 min—
Fri 30 OctRheden 19:31No data—
Thu 29 Oct— 19:310 min—
Tue 27 Oct— 19:38No data—
Mon 26 Oct— 19:31No data—
Sun 25 OctNijmegen Lent 19:39No data—
Sat 24 OctNijmegen Lent 19:41No data—
Fri 23 OctNijmegen Lent 19:40+1 min+1 min
Thu 22 OctBrummen 19:32No data—
Wed 21 OctZutphen 19:320 min—
Tue 20 OctBrummen 19:300 min—
Mon 19 OctZutphen 19:29Partial coverage0 min—
Sun 18 OctNijmegen Lent 19:40+1 min+1 min
Sat 17 OctNijmegen Lent 19:39Partial coverage0 min—
Fri 16 OctNijmegen Lent 19:39No data—
Thu 15 Oct— 19:30No data—
Wed 14 OctNijmegen Lent 19:39No data—
Tue 13 OctZutphen 19:30No data—
Mon 12 OctBrummen 19:10Partial coverage0 min—
Sun 11 OctNijmegen Lent 19:40+1 min+3 min
Sat 10 OctNijmegen Lent 19:40Partial coverage0 min—
Fri 9 Oct— 19:29+2 min+2 min
Thu 8 Oct— 19:38+4 min+5 min
Wed 7 Oct— 19:290 min—