Train NS 3127 Den Haag Centraal – Nijmegen

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

It has not run yet today

Last recorded run: Thursday 12 November +3 min

Next service: today 07:31 from Den Haag Centraal · Fri 13 Nov

Next departure 07:31 today · Den Haag Centraal
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 16 full · 6 partial · 7 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 19 full · 9 partial · 58 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: +3 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 +7 min · last fix heading to Arnhem Centraal +7 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Arnhem Centraal +5 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Arnhem Centraal +3 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=3
  • 75% T n=4
  • 75% W n=4
  • 75% T n=4
  • 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, 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
07:31on time on time
07:42 / 07:47≈ on time ≈ on time
08:03 / 08:05≈ on time ≈ on time
08:12 / 08:15≈ on time ≈ on time
08:20 / 08:22≈ on time ≈ +1 min
08:38 / 08:43≈ on time ≈ +1 min
09:05≈ on time ≈ +1 min
09:15 / 09:20≈ on time ≈ +1 min
09: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 09:37Partial coverage+3 min+3 min
Wed 11 NovArnhem Centraal 09:39Partial coverage+5 min+5 min
Tue 10 NovArnhem Centraal 09:39Partial coverage+7 min+7 min
Mon 9 NovArnhem Centraal 09:34Partial coverage0 min—
Sun 8 NovAmsterdam Bijlmer ArenA 08:34+1 min+3 min
Sat 7 NovAmsterdam Bijlmer ArenA 08:340 min—
Fri 6 NovArnhem Centraal 10:04No data—
Thu 5 NovArnhem Centraal 09:39No data—
Wed 4 NovArnhem Centraal 09:34Partial coverage0 min—
Tue 3 NovArnhem Centraal 09:34No data—
Mon 2 NovArnhem Centraal 09:39No data—
Sun 1 NovSittard 10:35+3 min+3 min
Sat 31 OctAmsterdam Bijlmer ArenA 08:310 min—
Fri 30 OctVeenendaal-De Klomp 09:160 min—
Thu 29 OctVeenendaal-De Klomp 09:280 min—
Wed 28 OctVeenendaal-De Klomp 09:210 min—
Tue 27 OctVeenendaal-De Klomp 09:200 min—
Mon 26 OctVeenendaal-De Klomp 09:220 min—
Sun 25 OctAmsterdam Bijlmer ArenA 08:34No data—
Sat 24 OctAmsterdam Bijlmer ArenA 08:390 min—
Fri 23 OctUtrecht Centraal 08:540 min—
Thu 22 OctUtrecht Centraal 08:560 min—
Wed 21 OctUtrecht Centraal 08:56No data—
Tue 20 OctUtrecht Centraal 08:540 min—
Mon 19 OctArnhem Centraal 09:34Partial coverage0 min—
Sun 18 OctAmsterdam Bijlmer ArenA 08:340 min—
Sat 17 OctAmsterdam Bijlmer ArenA 08:35+1 min+2 min
Fri 16 OctArnhem Centraal 09:340 min—
Thu 15 OctArnhem Centraal 10:58No data—
Wed 14 OctArnhem Centraal 09:34No data—