Train NS 5049 Den Haag Centraal – Dordrecht

Den Haag Centraal 16:05 → Dordrecht 16:58 Daily 0 h 53 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:05 from Den Haag Centraal · Thu 5 Nov

Next departure 16:05 today · Den Haag Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 8 full · 10 partial · 8 no data
On-time · 90 days
97%
57/59 runs under 3 min
RT coverage: 47 full · 12 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Tue 29 Sept Max en route +4 min · last fix heading to Den Haag Moerwijk +3 min
  • Fri 25 Sept Max en route +6 min · last fix heading to Rijswijk +3 min

Distribution · 90 days

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

  • Early 25% · 15
  • On time 71% · 42
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 90% T n=10
  • 100% W n=8
  • 100% T n=10
  • 89% F n=9
  • 100% S n=10
  • 100% S n=1

Stops and timetable

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

Last 90 days, 59 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
16:05on time on time
16:08 / 16:09≈ on time ≈ on time
16:12≈ on time ≈ on time
16:16≈ on time ≈ on time
16:20≈ on time ≈ +1 min
16:23≈ on time ≈ +1 min
16:29≈ on time ≈ +1 min
16:33 / 16:35≈ on time ≈ +1 min
16:38≈ on time ≈ +1 min
16:41≈ on time ≈ +1 min
16:44≈ on time ≈ +1 min
16:48≈ on time ≈ +1 min
16:54≈ on time ≈ +2 min
16:58on time +2 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
Wed 4 NovZwijndrecht 17:09Partial coverage0 min—
Tue 3 NovZwijndrecht 17:14Partial coverage0 min—
Mon 2 NovZwijndrecht 17:08Partial coverage0 min—
Sat 31 OctZwijndrecht 17:170 min—
Fri 30 OctZwijndrecht 17:17No data—
Thu 29 OctZwijndrecht 17:08Partial coverage0 min—
Wed 28 OctZwijndrecht 17:11Partial coverage0 min—
Tue 27 OctZwijndrecht 17:08Partial coverage0 min—
Mon 26 OctZwijndrecht 17:08No data—
Sat 24 OctZwijndrecht 17:180 min—
Fri 23 OctZwijndrecht 17:16No data—
Thu 22 OctZwijndrecht 17:080 min—
Wed 21 OctZwijndrecht 17:08No data—
Tue 20 OctZwijndrecht 17:080 min—
Mon 19 OctZwijndrecht 17:08Partial coverage0 min—
Sun 18 OctZwijndrecht 17:170 min—
Sat 17 OctZwijndrecht 17:17No data—
Fri 16 OctZwijndrecht 17:170 min—
Thu 15 OctZwijndrecht 17:10No data—
Wed 14 OctZwijndrecht 17:08No data—
Tue 13 OctZwijndrecht 17:08No data—
Mon 12 OctZwijndrecht 17:12Partial coverage0 min—
Sat 10 OctZwijndrecht 17:170 min—
Fri 9 OctZwijndrecht 17:19+2 min+3 min
Thu 8 OctZwijndrecht 17:08Partial coverage0 min—
Wed 7 OctZwijndrecht 17:08Partial coverage0 min—
Tue 6 OctZwijndrecht 17:08Partial coverage0 min—
Mon 5 OctZwijndrecht 17:08Partial coverage0 min—
Sat 3 OctDen Haag Moerwijk 00:27+1 min+3 min
Fri 2 OctDen Haag Moerwijk 18:27−2 min+2 min