Train NS 5125 Den Haag Centraal – Dordrecht

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

It has not run yet today

Last recorded run: Thursday 12 November +1 min

Next service: today 09:55 from Den Haag Centraal · Fri 13 Nov

Next departure 09:55 today · Den Haag Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 10 full · 11 partial · 8 no data
On-time · 90 days
97%
68/70 runs under 3 min
RT coverage: 55 full · 15 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Sat 3 Oct Max en route +4 min · last fix heading to Den Haag Centraal +4 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Zwijndrecht +4 min

Distribution · 90 days

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

  • Early 9% · 6
  • On time 89% · 62
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 100% T n=9
  • 100% W n=10
  • 100% T n=9
  • 100% F n=9
  • 91% S n=11
  • 100% S n=9

Stops and timetable

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

Last 90 days, 70 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
09:55on time on time
09:58 / 09:59≈ on time ≈ on time
10:02≈ on time ≈ on time
10:05≈ on time ≈ on time
10:10≈ on time ≈ on time
10:13≈ on time ≈ on time
10:19≈ on time ≈ on time
10:23 / 10:26≈ on time ≈ on time
10:29≈ on time ≈ on time
10:32≈ on time ≈ on time
10:36≈ on time ≈ on time
10:39≈ on time ≈ on time
10:45≈ on time ≈ on time
10:49on time on time

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 12 NovZwijndrecht 11:00Partial coverage+1 min—
Wed 11 NovZwijndrecht 10:59Partial coverage0 min—
Tue 10 NovZwijndrecht 10:59Partial coverage+1 min+3 min
Mon 9 NovZwijndrecht 11:04Partial coverage+4 min+4 min
Sun 8 NovDelft 10:290 min—
Sat 7 NovDelft 10:29+1 min+1 min
Fri 6 NovZwijndrecht 10:59No data—
Thu 5 NovZwijndrecht 10:59No data—
Wed 4 NovZwijndrecht 10:59Partial coverage0 min—
Tue 3 NovZwijndrecht 10:59No data—
Mon 2 NovZwijndrecht 10:59Partial coverage0 min—
Sun 1 NovZwijndrecht 11:010 min—
Sat 31 OctZwijndrecht 11:000 min—
Fri 30 OctZwijndrecht 10:590 min—
Thu 29 OctZwijndrecht 11:00Partial coverage0 min—
Wed 28 OctZwijndrecht 11:00Partial coverage0 min—
Tue 27 OctZwijndrecht 11:02Partial coverage0 min—
Mon 26 OctZwijndrecht 11:02Partial coverage0 min—
Sun 25 OctZwijndrecht 10:59No data—
Sat 24 OctZwijndrecht 10:590 min—
Fri 23 OctZwijndrecht 11:010 min—
Thu 22 OctZwijndrecht 11:000 min—
Wed 21 OctZwijndrecht 11:00No data—
Tue 20 OctZwijndrecht 11:00No data—
Mon 19 OctZwijndrecht 11:00Partial coverage0 min—
Sun 18 OctZwijndrecht 10:590 min—
Sat 17 OctZwijndrecht 10:590 min—
Fri 16 OctZwijndrecht 11:00No data—
Thu 15 OctZwijndrecht 11:00No data—
Wed 14 OctZwijndrecht 11:00Partial coverage0 min—