Train NS 7655 Wijchen – Zutphen

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

Running now · updated 16:02

Position estimated from the timetable

Heading to Zutphen 0 min

Estimated arrival at Zutphen 16:54 · 28 km/h

  1. Wijchen15:48
  2. Nijmegen Goffert15:55
  3. Elst16:10
  4. Arnhem Centraal16:19
  5. Arnhem Presikhaaf16:31
  6. Dieren16:43
  7. Zutphen16:54

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 21 runs arrived on time.

On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 9 full · 12 partial · 9 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 10 full · 19 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Fri 13 Nov Max en route +5 min · last fix heading to Brummen +5 min

Distribution · 90 days

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

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

On-time by weekday

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