Train NS 7632 Zutphen – Wijchen

Zutphen 09:37 → Wijchen 10:41 Daily 1 h 04 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November +3 min

Next service: today 09:37 from Zutphen · Fri 20 Nov

Next departure 09:37 today · Zutphen
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 5 full · 15 partial · 9 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 10 full · 21 partial · 57 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

  • Wed 11 Nov Max en route +4 min · last fix heading to Nijmegen Dukenburg +4 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 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 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:37on time on time
09:42≈ on time ≈ on time
09:47 / 09:48≈ on time ≈ on time
09:53≈ on time ≈ on time
09:57≈ on time ≈ on time
10:00≈ on time ≈ on time
10:03≈ on time ≈ on time
10:06 / 10:10≈ on time ≈ on time
10:15≈ on time ≈ on time
10:19≈ on time ≈ on time
10:24≈ on time ≈ on time
10:27 / 10:30≈ on time ≈ on time
10:34≈ on time ≈ on time
10:37≈ on time ≈ on time
10:41on time on time

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
Thu 19 NovNijmegen Dukenburg 10:53Partial coverage+3 min+5 min
Wed 18 NovNijmegen Dukenburg 10:50Partial coverage0 min—
Tue 17 NovNijmegen Dukenburg 10:53Partial coverage+2 min+2 min
Mon 16 NovNijmegen Dukenburg 10:52Partial coverage0 min—
Sun 15 NovNijmegen Lent 10:400 min—
Sat 14 NovNijmegen Dukenburg 10:49Partial coverage0 min—
Fri 13 NovNijmegen Dukenburg 10:49Partial coverage0 min—
Thu 12 NovNijmegen Dukenburg 10:52Partial coverage+1 min+1 min
Wed 11 NovNijmegen Dukenburg 10:54Partial coverage+4 min+4 min
Tue 10 NovNijmegen Dukenburg 11:04Partial coverage0 min+16 min
Mon 9 NovNijmegen Dukenburg 10:49Partial coverage0 min—
Sun 8 NovNijmegen Lent 10:39+2 min+2 min
Sat 7 NovNijmegen Dukenburg 10:49Partial coverage0 min—
Fri 6 NovNijmegen Dukenburg 10:49No data—
Thu 5 NovNijmegen Dukenburg 10:49No data—
Wed 4 NovNijmegen Dukenburg 10:49Partial coverage0 min—
Tue 3 NovNijmegen Dukenburg 10:54No data—
Mon 2 NovArnhem Zuid 11:430 min—
Sun 1 NovNijmegen Lent 10:400 min—
Sat 31 OctNijmegen Dukenburg 10:51No data—
Fri 30 OctNijmegen Dukenburg 10:55Partial coverage0 min—
Thu 29 OctNijmegen Dukenburg 10:51No data—
Wed 28 OctNijmegen Dukenburg 10:51Partial coverage0 min—
Tue 27 OctNijmegen Dukenburg 10:51Partial coverage0 min—
Mon 26 OctNijmegen Dukenburg 10:51No data—
Sun 25 OctNijmegen Lent 10:39No data—
Sat 24 OctNijmegen Dukenburg 10:520 min—
Fri 23 OctNijmegen Dukenburg 10:53No data—
Thu 22 OctNijmegen Dukenburg 10:54No data—
Wed 21 OctNijmegen Dukenburg 10:530 min—