Train NS 7642 Zutphen – Nijmegen

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

✓ Today’s run finished

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

  1. Zutphen12:07
  2. Dieren12:17
  3. Velp12:27
  4. Arnhem Velperpoort12:33
  5. Arnhem Centraal12:36
  6. Nijmegen Lent12:55
  7. Nijmegen12:58

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

Next departure 12:07 tomorrow · Zutphen
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 19 full · 3 partial · 8 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 26 full · 3 partial · 58 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

  • Tue 10 Nov Max en route +6 min · last fix heading to Nijmegen Dukenburg +6 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 100% W n=5
  • 100% T n=2
  • 100% F n=3
  • 100% 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, 29 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
12:07on time on time
12:12≈ on time ≈ on time
12:17 / 12:18≈ on time ≈ on time
12:23≈ on time ≈ on time
12:27≈ on time ≈ on time
12:30≈ on time ≈ on time
12:33≈ on time ≈ +1 min
12:36 / 12:41≈ on time ≈ +1 min
12:46≈ on time ≈ +1 min
12:50≈ on time ≈ +1 min
12:55≈ on time ≈ +1 min
12:58on 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
Sun 15 NovNijmegen Lent 13:09Partial coverage+1 min+1 min
Sat 14 NovNijmegen Dukenburg 13:190 min—
Fri 13 NovNijmegen Dukenburg 13:190 min—
Thu 12 NovNijmegen Dukenburg 13:23+2 min+2 min
Wed 11 NovNijmegen Dukenburg 13:190 min—
Tue 10 NovNijmegen Dukenburg 13:28+6 min+6 min
Mon 9 NovNijmegen Dukenburg 13:190 min—
Sun 8 NovNijmegen Lent 13:09Partial coverage0 min—
Sat 7 NovNijmegen Dukenburg 13:190 min—
Fri 6 NovNijmegen Dukenburg 13:19No data—
Thu 5 NovNijmegen Dukenburg 13:19No data—
Wed 4 NovNijmegen Dukenburg 13:190 min—
Tue 3 NovNijmegen Dukenburg 13:19No data—
Mon 2 NovNijmegen Dukenburg 13:220 min—
Sun 1 NovNijmegen Lent 13:10Partial coverage0 min—
Sat 31 OctNijmegen Dukenburg 13:210 min—
Fri 30 OctNijmegen Dukenburg 13:210 min—
Thu 29 OctNijmegen Dukenburg 13:21No data—
Wed 28 OctNijmegen Dukenburg 13:220 min—
Tue 27 OctNijmegen Dukenburg 13:210 min—
Mon 26 OctNijmegen Dukenburg 13:21No data—
Sun 25 OctNijmegen Lent 13:15No data—
Sat 24 OctNijmegen Dukenburg 13:210 min—
Fri 23 OctNijmegen Dukenburg 13:21No data—
Thu 22 OctNijmegen Dukenburg 13:22No data—
Wed 21 OctNijmegen Dukenburg 13:210 min—
Tue 20 OctNijmegen Dukenburg 13:210 min—
Mon 19 OctNijmegen Dukenburg 13:210 min—
Sun 18 OctNijmegen Lent 13:100 min—
Sat 17 OctNijmegen Dukenburg 13:210 min—