Train NS 7644 Arnhem Centraal – Nijmegen

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

✓ Today’s run finished

Today, last fix heading to Nijmegen Lent at 13:40 +1 min

  1. Arnhem Centraal13:11
  2. Arnhem Zuid13:16
  3. Elst13:20
  4. Nijmegen Lent13:25
  5. Nijmegen13:28

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

Next departure 13:11 tomorrow · Arnhem Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 11 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 22 full · 5 partial · 62 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 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

  • Tue 10 Nov Max en route +6 min · last fix heading to Nijmegen Dukenburg +6 min
  • Sun 11 Oct Max en route +3 min · last fix heading to Nijmegen Lent +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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