Train NS 3587 Dordrecht – Amsterdam Zuid

Dordrecht 22:09 → Amsterdam Zuid 23:23 Daily 1 h 14 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 22:09 from Dordrecht · Thu 5 Nov

Next departure 22:09 today · Dordrecht
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 15 full · 3 partial · 9 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 16 full · 3 partial · 27 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: +2 min

Last 30 days

Arrival delay at Amsterdam Zuid, 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

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

  • Early 0% · 0
  • On time 100% · 19
  • 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=1
  • 100% W n=2
  • 100% T n=2
  • 100% F n=4
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
22:09on time on time
22:20≈ on time ≈ on time
22:23 / 22:26≈ on time ≈ on time
22:31≈ on time ≈ on time
22:38≈ on time ≈ +1 min
22:45 / 22:47≈ on time ≈ +1 min
22:50≈ on time ≈ +1 min
22:59 / 23:00≈ on time ≈ +1 min
23:15 / 23:16≈ on time ≈ +1 min
23:23on 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 Nov— 23:24+1 min+1 min
Tue 3 Nov— 23:24No data—
Mon 2 Nov— 23:240 min—
Sun 1 NovSchiphol Airport 23:290 min—
Sat 31 OctSchiphol Airport 23:33Partial coverage0 min—
Fri 30 Oct— 23:250 min—
Wed 28 Oct— 23:03No data—
Tue 27 Oct— 23:23No data—
Mon 26 Oct— 23:240 min—
Sun 25 OctSchiphol Airport 23:34No data—
Sat 24 OctDelft 23:27No data—
Fri 23 Oct— 23:250 min—
Thu 22 Oct— 23:22No data—
Wed 21 Oct— 23:25No data—
Tue 20 Oct— 23:25No data—
Mon 19 Oct— 23:27No data—
Sun 18 OctSchiphol Airport 23:30Partial coverage0 min—
Sat 17 OctSchiphol Airport 23:300 min—
Fri 16 Oct— 23:28+2 min+2 min
Thu 15 Oct— 23:27+2 min+2 min
Tue 13 Oct— 23:330 min—
Mon 12 Oct— 23:240 min—
Sun 11 OctSchiphol Airport 23:30Partial coverage0 min—
Sat 10 Oct— 22:250 min—
Fri 9 Oct— 23:01+2 min+2 min
Thu 8 Oct— 23:250 min—
Wed 7 Oct— 23:240 min—
Mon 5 Oct— 22:330 min—
Sun 4 OctSchiphol Airport 23:30No data—
Sat 3 OctSchiphol Airport 23:31No data—