Train NS 7661 Wijchen – Zutphen

Wijchen 17:18 → Zutphen 18:24 Daily 1 h 06 min · 15 stops NS (Nederlandse Spoorwegen)

Running now · updated 18:11

Heading to Zutphen 0 min

Estimated arrival at Zutphen 18:24 · 130 km/h

  1. Wijchen17:18
  2. Nijmegen Goffert17:25
  3. Elst17:40
  4. Arnhem Centraal17:49
  5. Arnhem Presikhaaf18:01
  6. Dieren18:13
  7. Zutphen18:24

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

On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 8 full · 10 partial · 12 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 8 full · 13 partial · 68 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: +2 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 23 Oct Max en route +9 min · last fix heading to Brummen +9 min

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 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 75% F n=4
  • 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
17:18on time on time
17:22≈ on time ≈ on time
17:25≈ on time ≈ on time
17:29 / 17:32≈ on time ≈ +1 min
17:35≈ on time ≈ +1 min
17:40≈ on time ≈ +1 min
17:44≈ on time ≈ +1 min
17:49 / 17:55≈ on time ≈ +2 min
17:57≈ on time ≈ +2 min
18:01≈ on time ≈ +2 min
18:04≈ on time ≈ +2 min
18:08≈ on time ≈ +3 min
18:13 / 18:14≈ on time ≈ +3 min
18:18≈ on time ≈ +3 min
18:24on time +4 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 6 NovRheden 18:09Partial coverage0 min—
Thu 5 NovRheden 18:24No data—
Wed 4 NovDieren 18:28Partial coverage0 min—
Tue 3 NovRheden 18:24No data—
Mon 2 NovRheden 18:22No data—
Sun 1 NovArnhem Zuid 18:01+1 min+1 min
Sat 31 OctBrummen 18:34Partial coverage0 min—
Fri 30 OctBrummen 18:32Partial coverage0 min—
Thu 29 OctArnhem Presikhaaf 18:26No data—
Wed 28 OctRheden 18:25No data—
Tue 27 OctVelp 18:35No data—
Mon 26 OctRheden 18:28Partial coverage0 min—
Sun 25 OctArnhem Zuid 18:00No data—
Sat 24 OctBrummen 18:360 min—
Fri 23 OctBrummen 18:42+9 min+9 min
Thu 22 OctBrummen 18:32No data—
Wed 21 OctBrummen 18:320 min—
Tue 20 OctBrummen 18:320 min—
Mon 19 OctBrummen 18:32Partial coverage0 min—
Sun 18 OctArnhem Zuid 18:010 min—
Sat 17 OctBrummen 18:35Partial coverage0 min—
Fri 16 OctBrummen 18:30No data—
Thu 15 OctBrummen 18:32No data—
Wed 14 OctBrummen 18:32No data—
Tue 13 OctBrummen 18:32No data—
Mon 12 OctBrummen 18:32Partial coverage0 min—
Sun 11 OctArnhem Zuid 18:000 min—
Sat 10 OctBrummen 18:34Partial coverage0 min—
Fri 9 OctBrummen 18:32Partial coverage+3 min+3 min
Thu 8 OctArnhem Presikhaaf 18:260 min—