Train NS 7621 Nijmegen – Zutphen

Nijmegen 07:33 → Zutphen 08:24 Mon, Tue, Wed, Thu, Fri, Sat 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 07:33 from Nijmegen · Mon 9 Nov

Next departure 07:33 tomorrow · Nijmegen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 11 full · 5 partial · 9 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 15 full · 5 partial · 57 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 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

  • Tue 3 Nov Max en route +4 min · last fix heading to Brummen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 67% T n=3
  • 100% W n=4
  • 100% T n=2
  • 100% F n=3
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
07:33on time on time
07:36≈ on time ≈ on time
07:41≈ on time ≈ on time
07:45≈ on time ≈ +1 min
07:50 / 07:55≈ on time ≈ +1 min
07:57≈ on time ≈ +1 min
08:01≈ on time ≈ +1 min
08:04≈ on time ≈ +2 min
08:08≈ on time ≈ +2 min
08:13 / 08:14≈ on time ≈ +2 min
08:18≈ on time ≈ +2 min
08:24on 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
Sat 7 NovBrummen 08:34Partial coverage0 min—
Fri 6 NovBrummen 08:38No data—
Thu 5 NovBrummen 08:34No data—
Wed 4 NovBrummen 08:340 min—
Tue 3 NovBrummen 08:37+4 min+4 min
Mon 2 NovBrummen 08:34No data—
Sat 31 OctBrummen 08:34Partial coverage0 min—
Fri 30 OctBrummen 08:350 min—
Thu 29 OctBrummen 08:390 min+3 min
Wed 28 OctBrummen 08:34No data—
Tue 27 OctBrummen 08:34No data—
Mon 26 OctBrummen 08:350 min—
Sat 24 OctBrummen 08:34Partial coverage+1 min—
Fri 23 OctBrummen 08:350 min—
Thu 22 OctBrummen 08:34No data—
Wed 21 OctBrummen 08:340 min—
Tue 20 OctBrummen 08:340 min—
Mon 19 OctBrummen 08:340 min—
Sat 17 OctBrummen 08:35Partial coverage+1 min—
Fri 16 OctBrummen 08:34No data—
Thu 15 OctBrummen 08:35No data—
Wed 14 OctBrummen 08:350 min—
Tue 13 OctBrummen 08:37No data—
Mon 12 OctBrummen 08:380 min—
Sat 10 OctBrummen 08:34Partial coverage+1 min—
Fri 9 OctBrummen 08:36+3 min+3 min
Thu 8 OctBrummen 08:360 min—
Wed 7 OctBrummen 08:340 min—
Tue 6 OctBrummen 08:36+2 min+2 min
Mon 5 OctBrummen 08:35No data—