Train NS 7625 Nijmegen – Zutphen

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

It has not run yet today

Last recorded run: Saturday 14 November +3 min

Next service: today 08:33 from Nijmegen · Mon 16 Nov

Next departure 08:33 today · Nijmegen
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 13 full · 4 partial · 7 no data
On-time · 90 days
74%
17/23 runs under 3 min
RT coverage: 17 full · 6 partial · 53 no data
Typical delay
+1min
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 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

  • Thu 8 Oct Max en route +30 min · last fix heading to Brummen +30 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Brummen +4 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Brummen +4 min
  • Sat 14 Nov Max en route +3 min · last fix heading to Brummen +3 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Brummen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 17
  • 3–10 min 22% · 5
  • 10–30 min 0% · 0
  • 30+ min 4% · 1

On-time by weekday

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

Stops and timetable

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

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