Train NS 5157 Den Haag Centraal – Dordrecht

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

It has not run yet today

Last recorded run: Wednesday 11 November +7 min

Next service: today 17:55 from Den Haag Centraal · Thu 12 Nov

Next departure 17:55 today · Den Haag Centraal
On-time · 30 days
89%
17/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
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 11 Nov Max en route +8 min · last fix heading to Delft Campus +7 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Schiedam Centrum +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 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 75% W n=4
  • 100% T n=2
  • 100% F n=5
  • 100% S n=3
  • 100% 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
17:55on time on time
17:58 / 17:59≈ on time ≈ on time
18:02≈ on time ≈ on time
18:05≈ on time ≈ on time
18:10≈ on time ≈ on time
18:13≈ on time ≈ on time
18:19≈ on time ≈ +1 min
18:23 / 18:26≈ on time ≈ +1 min
18:29≈ on time ≈ +1 min
18:32≈ on time ≈ +1 min
18:36≈ on time ≈ +1 min
18:39≈ on time ≈ +1 min
18:45≈ on time ≈ +1 min
18:49on 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
Wed 11 NovDelft Campus 18:59Partial coverage+7 min+8 min
Tue 10 NovSchiedam Centrum 18:59Partial coverage+5 min+5 min
Mon 9 NovDelft Campus 18:49Partial coverage0 min—
Sun 8 NovDelft 18:290 min—
Sat 7 NovDelft 18:290 min—
Fri 6 NovZwijndrecht 18:590 min—
Thu 5 NovDelft Campus 18:54No data—
Wed 4 NovDelft Campus 18:49No data—
Tue 3 NovDelft 18:52No data—
Mon 2 NovDelft 18:24Partial coverage0 min—
Sun 1 NovZwijndrecht 18:590 min—
Sat 31 OctZwijndrecht 19:160 min+13 min
Fri 30 OctZwijndrecht 18:590 min—
Thu 29 OctDen Haag Moerwijk 18:55Partial coverage0 min—
Wed 28 OctDelft Campus 18:50Partial coverage0 min—
Tue 27 OctRijswijk 18:57Partial coverage0 min—
Mon 26 OctRijswijk 18:59No data—
Sun 25 OctZwijndrecht 19:00No data—
Sat 24 OctZwijndrecht 19:09No data—
Fri 23 OctZwijndrecht 18:59+2 min+4 min
Thu 22 OctZwijndrecht 19:00No data—
Wed 21 OctBarendrecht 18:530 min—
Tue 20 OctZwijndrecht 18:500 min—
Mon 19 OctBarendrecht 18:53Partial coverage0 min—
Sun 18 OctZwijndrecht 19:01+2 min+2 min
Sat 17 OctZwijndrecht 18:59No data—
Fri 16 OctZwijndrecht 18:590 min—
Thu 15 OctRotterdam Blaak 18:52No data—
Wed 14 OctZwijndrecht 19:02No data—
Tue 13 OctBarendrecht 18:50No data—