Train NS 5107 Den Haag Centraal – Dordrecht

Den Haag Centraal 05:36 → Dordrecht 06:36 Daily 1 h 00 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Zwijndrecht at 06:47 0 min

  1. Den Haag Centraal05:36
  2. Den Haag Moerwijk05:48
  3. Delft05:55
  4. Rotterdam Centraal06:09
  5. Rotterdam Zuid06:19
  6. Zwijndrecht06:31
  7. Dordrecht06:36

Next service: tomorrow 05:36 from Den Haag Centraal · Fri 6 Nov

Next departure 05:36 tomorrow · Den Haag Centraal
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 22 full · 7 partial · 1 no data
On-time · 90 days
98%
58/59 runs under 3 min
RT coverage: 51 full · 8 partial · 30 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

  • Fri 30 Oct Max en route +6 min · last fix heading to Zwijndrecht +6 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 93% · 55
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 100% W n=10
  • 100% T n=11
  • 89% F n=9
  • 100% S n=5
  • 100% S n=3

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
05:36on time on time
05:39 / 05:45≈ on time ≈ on time
05:48≈ on time ≈ on time
05:51≈ on time ≈ on time
05:55≈ on time ≈ on time
05:58≈ on time ≈ on time
06:05≈ on time ≈ on time
06:09 / 06:13≈ on time ≈ on time
06:16≈ on time ≈ on time
06:19≈ on time ≈ on time
06:22≈ on time ≈ on time
06:26≈ on time ≈ on time
06:31 / 06:32≈ on time ≈ on time
06:36on 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 5 NovZwijndrecht 06:47Partial coverage0 min—
Wed 4 NovZwijndrecht 06:470 min—
Tue 3 NovZwijndrecht 06:47Partial coverage0 min—
Mon 2 NovZwijndrecht 06:470 min—
Sun 1 NovZwijndrecht 06:50+1 min+1 min
Sat 31 OctZwijndrecht 06:35+2 min+2 min
Fri 30 OctZwijndrecht 06:52+6 min+6 min
Thu 29 OctZwijndrecht 06:470 min—
Wed 28 OctZwijndrecht 06:470 min—
Tue 27 OctZwijndrecht 06:47Partial coverage0 min—
Mon 26 OctZwijndrecht 06:470 min—
Sun 25 OctZwijndrecht 06:48No data—
Sat 24 OctZwijndrecht 06:340 min—
Fri 23 OctZwijndrecht 06:460 min—
Thu 22 OctZwijndrecht 06:46Partial coverage0 min—
Wed 21 OctZwijndrecht 06:470 min—
Tue 20 OctZwijndrecht 06:47Partial coverage0 min—
Mon 19 OctZwijndrecht 06:470 min—
Sun 18 OctZwijndrecht 06:48+1 min+1 min
Sat 17 OctZwijndrecht 06:340 min—
Fri 16 OctZwijndrecht 06:470 min—
Thu 15 OctZwijndrecht 06:46Partial coverage0 min—
Wed 14 OctZwijndrecht 06:460 min—
Tue 13 OctZwijndrecht 06:460 min—
Mon 12 OctZwijndrecht 06:470 min—
Sun 11 OctZwijndrecht 06:570 min—
Sat 10 OctZwijndrecht 06:340 min—
Fri 9 OctZwijndrecht 06:460 min—
Thu 8 OctZwijndrecht 06:47Partial coverage+1 min+2 min
Wed 7 OctZwijndrecht 06:470 min—