Train NS 7656 Zutphen → Wijchen

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

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 15:37 from Zutphen · Sat 21 Nov

Next departure 15:37 today · Zutphen
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 4 full · 15 partial · 10 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 9 full · 23 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 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

  • Tue 6 Oct Max en route +7 min · last fix heading to Nijmegen Dukenburg +7 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 100% W n=6
  • 100% T n=4
  • 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, 32 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
15:37on time on time
15:42≈ on time ≈ on time
15:47 / 15:48≈ on time ≈ on time
15:53≈ on time ≈ on time
15:57≈ on time ≈ on time
16:00≈ on time ≈ +1 min
16:03≈ on time ≈ +1 min
16:06 / 16:11≈ on time ≈ +1 min
16:16≈ on time ≈ +1 min
16:20≈ on time ≈ +1 min
16:25≈ on time ≈ +1 min
16:29 / 16:30≈ on time ≈ +1 min
16:34≈ on time ≈ +1 min
16:37≈ on time ≈ +1 min
16:41on 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
Fri 20 NovNijmegen Dukenburg 16:52Partial coverage0 min—
Thu 19 NovNijmegen Dukenburg 16:50Partial coverage0 min—
Wed 18 NovNijmegen Dukenburg 16:52Partial coverage+1 min+1 min
Tue 17 NovNijmegen Dukenburg 16:54Partial coverage0 min—
Mon 16 NovNijmegen Dukenburg 16:54Partial coverage+2 min+2 min
Sun 15 NovNijmegen Lent 16:390 min—
Sat 14 NovNijmegen Dukenburg 16:52Partial coverage0 min—
Fri 13 NovNijmegen Dukenburg 16:53Partial coverage+3 min+3 min
Thu 12 NovNijmegen Dukenburg 16:52Partial coverage0 min—
Wed 11 NovNijmegen Dukenburg 16:49Partial coverage0 min—
Tue 10 NovNijmegen Dukenburg 16:49Partial coverage0 min—
Mon 9 NovNijmegen Dukenburg 16:52Partial coverage0 min—
Sun 8 NovNijmegen Lent 16:400 min—
Sat 7 NovNijmegen Dukenburg 16:52Partial coverage0 min—
Fri 6 NovNijmegen Dukenburg 16:58No data—
Thu 5 NovNijmegen Dukenburg 16:52No data—
Wed 4 NovNijmegen Dukenburg 16:54Partial coverage+1 min+2 min
Tue 3 NovNijmegen Dukenburg 16:49No data—
Mon 2 NovNijmegen Dukenburg 16:54No data—
Sun 1 NovNijmegen Lent 16:40+2 min+2 min
Sat 31 OctNijmegen Dukenburg 16:51Partial coverage0 min—
Fri 30 OctNijmegen Dukenburg 16:51No data—
Thu 29 OctNijmegen 17:01No data—
Wed 28 OctNijmegen Dukenburg 16:48Partial coverage0 min—
Tue 27 OctNijmegen Dukenburg 16:51No data—
Mon 26 OctNijmegen Dukenburg 16:51No data—
Sun 25 OctNijmegen Lent 16:39No data—
Sat 24 OctNijmegen Dukenburg 16:520 min—
Fri 23 OctNijmegen Dukenburg 16:54No data—
Thu 22 OctNijmegen Dukenburg 16:540 min—