Train NS 7657 Nijmegen – Arnhem Centraal

Nijmegen 16:33 → Arnhem Centraal 16:50 Daily 0 h 17 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Brummen at 17:32 No data

  1. Nijmegen16:33
  2. Nijmegen Lent16:36
  3. Elst16:41
  4. Arnhem Zuid16:45
  5. Arnhem Centraal16:50

Next service: tomorrow 16:33 from Nijmegen · Fri 6 Nov

Next departure 16:33 tomorrow · Nijmegen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 13 full · 3 partial · 14 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 14 full · 3 partial · 72 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 Arnhem Centraal, in minutes. One bar per run.

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

Worst days

  • Thu 8 Oct Max en route +4 min · last fix heading to Brummen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=3
  • 0% T n=1
  • 100% F n=1
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
16:33on time on time
16:36≈ on time ≈ on time
16:41≈ on time ≈ on time
16:45≈ on time ≈ +1 min
16:50on 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
Thu 5 NovBrummen 17:32No data—
Wed 4 NovBrummen 17:32No data—
Tue 3 NovBrummen 17:32No data—
Mon 2 NovBrummen 17:32No data—
Sun 1 NovArnhem Zuid 17:01Partial coverage+1 min—
Sat 31 OctBrummen 17:35+1 min+1 min
Fri 30 OctBrummen 17:34No data—
Thu 29 OctBrummen 17:32No data—
Wed 28 OctBrummen 17:320 min—
Tue 27 OctBrummen 17:32No data—
Mon 26 OctBrummen 17:320 min—
Sun 25 OctArnhem Zuid 17:00No data—
Sat 24 OctBrummen 17:340 min—
Fri 23 OctBrummen 17:49No data—
Thu 22 OctBrummen 17:32No data—
Wed 21 OctBrummen 17:340 min—
Tue 20 OctBrummen 17:320 min—
Mon 19 OctBrummen 17:320 min—
Sun 18 OctArnhem Zuid 17:02Partial coverage+2 min+2 min
Sat 17 OctBrummen 17:350 min—
Fri 16 OctBrummen 17:34No data—
Thu 15 OctBrummen 17:32No data—
Wed 14 OctBrummen 17:34No data—
Tue 13 OctBrummen 17:46No data—
Mon 12 OctBrummen 17:320 min—
Sun 11 OctArnhem Zuid 17:02Partial coverage+2 min+2 min
Sat 10 OctBrummen 17:340 min—
Fri 9 OctBrummen 17:320 min—
Thu 8 OctBrummen 23:27+4 min+4 min
Wed 7 OctBrummen 17:320 min—