Train NS 5117 Den Haag Centraal – Dordrecht

Den Haag Centraal 07:55 → Dordrecht 08:49 Daily 0 h 54 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Zwijndrecht at 08:59 0 min

  1. Den Haag Centraal07:55
  2. Den Haag Moerwijk08:02
  3. Delft08:10
  4. Rotterdam Centraal08:23
  5. Rotterdam Zuid08:32
  6. Zwijndrecht08:45
  7. Dordrecht08:49

Next service: tomorrow 07:55 from Den Haag Centraal · Fri 13 Nov

Next departure 07:55 tomorrow · Den Haag Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 9 full · 10 partial · 11 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 12 full · 14 partial · 63 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: 0 min

Last 30 days

Arrival delay at Dordrecht, 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

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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:55on time on time
07:58 / 07:59≈ on time ≈ on time
08:02≈ on time ≈ on time
08:05≈ on time ≈ on time
08:10≈ on time ≈ on time
08:13≈ on time ≈ on time
08:19≈ on time ≈ on time
08:23 / 08:26≈ on time ≈ on time
08:29≈ on time ≈ on time
08:32≈ on time ≈ on time
08:36≈ on time ≈ on time
08:39≈ on time ≈ on time
08:45≈ on time ≈ on time
08:49on time on time

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 NovZwijndrecht 08:59Partial coverage0 min—
Wed 11 NovZwijndrecht 08:59Partial coverage0 min—
Tue 10 NovZwijndrecht 08:59Partial coverage+1 min+1 min
Mon 9 NovZwijndrecht 08:59Partial coverage0 min—
Sun 8 NovDelft 08:290 min—
Sat 7 NovDelft 08:290 min—
Fri 6 NovZwijndrecht 08:59No data—
Thu 5 NovZwijndrecht 09:03Partial coverage0 min—
Wed 4 NovZwijndrecht 08:59Partial coverage0 min—
Tue 3 NovZwijndrecht 08:59No data—
Mon 2 NovZwijndrecht 08:59Partial coverage0 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:59Partial coverage0 min—
Mon 26 OctZwijndrecht 09:01Partial coverage0 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:00Partial coverage0 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—