Train NS 3118 Nijmegen – Den Haag Centraal

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

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 06:28 from Nijmegen · Fri 13 Nov

Next departure 06:28 today · Nijmegen
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 23 full · 3 partial · 2 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 32 full · 3 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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 100% · 35
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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:28on time on time
06:40 / 06:45≈ on time ≈ on time
06:55≈ on time ≈ on time
07:17 / 07:21≈ on time ≈ on time
07:38≈ on time ≈ on time
07:44 / 07:48≈ on time ≈ on time
07:54 / 07:57≈ on time ≈ on time
08:13 / 08:18≈ on time ≈ +1 min
08:29on 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 NovLeiden Centraal 08:32Partial coverage0 min—
Wed 11 NovLeiden Centraal 08:34+1 min+2 min
Tue 10 NovLeiden Centraal 08:34Partial coverage+2 min+3 min
Mon 9 NovLeiden Centraal 08:34Partial coverage+2 min+2 min
Sun 8 NovLeiden Centraal 08:330 min—
Sat 7 NovLeiden Centraal 08:33+1 min+1 min
Fri 6 NovLeiden Centraal 08:47No data—
Thu 5 NovLeiden Centraal 08:320 min—
Wed 4 NovLeiden Centraal 08:320 min+1 min
Tue 3 NovLeiden Centraal 08:440 min—
Mon 2 NovLeiden Centraal 08:390 min—
Sat 31 OctLeiden Centraal 08:33+1 min—
Fri 30 OctLeiden Centraal 08:330 min—
Thu 29 OctLeiden Centraal 08:330 min—
Wed 28 OctLeiden Centraal 08:330 min—
Tue 27 OctLeiden Centraal 08:330 min—
Mon 26 OctLeiden Centraal 08:350 min—
Sun 25 OctLeiden Centraal 08:33No data—
Sat 24 OctLeiden Centraal 08:330 min+1 min
Fri 23 OctLeiden Centraal 08:320 min—
Thu 22 OctLeiden Centraal 08:320 min—
Wed 21 OctLeiden Centraal 08:320 min—
Tue 20 OctLeiden Centraal 08:320 min—
Mon 19 OctLeiden Centraal 08:370 min—
Sun 18 OctLeiden Centraal 08:32+1 min—
Sat 17 OctLeiden Centraal 08:33+1 min—
Fri 16 OctLeiden Centraal 08:360 min—
Thu 15 OctLeiden Centraal 08:350 min—
Wed 14 OctLeiden Centraal 08:320 min—
Tue 13 OctLeiden Centraal 08:320 min—