Train NS 7662 Zutphen – Wijchen

Zutphen 17:07 → Wijchen 18:11 Daily 1 h 04 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Nijmegen Dukenburg at 18:24 +3 min

  1. Zutphen17:07
  2. Dieren17:17
  3. Arnhem Presikhaaf17:31
  4. Arnhem Centraal17:37
  5. Elst17:50
  6. Nijmegen Dukenburg18:07
  7. Wijchen18:11

Next service: tomorrow 17:07 from Zutphen · Sun 8 Nov

Next departure 17:07 tomorrow · Zutphen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 11 full · 7 partial · 12 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 12 full · 10 partial · 65 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 Wijchen, 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 24 Oct Max en route +5 min · last fix heading to Nijmegen Dukenburg +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 100% F n=4
  • 80% S n=5
  • 100% S n=3

Stops and timetable

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

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