Train NS 5247 Den Haag Centraal – Dordrecht

Den Haag Centraal 15:46 → Dordrecht 16:39 Mon, Tue, Wed, Thu 0 h 53 min · 14 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 5 November No data

Next service: Monday 15:46 from Den Haag Centraal · Mon 9 Nov

Next departure 15:46 Monday · Den Haag Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 9 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 3 full · 8 partial · 30 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 11
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
15:46on time on time
15:49 / 15:50— —
15:53— —
15:56— —
16:00— —
16:03 / 16:04— —
16:10— —
16:14 / 16:17— —
16:20— —
16:23— —
16:26— —
16:30— —
16:35 / 16:36— —
16:39— —

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 16:53No data—
Wed 4 NovZwijndrecht 16:49Partial coverage0 min—
Tue 3 NovZwijndrecht 16:49No data—
Mon 2 NovZwijndrecht 16:49Partial coverage0 min—
Thu 29 OctZwijndrecht 16:50No data—
Wed 28 OctZwijndrecht 16:48No data—
Tue 27 OctZwijndrecht 16:52Partial coverage0 min—
Mon 26 OctZwijndrecht 16:50No data—
Thu 22 OctZwijndrecht 16:51No data—
Wed 21 OctZwijndrecht 16:500 min—
Tue 20 OctZwijndrecht 16:510 min—
Mon 19 OctZwijndrecht 16:50Partial coverage0 min—
Thu 15 OctZwijndrecht 16:51No data—
Wed 14 OctZwijndrecht 16:50No data—
Tue 13 OctZwijndrecht 16:51No data—
Mon 12 OctZwijndrecht 16:50+1 min—
Thu 8 OctZwijndrecht 16:51Partial coverage+1 min+1 min
Wed 7 OctZwijndrecht 16:51Partial coverage+1 min+2 min
Tue 6 OctZwijndrecht 16:52Partial coverage+1 min+2 min
Mon 5 OctZwijndrecht 16:48Partial coverage+1 min+1 min
Thu 1 OctZwijndrecht 16:50No data—
Wed 30 SeptZwijndrecht 16:50No data—
Tue 29 SeptZwijndrecht 16:50No data—
Mon 28 SeptZwijndrecht 16:51No data—
Thu 24 SeptZwijndrecht 16:50No data—
Wed 23 SeptZwijndrecht 16:50No data—
Tue 22 SeptZwijndrecht 16:51No data—
Mon 21 SeptZwijndrecht 16:50No data—
Thu 17 SeptZwijndrecht 16:53No data—
Wed 16 SeptZwijndrecht 16:52No data—