Train NS 5111 Den Haag Centraal – Dordrecht

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

Running now · updated 07:28

Heading to Dordrecht No data

Estimated arrival at Dordrecht 07:19

  1. Den Haag Centraal06:25
  2. Den Haag Moerwijk06:32
  3. Delft06:40
  4. Rotterdam Centraal06:53
  5. Rotterdam Zuid07:02
  6. Barendrecht07:09
  7. Dordrecht07:19
On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 16 full · 11 partial · 3 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 16 full · 13 partial · 60 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

  • Fri 23 Oct Max en route +5 min · last fix heading to Zwijndrecht +5 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Zwijndrecht +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=5
  • 100% T n=4
  • 75% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 29 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 10Today
06:25on time on time
06:28 / 06:29≈ on time ≈ on time
06:32≈ on time ≈ on time
06:35≈ on time ≈ on time
06:40≈ on time ≈ on time
06:43≈ on time ≈ on time
06:49≈ on time ≈ on time
06:53 / 06:56≈ on time ≈ on time
06:59≈ on time ≈ on time
07:02≈ on time ≈ on time
07:06≈ on time ≈ +1 min
07:09≈ on time ≈ +1 min
07:15≈ on time ≈ +1 min
07: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
Fri 6 NovZwijndrecht 07:25No data—
Thu 5 NovZwijndrecht 07:29No data—
Wed 4 NovZwijndrecht 07:29Partial coverage0 min—
Tue 3 NovZwijndrecht 07:29Partial coverage0 min—
Mon 2 NovZwijndrecht 07:32Partial coverage0 min—
Sun 1 NovZwijndrecht 07:290 min—
Sat 31 OctZwijndrecht 07:30+1 min+2 min
Fri 30 OctZwijndrecht 07:30+1 min+1 min
Thu 29 OctZwijndrecht 07:300 min—
Wed 28 OctZwijndrecht 07:29Partial coverage0 min—
Tue 27 OctZwijndrecht 07:32Partial coverage+3 min+3 min
Mon 26 OctZwijndrecht 07:30Partial coverage0 min—
Sun 25 OctZwijndrecht 07:29No data—
Sat 24 OctZwijndrecht 07:300 min—
Fri 23 OctZwijndrecht 07:34+5 min+5 min
Thu 22 OctZwijndrecht 07:300 min—
Wed 21 OctZwijndrecht 07:300 min—
Tue 20 OctZwijndrecht 07:290 min—
Mon 19 OctZwijndrecht 07:29Partial coverage0 min—
Sun 18 OctZwijndrecht 07:30+1 min+2 min
Sat 17 OctZwijndrecht 07:290 min—
Fri 16 OctZwijndrecht 07:300 min—
Thu 15 OctZwijndrecht 07:31Partial coverage+2 min+3 min
Wed 14 OctZwijndrecht 07:30Partial coverage0 min—
Tue 13 OctZwijndrecht 07:30Partial coverage+1 min—
Mon 12 OctZwijndrecht 07:290 min—
Sun 11 OctZwijndrecht 07:290 min—
Sat 10 OctZwijndrecht 07:300 min—
Fri 9 OctZwijndrecht 07:30+1 min—
Thu 8 OctZwijndrecht 07:30Partial coverage0 min—