Train NS 5019 Den Haag Centraal – Dordrecht

Den Haag Centraal 08:35 → Dordrecht 09:28 Daily 0 h 53 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Zwijndrecht at 09:39 No data

  1. Den Haag Centraal08:35
  2. Den Haag Moerwijk08:42
  3. Delft08:50
  4. Rotterdam Centraal09:03
  5. Rotterdam Zuid09:11
  6. Zwijndrecht09:24
  7. Dordrecht09:28

Next service: tomorrow 08:35 from Den Haag Centraal · Fri 6 Nov

Next departure 08:35 tomorrow · Den Haag Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 8 full · 10 partial · 4 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 8 full · 11 partial · 46 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: 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 9 Oct Max en route +4 min · last fix heading to Zwijndrecht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
08:35on time on time
08:38 / 08:39≈ on time ≈ on time
08:42≈ on time ≈ on time
08:46≈ on time ≈ on time
08:50≈ on time ≈ on time
08:53≈ on time ≈ on time
08:59≈ on time ≈ +1 min
09:03 / 09:05≈ on time ≈ +1 min
09:08≈ on time ≈ +1 min
09:11≈ on time ≈ +1 min
09:14≈ on time ≈ +1 min
09:18≈ on time ≈ +1 min
09:24≈ on time ≈ +1 min
09:28on 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 NovZwijndrecht 09:39No data—
Wed 4 NovZwijndrecht 09:38Partial coverage0 min—
Tue 3 NovZwijndrecht 09:39Partial coverage0 min—
Mon 2 NovZwijndrecht 09:39Partial coverage0 min—
Fri 30 OctZwijndrecht 09:460 min—
Thu 29 OctZwijndrecht 09:39Partial coverage0 min—
Wed 28 OctZwijndrecht 09:44Partial coverage0 min—
Tue 27 OctZwijndrecht 09:38Partial coverage0 min—
Mon 26 OctZwijndrecht 09:38Partial coverage0 min—
Fri 23 OctZwijndrecht 09:460 min—
Thu 22 OctZwijndrecht 09:400 min—
Wed 21 OctZwijndrecht 09:38No data—
Tue 20 OctZwijndrecht 09:380 min—
Mon 19 OctZwijndrecht 09:380 min—
Fri 16 OctZwijndrecht 09:470 min—
Thu 15 OctZwijndrecht 10:580 min—
Wed 14 OctZwijndrecht 09:38No data—
Tue 13 OctZwijndrecht 09:38Partial coverage0 min—
Mon 12 OctZwijndrecht 09:42No data—
Fri 9 OctZwijndrecht 09:51+4 min+4 min
Thu 8 OctZwijndrecht 09:38Partial coverage0 min—
Wed 7 OctZwijndrecht 09:38Partial coverage0 min—
Tue 6 OctZwijndrecht 09:38Partial coverage0 min—
Mon 5 OctZwijndrecht 09:38No data—
Fri 2 OctZwijndrecht 09:46No data—
Thu 1 OctZwijndrecht 09:38No data—
Wed 30 SeptZwijndrecht 09:39No data—
Tue 29 SeptZwijndrecht 09:38No data—
Mon 28 SeptZwijndrecht 09:38No data—
Fri 25 SeptZwijndrecht 09:46No data—