Train NS 7631 Nijmegen – Zutphen

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

It has not run yet today

Last recorded run: Sunday 15 November +11 min

Next service: today 10:03 from Nijmegen · Mon 16 Nov

Next departure 10:03 today · Nijmegen
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 15 full · 4 partial · 10 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 22 full · 5 partial · 59 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: +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

  • Tue 10 Nov Max en route +12 min · last fix heading to Brummen +12 min
  • Sun 15 Nov Max en route +11 min · last fix heading to Brummen +11 min
  • Sat 14 Nov Max en route +4 min · last fix heading to Brummen +4 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Brummen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 7% · 2
  • 10–30 min 7% · 2
  • 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=4
  • 83% S n=6
  • 60% S n=5

Stops and timetable

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

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