Train NS 7665 Wijchen – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Arnhem Zuid at 19:24 0 min

  1. Wijchen18:18
  2. Nijmegen Goffert18:25
  3. Elst18:40
  4. Arnhem Zuid18:44
  5. Arnhem Centraal18:49
  6. Arnhem Presikhaaf19:01
  7. Zutphen19:24

Next service: tomorrow 18:18 from Wijchen · Sat 7 Nov

Next departure 18:18 tomorrow · Wijchen
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 11 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 13 full · 8 partial · 49 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: 0 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

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=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 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 10
18:18on time on time
18:22≈ on time ≈ on time
18:25≈ on time ≈ on time
18:29 / 18:32≈ on time ≈ on time
18:35≈ on time ≈ on time
18:40≈ on time ≈ on time
18:44≈ on time ≈ on time
18:49 / 18:55≈ on time ≈ on time
18:57≈ on time ≈ on time
19:01≈ on time ≈ on time
19:04≈ on time ≈ on time
19:08≈ on time ≈ on time
19:13 / 19:14≈ on time ≈ on time
19:18≈ on time ≈ on time
19:24on 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
Fri 6 NovArnhem Zuid 19:24Partial coverage0 min—
Thu 5 Nov— 19:44No data—
Wed 4 Nov— 19:24No data—
Mon 2 NovNijmegen Lent 19:28Partial coverage0 min—
Sun 1 NovArnhem Zuid 18:590 min—
Sat 31 OctBrummen 19:35Partial coverage0 min—
Fri 30 OctArnhem Zuid 19:25No data—
Thu 29 Oct— 19:260 min—
Wed 28 Oct— 19:250 min—
Tue 27 Oct— 19:00No data—
Mon 26 Oct— 19:25No data—
Sun 25 OctArnhem Zuid 19:01No data—
Sat 24 OctBrummen 19:370 min—
Fri 23 OctBrummen 19:32+1 min—
Thu 22 OctArnhem Zuid 19:30No data—
Wed 21 OctElst 19:260 min—
Tue 20 OctArnhem Zuid 19:250 min—
Mon 19 OctElst 19:26Partial coverage0 min—
Sun 18 OctArnhem Zuid 19:000 min—
Sat 17 OctBrummen 19:41Partial coverage0 min—
Fri 16 OctBrummen 19:32No data—
Thu 15 OctNijmegen Goffert 19:27No data—
Wed 14 OctBrummen 19:32No data—
Tue 13 OctElst 19:26No data—
Mon 12 OctArnhem Zuid 19:26Partial coverage0 min—
Sun 11 OctArnhem Zuid 19:000 min—
Sat 10 OctBrummen 19:35Partial coverage0 min—
Fri 9 OctNijmegen Lent 19:25Partial coverage0 min—
Thu 8 Oct— 19:250 min—
Wed 7 Oct— 19:250 min—