Train NS 7660 Arnhem Centraal – Nijmegen

Arnhem Centraal 17:11 → Nijmegen 17:28 Daily 0 h 17 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Nijmegen Lent at 17:39 +4 min

  1. Arnhem Centraal17:11
  2. Arnhem Zuid17:16
  3. Elst17:20
  4. Nijmegen Lent17:25
  5. Nijmegen17:28

Next service: tomorrow 17:11 from Arnhem Centraal · Mon 16 Nov

Next departure 17:11 tomorrow · Arnhem Centraal
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 16 full · 4 partial · 10 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 23 full · 5 partial · 61 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 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

  • Sun 1 Nov Max en route +6 min · last fix heading to Nijmegen Lent +5 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Nijmegen Lent +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Nijmegen Dukenburg +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 50% T n=2
  • 100% W n=4
  • 100% T n=2
  • 100% F n=4
  • 100% S n=6
  • 60% S n=5

Stops and timetable

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

Last 90 days, 28 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
17:11on time on time
17:16≈ on time ≈ +1 min
17:20≈ on time ≈ +1 min
17:25≈ on time ≈ +2 min
17:28on time +2 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 15 NovNijmegen Lent 17:39Partial coverage+4 min+4 min
Sat 14 NovNijmegen Dukenburg 17:490 min—
Fri 13 NovNijmegen Dukenburg 17:52+1 min—
Thu 12 NovNijmegen Dukenburg 17:49+2 min+2 min
Wed 11 NovNijmegen Dukenburg 17:49+2 min+2 min
Tue 10 NovNijmegen Dukenburg 17:49+4 min+4 min
Mon 9 NovNijmegen Dukenburg 17:49+2 min+2 min
Sun 8 NovNijmegen Lent 17:39Partial coverage0 min—
Sat 7 NovNijmegen Dukenburg 17:54+2 min+4 min
Fri 6 NovNijmegen Dukenburg 17:490 min—
Thu 5 NovNijmegen Dukenburg 17:49No data—
Wed 4 NovNijmegen Dukenburg 17:490 min—
Tue 3 NovNijmegen Dukenburg 17:49No data—
Mon 2 NovNijmegen Dukenburg 17:49No data—
Sun 1 NovNijmegen Lent 17:44Partial coverage+5 min+6 min
Sat 31 OctNijmegen Dukenburg 17:530 min—
Fri 30 OctNijmegen Dukenburg 17:520 min—
Thu 29 OctNijmegen Dukenburg 17:52No data—
Wed 28 OctNijmegen Dukenburg 17:520 min—
Tue 27 OctNijmegen Dukenburg 17:52No data—
Mon 26 OctNijmegen Dukenburg 17:52+3 min+3 min
Sun 25 OctNijmegen Lent 17:39No data—
Sat 24 OctNijmegen Dukenburg 17:53+1 min—
Fri 23 OctNijmegen Dukenburg 17:52No data—
Thu 22 OctNijmegen Dukenburg 17:52No data—
Wed 21 OctNijmegen Dukenburg 17:52No data—
Tue 20 OctNijmegen Dukenburg 17:52No data—
Mon 19 OctNijmegen Dukenburg 17:510 min—
Sun 18 OctNijmegen Lent 17:40Partial coverage0 min—
Sat 17 OctNijmegen Dukenburg 17:510 min—