Train NS 7672 Zutphen – Nijmegen

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

Running now · updated 20:28

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 20:28 · 13 km/h

  1. Zutphen19:37
  2. Dieren19:47
  3. Velp19:57
  4. Arnhem Velperpoort20:03
  5. Arnhem Centraal20:06
  6. Elst20:20
  7. Nijmegen20:28

Today it is running no worse than usual: typical arrival delay is 0 min; 86% of the last 22 runs arrived on time.

On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 18 full · 4 partial · 7 no data
On-time · 90 days
84%
27/32 runs under 3 min
RT coverage: 27 full · 5 partial · 27 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: +4 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 13 Nov Max en route +11 min · last fix heading to — +10 min
  • Wed 4 Nov Max en route +6 min · last fix heading to — +6 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Nijmegen Lent +4 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Nijmegen Lent +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 27
  • 3–10 min 16% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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 10Today
19:37on time on time
19:42≈ on time ≈ on time
19:47 / 19:48≈ on time ≈ +1 min
19:53≈ on time ≈ +2 min
19:57≈ on time ≈ +2 min
20:00≈ on time ≈ +2 min
20:03≈ on time ≈ +2 min
20:06 / 20:11≈ on time ≈ +3 min
20:16≈ on time ≈ +4 min
20:20≈ on time ≈ +4 min
20:25≈ on time ≈ +5 min
20:28on 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
Wed 18 Nov— 20:240 min—
Tue 17 Nov— 19:480 min—
Mon 16 Nov— 20:34+2 min+2 min
Sun 15 NovNijmegen Lent 20:39+2 min+2 min
Sat 14 NovNijmegen Lent 20:39Partial coverage0 min—
Fri 13 Nov— 20:48+10 min+11 min
Thu 12 Nov— 20:29+2 min+3 min
Wed 11 Nov— 20:290 min—
Tue 10 Nov— 20:29+1 min+1 min
Mon 9 Nov— 20:290 min—
Sun 8 NovNijmegen Lent 20:390 min—
Sat 7 NovNijmegen Lent 20:39Partial coverage0 min—
Fri 6 Nov— 20:300 min—
Thu 5 Nov— 20:38No data—
Wed 4 Nov— 20:39+6 min+6 min
Mon 2 Nov— 20:29No data—
Sun 1 NovNijmegen Lent 20:39+4 min+4 min
Sat 31 OctNijmegen Lent 20:39Partial coverage0 min—
Fri 30 Oct— 20:290 min—
Thu 29 Oct— 20:290 min—
Wed 28 Oct— 20:29No data—
Tue 27 Oct— 20:30No data—
Mon 26 OctArnhem Centraal 20:33Partial coverage0 min—
Sun 25 OctNijmegen Lent 20:39No data—
Sat 24 OctNijmegen Lent 20:420 min—
Fri 23 Oct— 20:32+1 min—
Thu 22 Oct— 20:32No data—
Wed 21 Oct— 20:32No data—
Tue 20 Oct— 20:380 min—
Mon 19 Oct— 20:360 min—