Train NS 5153 Den Haag Centraal – Dordrecht

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 16:55 from Den Haag Centraal · Fri 6 Nov

Next departure 16:55 today · Den Haag Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 12 full · 5 partial · 12 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 12 full · 8 partial · 68 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: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:55on time on time
16:58 / 16:59≈ on time ≈ on time
17:02≈ on time ≈ on time
17:05≈ on time ≈ on time
17:10≈ on time ≈ +1 min
17:13≈ on time ≈ +1 min
17:19≈ on time ≈ +1 min
17:23 / 17:26≈ on time ≈ +1 min
17:29≈ on time ≈ +1 min
17:32≈ on time ≈ +1 min
17:36≈ on time ≈ +2 min
17:39≈ on time ≈ +2 min
17:45≈ on time ≈ +2 min
17:49on time +2 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 5 NovZwijndrecht 17:59No data—
Wed 4 NovZwijndrecht 17:59Partial coverage0 min—
Tue 3 NovZwijndrecht 17:59No data—
Mon 2 NovZwijndrecht 17:59No data—
Sun 1 NovZwijndrecht 17:590 min—
Sat 31 OctZwijndrecht 18:000 min—
Fri 30 OctZwijndrecht 17:590 min—
Thu 29 OctZwijndrecht 17:59No data—
Wed 28 OctZwijndrecht 17:57Partial coverage0 min—
Tue 27 OctZwijndrecht 18:00No data—
Mon 26 OctZwijndrecht 17:59+3 min+3 min
Sun 25 OctZwijndrecht 18:00No data—
Sat 24 OctZwijndrecht 18:02+2 min+3 min
Fri 23 OctZwijndrecht 18:00No data—
Thu 22 OctZwijndrecht 17:55No data—
Wed 21 OctZwijndrecht 17:590 min—
Tue 20 OctZwijndrecht 17:590 min—
Mon 19 OctZwijndrecht 17:59Partial coverage0 min—
Sun 18 OctZwijndrecht 18:010 min—
Sat 17 OctZwijndrecht 18:00No data—
Fri 16 OctZwijndrecht 17:590 min—
Thu 15 OctRotterdam Zuid 17:46No data—
Wed 14 OctZwijndrecht 18:05No data—
Tue 13 OctZwijndrecht 17:59Partial coverage0 min—
Mon 12 OctZwijndrecht 18:01No data—
Sun 11 OctZwijndrecht 18:090 min—
Sat 10 OctZwijndrecht 18:030 min—
Fri 9 OctZwijndrecht 17:590 min—
Thu 8 OctZwijndrecht 17:58Partial coverage+2 min+3 min
Wed 7 OctZwijndrecht 17:59Partial coverage0 min—