Train NS 5209 Rotterdam Centraal – Dordrecht

Rotterdam Centraal 06:47 → Dordrecht 07:11 Mon, Tue, Wed, Thu 0 h 24 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Zwijndrecht at 07:28 No data

  1. Rotterdam Centraal06:47
  2. Rotterdam Blaak06:50
  3. Rotterdam Zuid06:53
  4. Rotterdam Lombardijen06:56
  5. Barendrecht07:02
  6. Zwijndrecht07:08
  7. Dordrecht07:11

Next service: Monday 06:47 from Rotterdam Centraal · Mon 9 Nov

Next departure 06:47 Monday · Rotterdam Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 partial · 3 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 12 full · 16 partial · 13 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: +2 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

  • Wed 7 Oct Max en route +9 min · last fix heading to Zwijndrecht +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 86% W n=7
  • 100% T n=7
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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
06:47on time on time
06:50≈ on time ≈ on time
06:53≈ on time ≈ on time
06:56 / 06:58≈ on time ≈ on time
07:02≈ on time ≈ on time
07:08≈ on time ≈ on time
07:11on 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 07:28No data—
Wed 4 NovZwijndrecht 07:22Partial coverage0 min—
Tue 3 NovZwijndrecht 07:22Partial coverage0 min—
Mon 2 NovZwijndrecht 07:23No data—
Thu 29 OctZwijndrecht 07:22Partial coverage0 min—
Wed 28 OctZwijndrecht 07:22Partial coverage0 min—
Tue 27 OctZwijndrecht 07:22Partial coverage0 min—
Mon 26 OctZwijndrecht 07:22No data—
Thu 22 OctZwijndrecht 07:22Partial coverage0 min—
Wed 21 OctZwijndrecht 07:22Partial coverage0 min—
Tue 20 OctZwijndrecht 07:22Partial coverage0 min—
Mon 19 OctZwijndrecht 07:22Partial coverage0 min—
Thu 15 OctZwijndrecht 07:24Partial coverage+2 min+2 min
Wed 14 OctZwijndrecht 07:22Partial coverage+3 min+3 min
Tue 13 OctRotterdam Centraal 07:41Partial coverage0 min+14 min
Mon 12 OctZwijndrecht 07:22Partial coverage0 min—
Thu 8 OctZwijndrecht 07:22Partial coverage0 min—
Wed 7 OctZwijndrecht 07:31Partial coverage+9 min+9 min
Tue 6 OctZwijndrecht 07:22Partial coverage0 min—
Mon 5 OctRotterdam Centraal 08:030 min—
Thu 1 OctZwijndrecht 07:22No data—
Wed 30 SeptZwijndrecht 07:22No data—
Tue 29 SeptZwijndrecht 07:23No data—
Mon 28 SeptZwijndrecht 07:22No data—
Thu 24 SeptRotterdam Centraal 16:440 min—
Wed 23 SeptRotterdam Centraal 18:250 min—
Tue 22 SeptRotterdam Centraal 00:260 min—
Mon 21 SeptRotterdam Centraal 14:100 min—
Thu 17 SeptRotterdam Centraal 08:440 min—
Wed 16 SeptZwijndrecht 07:22No data—