Train NS 7679 Nijmegen – Zutphen

Nijmegen 22:03 → Zutphen 22:54 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 22:03 from Nijmegen · Wed 18 Nov

Next departure 22:03 today · Nijmegen
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 13 full · 5 partial · 8 no data
On-time · 90 days
87%
27/31 runs under 3 min
RT coverage: 22 full · 9 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Zutphen, 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 +20 min · last fix heading to — +20 min
  • Fri 16 Oct Max en route +7 min · last fix heading to — +7 min
  • Tue 10 Nov Max en route +5 min · last fix heading to — +5 min
  • Fri 13 Nov Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 27
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
22:03on time on time
22:06≈ on time ≈ on time
22:11≈ on time ≈ +1 min
22:15≈ on time ≈ +2 min
22:20 / 22:25≈ on time ≈ +2 min
22:27≈ on time ≈ +3 min
22:31≈ on time ≈ +4 min
22:34≈ on time ≈ +4 min
22:38≈ on time ≈ +4 min
22:43 / 22:44≈ on time ≈ +4 min
22:48≈ on time ≈ +5 min
22:54on time +5 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
Tue 17 Nov— 22:380 min—
Sun 15 NovBrummen 23:04Partial coverage+3 min+3 min
Sat 14 NovBrummen 23:02Partial coverage+2 min+2 min
Fri 13 Nov— 23:04+5 min+5 min
Thu 12 Nov— 22:54+2 min+2 min
Wed 11 Nov— 22:540 min—
Tue 10 Nov— 23:04+5 min+5 min
Mon 9 Nov— 22:540 min—
Sun 8 NovBrummen 23:04Partial coverage+2 min+2 min
Sat 7 NovBrummen 23:02Partial coverage+2 min+2 min
Fri 6 Nov— 22:540 min—
Thu 5 Nov— 22:54No data—
Wed 4 Nov— 22:540 min—
Mon 2 Nov— 22:54+1 min—
Sun 1 NovBrummen 23:04Partial coverage0 min—
Sat 31 OctBrummen 23:020 min—
Fri 30 Oct— 22:550 min—
Thu 29 Oct— 22:550 min—
Tue 27 Oct— 22:55No data—
Mon 26 Oct— 22:55No data—
Sun 25 OctBrummen 23:07No data—
Sat 24 OctRheden 22:55No data—
Fri 23 Oct— 23:25+20 min+20 min
Thu 22 Oct— 22:56No data—
Wed 21 Oct— 22:55No data—
Tue 20 Oct— 23:40No data—
Mon 19 Oct— 22:080 min—
Sun 18 OctBrummen 23:05Partial coverage+1 min+1 min
Sat 17 OctBrummen 23:04Partial coverage0 min—
Fri 16 Oct— 23:04+7 min+7 min