Train NS 3155 Den Haag Centraal – Nijmegen

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

It has not run yet today

Last recorded run: Wednesday 4 November +4 min

Next service: today 14:31 from Den Haag Centraal · Thu 5 Nov

Next departure 14:31 today · Den Haag Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 13 full · 5 partial · 11 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 14 full · 6 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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 6 Oct Max en route +7 min · last fix heading to Arnhem Centraal +7 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Veenendaal-De Klomp +4 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Arnhem Centraal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 15% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 67% T n=3
  • 67% W n=3
  • 100% T n=3
  • 100% F n=2
  • 67% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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
14:31on time on time
14:42 / 14:47≈ on time ≈ on time
15:03 / 15:05≈ on time ≈ +1 min
15:12 / 15:15≈ on time ≈ +1 min
15:20 / 15:22≈ on time ≈ +1 min
15:38 / 15:43≈ on time ≈ +1 min
16:05≈ on time ≈ +2 min
16:15 / 16:20≈ on time ≈ +2 min
16:32on 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
Wed 4 NovArnhem Centraal 16:42Partial coverage+4 min+4 min
Tue 3 NovArnhem Centraal 16:34No data—
Mon 2 NovArnhem Centraal 16:34No data—
Sun 1 NovSittard 17:320 min—
Sat 31 OctVeenendaal-De Klomp 16:21+4 min+4 min
Fri 30 OctVeenendaal-De Klomp 16:17No data—
Thu 29 OctVeenendaal-De Klomp 16:240 min—
Wed 28 OctVeenendaal-De Klomp 16:200 min—
Tue 27 OctVeenendaal-De Klomp 16:210 min—
Mon 26 OctVeenendaal-De Klomp 16:20No data—
Sun 25 OctVeenendaal-De Klomp 16:13No data—
Sat 24 OctVeenendaal-De Klomp 16:14+2 min+2 min
Fri 23 OctUtrecht Centraal 15:53No data—
Thu 22 OctUtrecht Centraal 15:540 min—
Wed 21 OctUtrecht Centraal 15:54No data—
Tue 20 OctUtrecht Centraal 15:540 min—
Mon 19 OctArnhem Centraal 16:42Partial coverage0 min—
Sun 18 OctArnhem Centraal 16:340 min—
Sat 17 OctArnhem Centraal 16:34No data—
Fri 16 OctArnhem Centraal 16:340 min—
Thu 15 OctArnhem Centraal 16:34No data—
Wed 14 OctArnhem Centraal 16:34No data—
Tue 13 OctArnhem Centraal 16:34No data—
Mon 12 OctArnhem Centraal 16:34Partial coverage0 min—
Sun 11 OctSittard 17:37+2 min+3 min
Sat 10 OctArnhem Centraal 16:52+2 min+2 min
Fri 9 OctArnhem Centraal 16:340 min—
Thu 8 OctArnhem Centraal 16:36Partial coverage+2 min+2 min
Wed 7 OctArnhem Centraal 16:34Partial coverage0 min—
Tue 6 OctArnhem Centraal 16:39Partial coverage+7 min+7 min