Train NS 3538 Venlo – Dordrecht

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 10:33 from Venlo · Tue 17 Nov

Next departure 10:33 today · Venlo
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 14 full · 9 partial · 6 no data
On-time · 90 days
94%
32/34 runs under 3 min
RT coverage: 20 full · 14 partial · 54 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 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

  • Sun 18 Oct Max en route +11 min · last fix heading to Rotterdam Blaak +11 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Rotterdam Blaak +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 32
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=5
  • 100% T n=5
  • 75% F n=4
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 34 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
10:33on time on time
10:36≈ on time ≈ on time
10:43≈ on time ≈ on time
10:54≈ on time ≈ on time
11:01≈ on time ≈ on time
11:11 / 11:16≈ on time ≈ on time
11:36 / 11:39≈ on time ≈ +1 min
12:05 / 12:11≈ on time ≈ +1 min
12:28≈ on time ≈ +1 min
12:34 / 12:37≈ on time ≈ +1 min
12:43 / 12:46≈ on time ≈ +1 min
13:02 / 13:04≈ on time ≈ +1 min
13:13 / 13:14≈ on time ≈ +1 min
13:16 / 13:18≈ on time ≈ +1 min
13:24≈ on time ≈ +2 min
13:32≈ on time ≈ +2 min
13:37 / 13:42≈ on time ≈ +2 min
13:45≈ on time ≈ +2 min
13:57on 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
Mon 16 NovRotterdam Blaak 13:59Partial coverage0 min—
Sun 15 NovRotterdam Blaak 13:540 min—
Sat 14 NovRotterdam Blaak 13:540 min—
Fri 13 NovRotterdam Blaak 13:54+4 min+4 min
Thu 12 NovRotterdam Blaak 13:59Partial coverage+2 min+2 min
Wed 11 NovRotterdam Blaak 13:59Partial coverage0 min—
Tue 10 NovRotterdam Blaak 13:59Partial coverage0 min—
Mon 9 NovRotterdam Blaak 13:59Partial coverage0 min—
Sun 8 NovDelft 13:38+2 min+4 min
Sat 7 NovDelft 13:340 min—
Fri 6 NovRotterdam Blaak 13:54No data—
Thu 5 NovRotterdam Blaak 13:59Partial coverage0 min—
Wed 4 NovRotterdam Blaak 13:59Partial coverage0 min—
Tue 3 NovBlerick 17:28No data—
Mon 2 NovRotterdam Blaak 13:59Partial coverage0 min—
Sun 1 NovUtrecht Centraal 12:32+2 min+3 min
Sat 31 OctRotterdam Blaak 13:550 min—
Fri 30 OctRotterdam Blaak 13:55No data—
Thu 29 OctRotterdam Blaak 13:590 min—
Wed 28 OctRotterdam Blaak 13:590 min—
Tue 27 OctRotterdam Blaak 13:590 min—
Mon 26 OctRotterdam Blaak 14:00No data—
Sun 25 OctRotterdam Blaak 13:56No data—
Sat 24 OctRotterdam Blaak 13:550 min—
Fri 23 OctRotterdam Blaak 13:570 min—
Thu 22 OctRotterdam Blaak 14:000 min—
Wed 21 OctRotterdam Blaak 13:59No data—
Tue 20 OctRotterdam Blaak 14:000 min—
Mon 19 OctRotterdam Blaak 14:00Partial coverage0 min—
Sun 18 OctRotterdam Blaak 14:07+11 min+11 min