Train NS 7690 Zutphen – Nijmegen

Zutphen 00:07 → Nijmegen 00:58 Daily 0 h 51 min · 12 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:04 +3 min

  1. Zutphen00:07
  2. Dieren00:17
  3. Velp00:27
  4. Arnhem Velperpoort00:33
  5. Arnhem Centraal00:36
  6. Elst00:50
  7. Nijmegen00:58

Next service: tomorrow 00:07 from Zutphen · Sat 21 Nov

Next departure 00:07 tomorrow · Zutphen
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 18 full · 2 partial · 4 no data
On-time · 90 days
81%
26/32 runs under 3 min
RT coverage: 28 full · 4 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Nijmegen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 18 Nov Max en route +10 min · last fix heading to — +10 min
  • Wed 7 Oct Max en route +10 min · last fix heading to — +9 min
  • Fri 13 Nov Max en route +9 min · last fix heading to — +9 min
  • Tue 6 Oct Max en route +11 min · last fix heading to Zutphen +8 min
  • Sat 14 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 26
  • 3–10 min 16% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 80% T n=5
  • 67% W n=6
  • 100% T n=5
  • 67% F n=6
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 32 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
00:07on time +2 min
00:12≈ on time ≈ +3 min
00:17 / 00:18≈ on time ≈ +3 min
00:23≈ on time ≈ +3 min
00:27≈ on time ≈ +3 min
00:30≈ on time ≈ +3 min
00:33≈ on time ≈ +3 min
00:36 / 00:41≈ on time ≈ +4 min
00:46≈ on time ≈ +4 min
00:50≈ on time ≈ +5 min
00:55≈ on time ≈ +5 min
00:58on time +6 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
Fri 20 Nov— 01:04+3 min+3 min
Thu 19 Nov— 00:590 min—
Wed 18 Nov— 01:19+10 min+10 min
Sun 15 NovNijmegen Lent 01:090 min—
Sat 14 Nov— 01:04+4 min+4 min
Fri 13 Nov— 01:14+9 min+9 min
Thu 12 Nov— 00:590 min—
Wed 11 Nov— 00:590 min—
Tue 10 Nov— 00:590 min—
Sun 8 NovNijmegen Lent 01:09Partial coverage0 min—
Sat 7 Nov— 01:02+2 min+4 min
Fri 6 Nov— 01:08No data—
Thu 5 Nov— 00:590 min—
Wed 4 Nov— 01:040 min—
Sun 1 NovNijmegen Lent 01:28Partial coverage0 min—
Sat 31 Oct— 00:590 min—
Fri 30 Oct— 00:590 min—
Thu 29 Oct— 00:59No data—
Wed 28 Oct— 01:040 min—
Tue 27 Oct— 00:590 min—
Sun 25 OctNijmegen Lent 01:10No data—
Sat 24 Oct— 01:00+1 min+1 min
Fri 23 Oct— 01:140 min—
Thu 22 Oct— 00:59No data—
Wed 21 Oct— 00:590 min—
Tue 20 Oct— 01:000 min—
Sun 18 OctNijmegen Lent 01:09Partial coverage0 min—
Sat 17 OctNijmegen Lent 01:080 min+3 min
Fri 16 Oct— 01:000 min—
Thu 15 Oct— 00:590 min—