Train NS 7626 Zutphen – Wijchen

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

Running now · updated 07:59

Heading to Wijchen No data

Estimated arrival at Wijchen 09:11

  1. Zutphen08:07
  2. Dieren08:17
  3. Arnhem Presikhaaf08:30
  4. Arnhem Centraal08:36
  5. Elst08:50
  6. Nijmegen Goffert09:04
  7. Wijchen09:11
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 6 full · 14 partial · 10 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 6 full · 15 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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