Train NS 7640 Zutphen – Wijchen

Zutphen 11:37 → Wijchen 12:41 Daily 1 h 04 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Nijmegen Dukenburg at 12:49 No data

  1. Zutphen11:37
  2. Dieren11:47
  3. Arnhem Presikhaaf12:00
  4. Arnhem Centraal12:06
  5. Elst12:20
  6. Nijmegen Dukenburg12:37
  7. Wijchen12:41

Next service: tomorrow 11:37 from Zutphen · Sat 7 Nov

Next departure 11:37 tomorrow · Zutphen
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 4 full · 14 partial · 12 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 4 full · 17 partial · 68 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 Wijchen, 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=4
  • 100% T n=2
  • 100% F n=2
  • 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
11:37on time on time
11:42— —
11:47 / 11:48— —
11:53— —
11:57— —
12:00— —
12:03— —
12:06 / 12:11— —
12:16— —
12:20— —
12:25— —
12:29 / 12:30— —
12:34— —
12:37— —
12:41— —

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 NovNijmegen Dukenburg 12:49No data—
Thu 5 NovNijmegen Dukenburg 12:49No data—
Wed 4 NovNijmegen Dukenburg 12:49Partial coverage0 min—
Tue 3 NovNijmegen Dukenburg 12:49No data—
Mon 2 NovNijmegen Dukenburg 12:49No data—
Sun 1 NovNijmegen Lent 12:41+1 min+1 min
Sat 31 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Fri 30 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Thu 29 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Wed 28 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Tue 27 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Mon 26 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Sun 25 OctNijmegen Lent 12:39No data—
Sat 24 OctNijmegen Dukenburg 12:530 min—
Fri 23 OctNijmegen Dukenburg 12:52No data—
Thu 22 OctNijmegen Dukenburg 12:52No data—
Wed 21 OctNijmegen Dukenburg 12:52No data—
Tue 20 OctNijmegen Dukenburg 12:53No data—
Mon 19 OctNijmegen Dukenburg 12:52Partial coverage0 min—
Sun 18 OctArnhem Centraal 12:400 min—
Sat 17 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Fri 16 OctNijmegen Dukenburg 12:56No data—
Thu 15 OctNijmegen Dukenburg 12:51No data—
Wed 14 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Tue 13 OctNijmegen Dukenburg 12:53No data—
Mon 12 OctNijmegen Dukenburg 12:52Partial coverage0 min—
Sun 11 OctNijmegen Lent 12:390 min—
Sat 10 OctNijmegen Dukenburg 12:51Partial coverage+1 min+1 min
Fri 9 OctNijmegen Dukenburg 12:51Partial coverage0 min—
Thu 8 OctNijmegen Dukenburg 12:51Partial coverage0 min—