Train NS 7639 Nijmegen → Zutphen

Nijmegen 12:03 → Zutphen 12:54 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

NS 7639 Nijmegen–Zutphen: final delay under 3 min on 20 of its 23 runs with data in the last 30 days (87%). Median final delay: 0 min. Running now, on time. Expected at Zutphen: 12:54. TrainsRadar data as of 22 Nov 2026, 12:16 (GMT+1).

Running now · updated 12:16

Heading to Zutphen 0 min

Estimated arrival at Zutphen 12:54 · 21 km/h

  1. Nijmegen12:03
  2. Elst12:11
  3. Arnhem Centraal12:20
  4. Arnhem Presikhaaf12:31
  5. Velp12:34
  6. Dieren12:43
  7. Zutphen12:54

Today it is running no worse than usual: typical arrival delay is 0 min; 87% of the last 23 runs arrived on time.

On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 19 full · 4 partial · 7 no data
On-time · 90 days
91%
31/34 runs under 3 min
RT coverage: 28 full · 6 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sun 15 Nov Max en route +9 min · last fix heading to Brummen +7 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Brummen +5 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Brummen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 31
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 83% W n=6
  • 100% T n=4
  • 100% F n=3
  • 100% S n=6
  • 83% S n=6

Stops and timetable

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

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