Train NS 3156 Nijmegen – Den Haag Centraal

Nijmegen 15:58 → Den Haag Centraal 17:59 Daily 2 h 01 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 15:58 from Nijmegen · Thu 5 Nov

Next departure 15:58 today · Nijmegen
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 15 full · 5 partial · 9 no data
On-time · 90 days
82%
18/22 runs under 3 min
RT coverage: 16 full · 6 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +7 min

Last 30 days

Arrival delay at Den Haag 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

  • Sun 1 Nov Max en route +12 min · last fix heading to Leiden Centraal +11 min
  • Thu 8 Oct Max en route +9 min · last fix heading to Leiden Centraal +8 min
  • Tue 6 Oct Max en route +8 min · last fix heading to Leiden Centraal +7 min
  • Sun 18 Oct Max en route +8 min · last fix heading to Leiden Centraal +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 18
  • 3–10 min 14% · 3
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
15:58on time on time
16:10 / 16:15≈ on time ≈ on time
16:25≈ on time ≈ +1 min
16:47 / 16:51≈ on time ≈ +2 min
17:08≈ on time ≈ +2 min
17:14 / 17:20≈ on time ≈ +2 min
17:27 / 17:29≈ on time ≈ +3 min
17:45 / 17:48≈ on time ≈ +3 min
17:59on time +4 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 NovLeiden Centraal 18:03Partial coverage0 min—
Tue 3 NovLeiden Centraal 18:02No data—
Mon 2 NovLeiden Centraal 18:02No data—
Sun 1 NovLeiden Centraal 18:13+11 min+12 min
Sat 31 OctLeiden Centraal 18:02+1 min+1 min
Fri 30 OctLeiden Centraal 18:02No data—
Thu 29 OctLeiden Centraal 18:020 min—
Wed 28 OctLeiden Centraal 18:190 min—
Tue 27 OctLeiden Centraal 18:13No data—
Mon 26 OctLeiden Centraal 18:02+1 min+1 min
Sun 25 OctLeiden Centraal 18:02No data—
Sat 24 OctLeiden Centraal 18:040 min+2 min
Fri 23 OctLeiden Centraal 18:050 min—
Thu 22 OctLeiden Centraal 18:020 min—
Wed 21 OctLeiden Centraal 18:03No data—
Tue 20 OctLeiden Centraal 18:140 min—
Mon 19 OctLeiden Centraal 18:02Partial coverage0 min—
Sun 18 OctLeiden Centraal 18:13+7 min+8 min
Sat 17 OctLeiden Centraal 18:020 min—
Fri 16 OctLeiden Centraal 18:050 min—
Thu 15 OctLeiden Centraal 18:03No data—
Wed 14 OctLeiden Centraal 18:04No data—
Tue 13 OctLeiden Centraal 18:14No data—
Mon 12 OctLeiden Centraal 18:02Partial coverage0 min—
Sun 11 OctLeiden Centraal 18:020 min+1 min
Sat 10 OctLeiden Centraal 18:03+1 min+1 min
Fri 9 OctLeiden Centraal 18:020 min—
Thu 8 OctLeiden Centraal 18:17Partial coverage+8 min+9 min
Wed 7 OctLeiden Centraal 18:02Partial coverage0 min—
Tue 6 OctLeiden Centraal 18:15Partial coverage+7 min+8 min