Train NS 5127 Den Haag Centraal – Dordrecht

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

Running now · updated 10:48

Heading to Dordrecht No data

Estimated arrival at Dordrecht 11:19 · 61 km/h

  1. Den Haag Centraal10:25
  2. Den Haag Moerwijk10:32
  3. Delft10:40
  4. Rotterdam Centraal10:53
  5. Rotterdam Zuid11:02
  6. Barendrecht11:09
  7. Dordrecht11:19
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 12 no data
On-time · 90 days
95%
59/62 runs under 3 min
RT coverage: 53 full · 9 partial · 27 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

  • Fri 2 Oct Max en route +11 min · last fix heading to Den Haag Centraal +11 min
  • Fri 18 Sept Max en route +12 min · last fix heading to Rijswijk +9 min
  • Sat 19 Sept Max en route +5 min · last fix heading to Rijswijk +5 min

Distribution · 90 days

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

  • Early 16% · 10
  • On time 79% · 49
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=11
  • 100% W n=10
  • 100% T n=8
  • 75% F n=8
  • 89% S n=9
  • 100% S n=6

Stops and timetable

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

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