Train NS 3534 Venlo – Dordrecht

Venlo 09:33 → Dordrecht 12:57 Daily 3 h 24 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 09:33 from Venlo · Fri 6 Nov

Next departure 09:33 today · Venlo
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 14 full · 6 partial · 9 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 15 full · 8 partial · 65 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

Worst days

  • Sat 10 Oct Max en route +6 min · last fix heading to Rotterdam Blaak +5 min

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 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=4
  • 75% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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
09:33on time on time
09:36≈ on time ≈ on time
09:43≈ on time ≈ on time
09:54≈ on time ≈ on time
10:01≈ on time ≈ on time
10:11 / 10:16≈ on time ≈ on time
10:36 / 10:39≈ on time ≈ on time
11:05 / 11:11≈ on time ≈ on time
11:28≈ on time ≈ on time
11:34 / 11:37≈ on time ≈ on time
11:43 / 11:46≈ on time ≈ on time
12:02 / 12:04≈ on time ≈ on time
12:13 / 12:14≈ on time ≈ on time
12:16 / 12:18≈ on time ≈ on time
12:24≈ on time ≈ on time
12:32≈ on time ≈ on time
12:37 / 12:42≈ on time ≈ on time
12:45≈ on time ≈ on time
12: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 13:04No data—
Wed 4 NovRotterdam Blaak 12:59Partial coverage0 min—
Tue 3 NovRotterdam Blaak 12:59No data—
Mon 2 NovRotterdam Blaak 12:590 min—
Sun 1 NovUtrecht Centraal 11:240 min—
Sat 31 OctRotterdam Blaak 12:550 min—
Fri 30 OctRotterdam Blaak 12:550 min—
Thu 29 OctRotterdam Blaak 12:59Partial coverage0 min—
Wed 28 OctRotterdam Blaak 12:59Partial coverage0 min—
Tue 27 OctRotterdam Blaak 13:00Partial coverage0 min—
Mon 26 OctRotterdam Blaak 12:59No data—
Sun 25 OctRotterdam Blaak 12:55No data—
Sat 24 OctRotterdam Blaak 12:56+1 min—
Fri 23 OctRotterdam Blaak 12:550 min—
Thu 22 OctRotterdam Blaak 12:59No data—
Wed 21 OctRotterdam Blaak 12:59No data—
Tue 20 OctRotterdam Blaak 12:590 min—
Mon 19 OctRotterdam Blaak 12:59Partial coverage0 min—
Sun 18 OctRotterdam Blaak 12:550 min—
Sat 17 OctRotterdam Blaak 12:540 min—
Fri 16 OctRotterdam Blaak 12:550 min—
Thu 15 OctRotterdam Blaak 13:01No data—
Wed 14 OctRotterdam Blaak 12:59No data—
Tue 13 OctRotterdam Blaak 12:59No data—
Mon 12 OctRotterdam Blaak 13:010 min—
Sun 11 OctRotterdam Blaak 12:560 min+1 min
Sat 10 OctRotterdam Blaak 12:55+5 min+6 min
Fri 9 OctRotterdam Blaak 12:550 min—
Thu 8 OctRotterdam Blaak 12:59Partial coverage0 min—
Wed 7 OctRotterdam Blaak 13:10Partial coverage0 min—