Train NS 3540 Venlo – Dordrecht

Venlo 11:03 → Dordrecht 14:23 Daily 3 h 20 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +15 min

Next service: today 11:03 from Venlo · Mon 16 Nov

Next departure 11:03 today · Venlo
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 18 full · 2 partial · 9 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 29 full · 2 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +7 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 15 Nov Max en route +16 min · last fix heading to Rotterdam Blaak +15 min
  • Sun 18 Oct Max en route +10 min · last fix heading to Rotterdam Blaak +9 min
  • Thu 12 Nov Max en route +6 min · last fix heading to Rotterdam Blaak +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
11:03on time on time
11:06≈ on time ≈ on time
11:13≈ on time ≈ on time
11:24≈ on time ≈ on time
11:31≈ on time ≈ on time
11:41 / 11:46≈ on time ≈ +1 min
12:06 / 12:10≈ on time ≈ +1 min
12:36 / 12:41≈ on time ≈ +2 min
12:58≈ on time ≈ +2 min
13:04 / 13:07≈ on time ≈ +2 min
13:13 / 13:14≈ on time ≈ +2 min
13:30 / 13:32≈ on time ≈ +2 min
13:40 / 13:41≈ on time ≈ +2 min
13:44 / 13:45≈ on time ≈ +2 min
13:52≈ on time ≈ +2 min
14:00≈ on time ≈ +2 min
14:04 / 14:07≈ on time ≈ +2 min
14:10≈ on time ≈ +2 min
14:23on time +3 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
Sun 15 NovRotterdam Blaak 14:25Partial coverage+15 min+16 min
Sat 14 NovRotterdam Blaak 14:24Partial coverage0 min—
Fri 13 NovRotterdam Blaak 14:240 min—
Thu 12 NovRotterdam Blaak 14:34+6 min+6 min
Wed 11 NovRotterdam Blaak 14:290 min—
Tue 10 NovRotterdam Blaak 14:29+1 min—
Mon 9 NovRotterdam Blaak 14:33+3 min+4 min
Sun 8 NovDelft 14:040 min+2 min
Sat 7 NovDelft 14:040 min—
Fri 6 NovRotterdam Blaak 14:24No data—
Thu 5 NovRotterdam Blaak 14:29No data—
Wed 4 NovRotterdam Blaak 14:29+1 min+1 min
Tue 3 NovRotterdam Blaak 14:29No data—
Mon 2 NovRotterdam Blaak 14:29No data—
Sun 1 NovUtrecht Centraal 12:580 min+2 min
Sat 31 OctRotterdam Blaak 14:250 min—
Fri 30 OctRotterdam Blaak 14:250 min—
Thu 29 OctRotterdam Blaak 14:300 min—
Wed 28 OctRotterdam Blaak 14:300 min—
Tue 27 OctRotterdam Blaak 14:41No data—
Mon 26 OctRotterdam Blaak 14:300 min—
Sun 25 OctRotterdam Blaak 14:26No data—
Sat 24 OctRotterdam Blaak 14:29+2 min+3 min
Fri 23 OctRotterdam Blaak 14:25No data—
Thu 22 OctRotterdam Blaak 14:29No data—
Wed 21 OctRotterdam Blaak 14:31No data—
Tue 20 OctRotterdam Blaak 14:310 min—
Mon 19 OctRotterdam Blaak 14:300 min—
Sun 18 OctRotterdam Blaak 14:43+9 min+10 min
Sat 17 OctRotterdam Blaak 14:250 min—