Train NS 7647 Wijchen – Zutphen

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

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

Next service: today 13:48 from Wijchen · Thu 19 Nov

Next departure 13:48 today · Wijchen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 6 full · 12 partial · 11 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 9 full · 21 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 100% W n=6
  • 100% T n=2
  • 50% F n=2
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

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