Train NS 3123 Den Haag Centraal – Nijmegen

Den Haag Centraal 06:31 → Nijmegen 08:32 Daily 2 h 01 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Arnhem Centraal at 08:34 +1 min

  1. Den Haag Centraal06:31
  2. Leiden Centraal06:42
  3. Amsterdam Zuid07:12
  4. Amsterdam Bijlmer ArenA07:20
  5. Utrecht Centraal07:38
  6. Arnhem Centraal08:15
  7. Nijmegen08:32

Next service: tomorrow 06:31 from Den Haag Centraal · Fri 13 Nov

Next departure 06:31 tomorrow · Den Haag Centraal
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 17 full · 10 partial · 3 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 20 full · 15 partial · 53 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: +1 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 11 Nov Max en route +16 min · last fix heading to Arnhem Centraal +16 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 34
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 35 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
06:31on time on time
06:42 / 06:47≈ on time ≈ on time
07:03 / 07:05≈ on time ≈ on time
07:12 / 07:15≈ on time ≈ on time
07:20 / 07:22≈ on time ≈ on time
07:38 / 07:43≈ on time ≈ +1 min
08:05≈ on time ≈ +1 min
08:15 / 08:20≈ on time ≈ +1 min
08:32on 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 12 NovArnhem Centraal 08:34Partial coverage+1 min+1 min
Wed 11 NovArnhem Centraal 08:59Partial coverage+16 min+16 min
Tue 10 NovArnhem Centraal 08:34Partial coverage+2 min+2 min
Mon 9 NovArnhem Centraal 08:34Partial coverage0 min—
Sun 8 NovAmsterdam Bijlmer ArenA 07:340 min—
Sat 7 NovAmsterdam Bijlmer ArenA 09:290 min—
Fri 6 NovArnhem Centraal 08:39No data—
Thu 5 NovArnhem Centraal 08:34No data—
Wed 4 NovArnhem Centraal 08:34Partial coverage0 min—
Tue 3 NovArnhem Centraal 08:34Partial coverage0 min—
Mon 2 NovArnhem Centraal 08:38Partial coverage0 min—
Sun 1 NovSittard 09:370 min+2 min
Sat 31 OctAmsterdam Bijlmer ArenA 07:340 min—
Fri 30 OctVeenendaal-De Klomp 08:170 min—
Thu 29 OctVeenendaal-De Klomp 08:210 min—
Wed 28 OctVeenendaal-De Klomp 08:220 min—
Tue 27 OctVeenendaal-De Klomp 08:210 min—
Mon 26 OctVeenendaal-De Klomp 08:200 min—
Sun 25 OctAmsterdam Bijlmer ArenA 09:30No data—
Sat 24 OctAmsterdam Bijlmer ArenA 07:370 min—
Fri 23 OctUtrecht Centraal 07:530 min—
Thu 22 OctUtrecht Centraal 07:540 min—
Wed 21 OctUtrecht Centraal 07:540 min—
Tue 20 OctUtrecht Centraal 07:540 min—
Mon 19 OctArnhem Centraal 08:40Partial coverage0 min—
Sun 18 OctAmsterdam Bijlmer ArenA 09:410 min—
Sat 17 OctAmsterdam Bijlmer ArenA 07:35+1 min+2 min
Fri 16 OctArnhem Centraal 08:340 min—
Thu 15 OctArnhem Centraal 08:34Partial coverage0 min—
Wed 14 OctArnhem Centraal 08:34Partial coverage0 min—