Train NS 3514 Amsterdam Zuid – Dordrecht

Amsterdam Zuid 06:37 → Dordrecht 07:57 Mon, Tue, Wed, Thu, Fri 1 h 20 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Rotterdam Blaak at 07:59 0 min

  1. Amsterdam Zuid06:37
  2. Leiden Centraal07:02
  3. Den Haag Laan v NOI07:13
  4. Delft07:25
  5. Schiedam Centrum07:33
  6. Rotterdam Blaak07:45
  7. Dordrecht07:57

Next service: tomorrow 06:37 from Amsterdam Zuid · Fri 6 Nov

Next departure 06:37 tomorrow · Amsterdam Zuid
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 9 full · 13 partial · 0 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 9 full · 14 partial · 40 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: 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 23
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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:37on time on time
06:43 / 06:46≈ on time ≈ on time
07:02 / 07:04≈ on time ≈ on time
07:13 / 07:14≈ on time ≈ on time
07:16 / 07:18≈ on time ≈ on time
07:25≈ on time ≈ on time
07:33≈ on time ≈ on time
07:38 / 07:42≈ on time ≈ on time
07:45≈ on time ≈ on time
07:57on 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 NovRotterdam Blaak 07:59Partial coverage0 min—
Wed 4 NovRotterdam Blaak 07:59Partial coverage0 min—
Tue 3 NovRotterdam Blaak 07:59Partial coverage0 min—
Mon 2 NovRotterdam Blaak 07:590 min—
Fri 30 OctRotterdam Blaak 08:000 min—
Thu 29 OctRotterdam Blaak 07:59Partial coverage+2 min+2 min
Wed 28 OctRotterdam Blaak 07:59Partial coverage0 min—
Tue 27 OctRotterdam Blaak 07:59Partial coverage0 min—
Mon 26 OctRotterdam Blaak 07:59Partial coverage0 min—
Fri 23 OctRotterdam Blaak 07:550 min—
Thu 22 OctRotterdam Blaak 07:590 min—
Wed 21 OctRotterdam Blaak 07:590 min—
Tue 20 OctRotterdam Blaak 08:000 min—
Mon 19 OctSchiedam Centrum 08:00Partial coverage+1 min+10 min
Fri 16 OctRotterdam Blaak 07:550 min—
Thu 15 OctRotterdam Blaak 07:59Partial coverage0 min—
Wed 14 OctRotterdam Blaak 07:59Partial coverage0 min—
Tue 13 OctRotterdam Blaak 08:00Partial coverage0 min—
Mon 12 OctRotterdam Blaak 08:000 min—
Fri 9 OctRotterdam Blaak 07:550 min—
Thu 8 OctRotterdam Blaak 08:00Partial coverage0 min—
Wed 7 OctRotterdam Blaak 07:59Partial coverage0 min—
Tue 6 OctRotterdam Blaak 07:59Partial coverage0 min—
Mon 5 OctRotterdam Blaak 08:01No data—
Fri 2 OctRotterdam Blaak 07:55No data—
Thu 1 OctRotterdam Blaak 07:59No data—
Wed 30 SeptRotterdam Blaak 07:59No data—
Tue 29 SeptRotterdam Blaak 07:59No data—
Mon 28 SeptRotterdam Blaak 07:59No data—
Fri 25 SeptRotterdam Blaak 07:55No data—