Train NS 7630 Zutphen – Nijmegen

Zutphen 09:07 → Nijmegen 09:58 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Nijmegen Lent at 10:09 +1 min

  1. Zutphen09:07
  2. Dieren09:17
  3. Velp09:28
  4. Arnhem Velperpoort09:34
  5. Arnhem Centraal09:37
  6. Nijmegen Lent09:55
  7. Nijmegen09:58

Next service: tomorrow 09:07 from Zutphen · Mon 16 Nov

Next departure 09:07 tomorrow · Zutphen
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 30 full · 1 partial · 56 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: +2 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

  • Tue 10 Nov Max en route +6 min · last fix heading to Nijmegen Dukenburg +6 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Nijmegen Dukenburg +4 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Nijmegen Dukenburg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
09:07on time on time
09:12≈ on time ≈ on time
09:17 / 09:19≈ on time ≈ on time
09:24≈ on time ≈ +1 min
09:28≈ on time ≈ +1 min
09:31≈ on time ≈ +1 min
09:34 / 09:35≈ on time ≈ +1 min
09:37 / 09:41≈ on time ≈ +1 min
09:46≈ on time ≈ +1 min
09:50≈ on time ≈ +2 min
09:55≈ on time ≈ +2 min
09:58on 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 NovNijmegen Lent 10:09Partial coverage+1 min+1 min
Sat 14 NovNijmegen Dukenburg 10:190 min—
Fri 13 NovNijmegen Dukenburg 10:23+1 min+1 min
Thu 12 NovNijmegen Dukenburg 10:23+2 min+2 min
Wed 11 NovNijmegen Dukenburg 10:190 min—
Tue 10 NovNijmegen Dukenburg 10:28+6 min+6 min
Mon 9 NovNijmegen Dukenburg 10:190 min—
Sun 8 NovNijmegen Lent 10:090 min—
Sat 7 NovNijmegen Dukenburg 10:190 min—
Fri 6 NovNijmegen Dukenburg 10:24No data—
Thu 5 NovNijmegen Dukenburg 10:19No data—
Wed 4 NovNijmegen Dukenburg 10:24+3 min+3 min
Tue 3 NovNijmegen Dukenburg 10:220 min—
Mon 2 NovNijmegen Dukenburg 10:220 min—
Sun 1 NovNijmegen Lent 10:09+1 min—
Sat 31 OctNijmegen Dukenburg 10:210 min—
Fri 30 OctNijmegen Dukenburg 10:300 min—
Thu 29 OctNijmegen Dukenburg 10:210 min—
Wed 28 OctNijmegen Dukenburg 10:220 min—
Tue 27 OctNijmegen Dukenburg 10:210 min—
Mon 26 OctNijmegen Dukenburg 10:230 min—
Sun 25 OctNijmegen Lent 10:09No data—
Sat 24 OctNijmegen Dukenburg 10:27+2 min+9 min
Fri 23 OctNijmegen Dukenburg 10:21No data—
Thu 22 OctNijmegen Dukenburg 10:25No data—
Wed 21 OctNijmegen Dukenburg 10:21No data—
Tue 20 OctNijmegen Dukenburg 10:21No data—
Mon 19 OctNijmegen Dukenburg 10:250 min—
Sun 18 OctNijmegen Lent 10:100 min—
Sat 17 OctNijmegen Dukenburg 10:210 min—