Train NS 7637 Wijchen – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Brummen at 12:40 +7 min

  1. Wijchen11:18
  2. Nijmegen Goffert11:25
  3. Elst11:40
  4. Arnhem Centraal11:49
  5. Arnhem Presikhaaf12:01
  6. Brummen12:18
  7. Zutphen12:24

Next service: tomorrow 11:18 from Wijchen · Tue 17 Nov

Next departure 11:18 tomorrow · Wijchen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 9 full · 12 partial · 9 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 10 full · 20 partial · 59 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

Worst days

  • Sat 7 Nov Max en route +11 min · last fix heading to Brummen +11 min
  • Mon 16 Nov Max en route +7 min · last fix heading to Brummen +7 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 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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