Train NS 5262 Dordrecht – Rotterdam Centraal

Dordrecht 18:51 → Rotterdam Centraal 19:13 Mon, Tue, Wed, Thu 0 h 22 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 19:19 +3 min

  1. Dordrecht18:51
  2. Zwijndrecht18:54
  3. Barendrecht19:00
  4. Rotterdam Lombardijen19:03
  5. Rotterdam Zuid19:07
  6. Rotterdam Blaak19:10
  7. Rotterdam Centraal19:13

Next service: tomorrow 18:51 from Dordrecht · Tue 10 Nov

Next departure 18:51 tomorrow · Dordrecht
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 8 full · 0 partial · 8 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 11 full · 0 partial · 8 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 Rotterdam Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 9 Nov Max en route +3 min · last fix heading to — +3 min

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 91% · 10
  • 3–10 min 9% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • — 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, 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
18:51on time on time
18:54≈ on time ≈ on time
19:00≈ on time ≈ on time
19:03≈ on time ≈ +1 min
19:07≈ on time ≈ +1 min
19:10≈ on time ≈ +1 min
19:13on 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
Mon 9 Nov— 19:19+3 min+3 min
Thu 5 Nov— 19:14No data—
Wed 4 Nov— 19:190 min—
Mon 2 Nov— 19:19+1 min—
Thu 29 Oct— 19:140 min—
Wed 28 Oct— 19:150 min—
Tue 27 Oct— 19:23No data—
Mon 26 Oct— 19:080 min—
Thu 22 Oct— 19:15No data—
Wed 21 Oct— 19:15No data—
Tue 20 Oct— 19:150 min—
Mon 19 Oct— 19:170 min—
Thu 15 Oct— 01:25No data—
Wed 14 OctRotterdam Blaak 19:29No data—
Tue 13 Oct— 19:15No data—
Mon 12 Oct— 19:19No data—
Thu 8 Oct— 19:150 min—
Tue 6 Oct— 19:190 min—
Mon 5 Oct— 18:590 min—