Train NS 7669 Nijmegen – Zutphen

Nijmegen 19:33 → Zutphen 20:24 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 19:33 from Nijmegen · Wed 18 Nov

Next departure 19:33 today · Nijmegen
On-time · 30 days
74%
14/19 runs under 3 min
RT coverage: 15 full · 4 partial · 9 no data
On-time · 90 days
71%
20/28 runs under 3 min
RT coverage: 23 full · 5 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 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

  • Sun 8 Nov Max en route +13 min · last fix heading to Arnhem Zuid +13 min
  • Tue 6 Oct Max en route +12 min · last fix heading to — +12 min
  • Wed 4 Nov Max en route +11 min · last fix heading to — +11 min
  • Sun 15 Nov Max en route +8 min · last fix heading to Arnhem Zuid +7 min
  • Sat 31 Oct Max en route +6 min · last fix heading to Brummen +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 20
  • 3–10 min 18% · 5
  • 10–30 min 11% · 3
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
19:33on time on time
19:36≈ on time ≈ +1 min
19:41≈ on time ≈ +2 min
19:45≈ on time ≈ +3 min
19:50 / 19:55≈ on time ≈ +4 min
19:57≈ +1 min ≈ +5 min
20:01≈ +1 min ≈ +6 min
20:04≈ +1 min ≈ +6 min
20:08≈ +1 min ≈ +7 min
20:13 / 20:14≈ +1 min ≈ +8 min
20:18≈ +1 min ≈ +9 min
20:24on time +10 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— 20:090 min—
Mon 16 Nov— 20:240 min—
Sun 15 NovArnhem Zuid 20:08+7 min+8 min
Sat 14 NovBrummen 20:34Partial coverage+1 min—
Fri 13 Nov— 20:24+2 min+2 min
Thu 12 Nov— 20:24+2 min+2 min
Wed 11 Nov— 20:240 min—
Tue 10 Nov— 20:34+4 min+4 min
Mon 9 Nov— 20:240 min—
Sun 8 NovArnhem Zuid 20:13+13 min+13 min
Sat 7 NovBrummen 20:34Partial coverage0 min—
Fri 6 Nov— 20:27+1 min+2 min
Thu 5 Nov— 20:25No data—
Wed 4 Nov— 20:34+11 min+11 min
Tue 3 Nov— 20:240 min—
Mon 2 Nov— 20:39No data—
Sun 1 NovArnhem Zuid 19:59+1 min+1 min
Sat 31 OctBrummen 20:41Partial coverage+6 min+6 min
Thu 29 Oct— 20:250 min—
Wed 28 Oct— 20:25No data—
Tue 27 Oct— 20:26No data—
Mon 26 OctArnhem Zuid 20:26Partial coverage0 min—
Sun 25 OctArnhem Zuid 20:02No data—
Sat 24 OctBrummen 20:38No data—
Fri 23 Oct— 20:280 min+28 min
Thu 22 Oct— 20:26No data—
Wed 21 Oct— 20:25No data—
Tue 20 Oct— 20:08No data—
Mon 19 Oct— 19:520 min—
Sun 18 OctArnhem Zuid 20:04+4 min+4 min