Train NS 5117 Den Haag Centraal – Delft Campus

Den Haag Centraal 08:00 → Delft Campus 08:17 Daily 0 h 17 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 08:00 from Den Haag Centraal · Sun 8 Nov

Next departure 08:00 today · Den Haag Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 12 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Delft Campus, 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 +5 min · last fix heading to Zwijndrecht +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
08:00on time on time
08:03 / 08:04≈ on time ≈ on time
08:08≈ on time ≈ on time
08:10≈ on time ≈ on time
08:15≈ on time ≈ on time
08:17on 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
Sat 7 NovDelft 08:29Partial coverage0 min—
Fri 6 NovZwijndrecht 08:59No data—
Thu 5 NovZwijndrecht 09:030 min—
Wed 4 NovZwijndrecht 08:590 min—
Tue 3 NovZwijndrecht 08:59No data—
Mon 2 NovZwijndrecht 08:590 min—
Sun 1 NovZwijndrecht 09:02+5 min+5 min
Sat 31 OctZwijndrecht 08:590 min—
Fri 30 OctZwijndrecht 13:220 min—
Thu 29 OctZwijndrecht 09:01No data—
Wed 28 OctZwijndrecht 08:59No data—
Tue 27 OctZwijndrecht 08:590 min—
Mon 26 OctZwijndrecht 09:010 min—
Sun 25 OctZwijndrecht 08:59No data—
Sat 24 OctZwijndrecht 08:590 min—
Fri 23 OctZwijndrecht 09:00No data—
Thu 22 OctZwijndrecht 09:00No data—
Wed 21 OctZwijndrecht 09:00No data—
Tue 20 OctZwijndrecht 08:59No data—
Mon 19 OctZwijndrecht 09:000 min—
Sun 18 OctZwijndrecht 08:590 min—
Sat 17 OctZwijndrecht 08:590 min—
Fri 16 OctZwijndrecht 08:590 min—
Thu 15 OctZwijndrecht 09:00No data—
Wed 14 OctZwijndrecht 09:06No data—
Tue 13 OctZwijndrecht 09:03No data—
Mon 12 OctZwijndrecht 08:590 min—
Sun 11 OctZwijndrecht 08:590 min—
Sat 10 OctZwijndrecht 08:590 min—
Fri 9 OctZwijndrecht 09:000 min—