Train NS 7651 Wijchen – Zutphen

Wijchen 14:48 → Zutphen 15:54 Daily 1 h 06 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Brummen at 16:09 +2 min

  1. Wijchen14:48
  2. Nijmegen Goffert14:55
  3. Elst15:10
  4. Arnhem Centraal15:19
  5. Arnhem Presikhaaf15:31
  6. Brummen15:48
  7. Zutphen15:54

Next service: tomorrow 14:48 from Wijchen · Tue 17 Nov

Next departure 14:48 tomorrow · Wijchen
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 9 full · 9 partial · 12 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 10 full · 17 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Zutphen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 12 Nov Max en route +12 min · last fix heading to Brummen +12 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Brummen +4 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Brummen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 24
  • 3–10 min 7% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
14:48on time on time
14:52≈ on time ≈ on time
14:55≈ on time ≈ on time
14:59 / 15:02≈ on time ≈ on time
15:05≈ on time ≈ +1 min
15:10≈ on time ≈ +1 min
15:14≈ on time ≈ +1 min
15:19 / 15:25≈ on time ≈ +1 min
15:27≈ on time ≈ +2 min
15:31≈ on time ≈ +2 min
15:34≈ on time ≈ +2 min
15:38≈ on time ≈ +2 min
15:43 / 15:44≈ on time ≈ +2 min
15:48≈ on time ≈ +3 min
15:54on time +3 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
Mon 16 NovBrummen 16:09Partial coverage+2 min+2 min
Sun 15 NovBrummen 16:040 min—
Sat 14 NovBrummen 16:04Partial coverage0 min—
Fri 13 NovBrummen 16:04Partial coverage+3 min+3 min
Thu 12 NovBrummen 16:14Partial coverage+12 min+12 min
Wed 11 NovBrummen 16:04+3 min+3 min
Tue 10 NovBrummen 16:04Partial coverage+1 min+1 min
Mon 9 NovBrummen 16:04Partial coverage0 min—
Sun 8 NovBrummen 16:040 min—
Sat 7 NovBrummen 16:04No data—
Fri 6 NovBrummen 16:04No data—
Thu 5 NovBrummen 16:05No data—
Wed 4 NovBrummen 16:04Partial coverage+2 min+2 min
Tue 3 NovBrummen 16:04No data—
Mon 2 NovBrummen 16:04No data—
Sun 1 NovBrummen 16:07+4 min+4 min
Sat 31 OctBrummen 16:04Partial coverage0 min+1 min
Fri 30 OctBrummen 16:04No data—
Thu 29 OctBrummen 16:04No data—
Wed 28 OctBrummen 16:04No data—
Tue 27 OctBrummen 16:08No data—
Mon 26 OctBrummen 16:04No data—
Sun 25 OctBrummen 16:05No data—
Sat 24 OctBrummen 16:040 min—
Fri 23 OctBrummen 16:100 min—
Thu 22 OctBrummen 16:05No data—
Wed 21 OctBrummen 16:050 min—
Tue 20 OctBrummen 16:050 min—
Mon 19 OctBrummen 16:05Partial coverage0 min—
Sun 18 OctBrummen 16:040 min—