Train NS 7639 Wijchen – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Brummen at 13:04 No data

  1. Wijchen11:48
  2. Nijmegen Goffert11:55
  3. Elst12:10
  4. Arnhem Centraal12:19
  5. Arnhem Presikhaaf12:31
  6. Brummen12:48
  7. Zutphen12:54

Next service: tomorrow 11:48 from Wijchen · Fri 6 Nov

Full trip card
Next departure 11:48 tomorrow · Wijchen
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 7 full · 9 partial · 14 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 partial · 69 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: +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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • 100% F n=1
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

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