Train NS 5141 Den Haag Centraal – Dordrecht

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

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 13:55 from Den Haag Centraal · Thu 5 Nov

Next departure 13:55 today · Den Haag Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 11 full · 8 partial · 10 no data
On-time · 90 days
96%
55/57 runs under 3 min
RT coverage: 48 full · 9 partial · 31 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 16 Aug Max en route +47 min · last fix heading to Den Haag Centraal +47 min
  • Wed 23 Sept Max en route +8 min · last fix heading to Den Haag Centraal +8 min

Distribution · 90 days

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

  • Early 14% · 8
  • On time 82% · 47
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=10
  • 100% T n=9
  • 89% W n=9
  • 100% T n=9
  • 100% F n=7
  • 100% S n=7
  • 83% S n=6

Stops and timetable

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

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