Train NS 7622 Zutphen – Nijmegen

Zutphen 07:07 → Nijmegen 07:59 Daily 0 h 52 min · 12 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Nijmegen Lent at 08:09 0 min

  1. Zutphen07:07
  2. Dieren07:17
  3. Velp07:28
  4. Arnhem Velperpoort07:34
  5. Arnhem Centraal07:37
  6. Nijmegen Lent07:55
  7. Nijmegen07:59

Next service: tomorrow 07:07 from Zutphen · Sun 15 Nov

Next departure 07:07 tomorrow · Zutphen
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 23 full · 4 partial · 3 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 32 full · 5 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 17 Oct Max en route +14 min · last fix heading to Nijmegen Lent +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 36
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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