Train NS 3551 Dordrecht – Venlo

Dordrecht 13:04 → Venlo 16:28 Daily 3 h 24 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 13:04 from Dordrecht · Thu 5 Nov

Next departure 13:04 today · Dordrecht
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 14 full · 5 partial · 10 no data
On-time · 90 days
86%
18/21 runs under 3 min
RT coverage: 15 full · 6 partial · 67 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: +1 min

Last 30 days

Arrival delay at Venlo, 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 +7 min · last fix heading to Blerick +6 min
  • Tue 6 Oct Max en route +6 min · last fix heading to Blerick +6 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Blerick +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 18
  • 3–10 min 14% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
13:04on time on time
13:15≈ on time ≈ on time
13:18 / 13:22≈ on time ≈ on time
13:27≈ on time ≈ on time
13:34≈ on time ≈ on time
13:41 / 13:43≈ on time ≈ on time
13:46≈ on time ≈ on time
13:55 / 13:57≈ on time ≈ +1 min
14:14 / 14:15≈ on time ≈ +1 min
14:22 / 14:26≈ on time ≈ +1 min
14:31 / 14:32≈ on time ≈ +1 min
14:48 / 14:54≈ on time ≈ +1 min
15:22 / 15:25≈ on time ≈ +1 min
15:45 / 15:49≈ on time ≈ +2 min
15:58 / 15:59≈ on time ≈ +2 min
16:06≈ on time ≈ +2 min
16:17≈ on time ≈ +2 min
16:25≈ on time ≈ +2 min
16:28on 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 NovBlerick 16:39Partial coverage+2 min+2 min
Tue 3 NovBlerick 16:39No data—
Mon 2 NovBlerick 16:44No data—
Sun 1 Nov's-Hertogenbosch 15:460 min—
Sat 31 Oct's-Hertogenbosch 15:450 min—
Fri 30 OctHelmond 't Hout 16:140 min—
Thu 29 OctBlerick 16:39Partial coverage0 min—
Wed 28 OctBlerick 16:450 min—
Tue 27 OctBlerick 16:390 min—
Mon 26 OctBlerick 16:39No data—
Sun 25 OctBlerick 16:50No data—
Sat 24 OctBlerick 16:390 min—
Fri 23 OctBlerick 16:390 min—
Thu 22 OctBlerick 16:41No data—
Wed 21 OctBlerick 16:55No data—
Tue 20 OctBlerick 16:400 min—
Mon 19 OctBlerick 16:40Partial coverage0 min—
Sun 18 OctBlerick 16:45+6 min+7 min
Sat 17 OctBlerick 16:40No data—
Fri 16 OctBlerick 16:390 min—
Thu 15 OctBlerick 16:39No data—
Wed 14 OctBlerick 16:40No data—
Tue 13 OctBlerick 16:39No data—
Mon 12 OctBlerick 16:40+1 min+1 min
Sun 11 OctBlerick 16:530 min—
Sat 10 OctBlerick 16:390 min—
Fri 9 OctBlerick 16:390 min—
Thu 8 OctBlerick 16:40Partial coverage+1 min—
Wed 7 OctBlerick 16:39Partial coverage0 min—
Tue 6 OctBlerick 16:45Partial coverage+6 min+6 min