Train NS 5151 Den Haag Centraal – Dordrecht

Den Haag Centraal 16:25 → Dordrecht 17:19 Daily 0 h 54 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November +1 min

Next service: today 16:25 from Den Haag Centraal · Tue 10 Nov

Next departure 16:25 today · Den Haag Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 11 full · 8 partial · 10 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 14 full · 12 partial · 62 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 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 8 Nov Max en route +8 min · last fix heading to Delft +7 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Zwijndrecht +4 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 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=1
  • 100% W n=3
  • 67% T n=3
  • 100% F n=5
  • 100% S n=4
  • 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
16:25on time on time
16:28 / 16:29≈ on time ≈ on time
16:32≈ on time ≈ on time
16:35≈ on time ≈ on time
16:40≈ on time ≈ on time
16:43≈ on time ≈ on time
16:49≈ on time ≈ on time
16:53 / 16:56≈ on time ≈ on time
16:59≈ on time ≈ on time
17:02≈ on time ≈ on time
17:06≈ on time ≈ on time
17:09≈ on time ≈ on time
17:15≈ on time ≈ on time
17:19on 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
Mon 9 NovZwijndrecht 17:29Partial coverage+1 min+1 min
Sun 8 NovDelft 17:07+7 min+8 min
Sat 7 NovDelft 16:590 min—
Fri 6 NovZwijndrecht 17:290 min—
Thu 5 NovZwijndrecht 17:39No data—
Wed 4 NovZwijndrecht 17:29Partial coverage0 min—
Tue 3 NovZwijndrecht 17:29No data—
Mon 2 NovZwijndrecht 17:29Partial coverage0 min—
Sun 1 NovZwijndrecht 17:300 min—
Sat 31 OctZwijndrecht 17:290 min—
Fri 30 OctZwijndrecht 17:300 min—
Thu 29 OctZwijndrecht 17:30Partial coverage0 min—
Wed 28 OctZwijndrecht 17:29Partial coverage0 min—
Tue 27 OctZwijndrecht 17:29No data—
Mon 26 OctZwijndrecht 17:29Partial coverage0 min—
Sun 25 OctZwijndrecht 17:31No data—
Sat 24 OctZwijndrecht 17:30+1 min+2 min
Fri 23 OctZwijndrecht 17:300 min—
Thu 22 OctZwijndrecht 17:300 min—
Wed 21 OctZwijndrecht 17:38No data—
Tue 20 OctZwijndrecht 17:30No data—
Mon 19 OctZwijndrecht 17:32Partial coverage0 min—
Sun 18 OctZwijndrecht 17:290 min—
Sat 17 OctZwijndrecht 17:30No data—
Fri 16 OctZwijndrecht 17:290 min—
Thu 15 OctZwijndrecht 17:29No data—
Wed 14 OctZwijndrecht 17:30No data—
Tue 13 OctZwijndrecht 17:30No data—
Mon 12 OctZwijndrecht 17:32Partial coverage0 min—
Sun 11 OctZwijndrecht 17:460 min—