Train NS 5167 Den Haag Centraal – Dordrecht

Den Haag Centraal 20:26 → Dordrecht 21:19 Daily 0 h 53 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 20:26 from Den Haag Centraal · Thu 12 Nov

Next departure 20:26 today · Den Haag Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 7 no data
On-time · 90 days
95%
38/40 runs under 3 min
RT coverage: 39 full · 1 partial · 15 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

  • Wed 4 Nov Max en route +6 min · last fix heading to — +6 min
  • Sun 4 Oct Max en route +5 min · last fix heading to Den Haag Centraal +5 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 93% · 37
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=3
  • 80% W n=5
  • 100% T n=5
  • 100% F n=6
  • 100% S n=7
  • 88% S n=8

Stops and timetable

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

Last 90 days, 40 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
20:26on time on time
20:29 / 20:30≈ on time ≈ on time
20:33≈ on time ≈ on time
20:36≈ on time ≈ on time
20:40≈ on time ≈ on time
20:43≈ on time ≈ on time
20:50≈ on time ≈ +1 min
20:54 / 20:56≈ on time ≈ +1 min
20:59≈ on time ≈ +1 min
21:02≈ on time ≈ +1 min
21:06≈ on time ≈ +1 min
21:09≈ on time ≈ +1 min
21:15≈ on time ≈ +1 min
21:19on 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 Nov— 21:190 min—
Tue 10 Nov— 21:190 min—
Mon 9 Nov— 21:190 min—
Sun 8 NovDelft 20:590 min—
Sat 7 NovDelft 20:590 min—
Fri 6 Nov— 21:190 min—
Thu 5 Nov— 21:190 min—
Wed 4 Nov— 21:29+6 min+6 min
Mon 2 Nov— 21:190 min—
Sun 1 NovZwijndrecht 21:29+1 min—
Sat 31 OctZwijndrecht 21:290 min—
Fri 30 Oct— 21:210 min—
Thu 29 Oct— 21:190 min—
Wed 28 Oct— 21:200 min—
Tue 27 Oct— 21:21No data—
Mon 26 Oct— 21:21No data—
Sun 25 OctZwijndrecht 21:41No data—
Sat 24 OctZwijndrecht 21:29No data—
Fri 23 Oct— 21:200 min—
Thu 22 Oct— 21:210 min—
Wed 21 Oct— 21:29No data—
Tue 20 Oct— 21:21No data—
Mon 19 Oct— 21:210 min—
Sun 18 OctZwijndrecht 21:290 min—
Sat 17 OctZwijndrecht 21:29No data—
Fri 16 Oct— 21:200 min—
Thu 15 Oct— 22:530 min—
Wed 14 Oct— 21:310 min—
Tue 13 Oct— 21:210 min—
Mon 12 Oct— 21:200 min—