Train NS 3555 Dordrecht – Venlo

Dordrecht 14:09 → Venlo 17:28 Daily 3 h 19 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 14:09 from Dordrecht · Mon 16 Nov

Next departure 14:09 today · Dordrecht
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 19 full · 5 partial · 5 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 25 full · 8 partial · 55 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: +3 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 1 Nov Max en route +12 min · last fix heading to 's-Hertogenbosch +11 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Blerick +5 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Blerick +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 30
  • 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=4
  • 80% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=4
  • 60% S n=5

Stops and timetable

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

Last 90 days, 33 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
14:09on time on time
14:20≈ on time ≈ on time
14:23 / 14:26≈ on time ≈ on time
14:31≈ on time ≈ on time
14:38≈ on time ≈ on time
14:45 / 14:47≈ on time ≈ on time
14:50≈ on time ≈ on time
14:59 / 15:00≈ on time ≈ +1 min
15:15 / 15:16≈ on time ≈ +1 min
15:23 / 15:26≈ on time ≈ +1 min
15:31 / 15:32≈ on time ≈ +1 min
15:48 / 15:54≈ on time ≈ +1 min
16:21 / 16:24≈ on time ≈ +1 min
16:44 / 16:49≈ on time ≈ +2 min
16:58 / 16:59≈ on time ≈ +2 min
17:06≈ on time ≈ +2 min
17:17≈ on time ≈ +2 min
17:25≈ on time ≈ +2 min
17: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
Sun 15 NovBlerick 17:42Partial coverage+3 min+4 min
Sat 14 NovBlerick 17:39Partial coverage+2 min+2 min
Fri 13 NovBlerick 17:39Partial coverage+2 min+2 min
Thu 12 NovBlerick 17:39+1 min+2 min
Wed 11 NovBlerick 17:39+5 min+5 min
Tue 10 NovBlerick 17:390 min—
Mon 9 NovBlerick 17:390 min—
Sun 8 NovBlerick 17:39+1 min—
Sat 7 NovBlerick 17:42+1 min+1 min
Fri 6 NovBlerick 17:39Partial coverage+1 min+1 min
Thu 5 NovBlerick 17:390 min—
Wed 4 NovBlerick 17:390 min—
Tue 3 NovBlerick 17:39No data—
Mon 2 NovBlerick 17:390 min—
Sun 1 Nov's-Hertogenbosch 17:08+11 min+12 min
Sat 31 Oct's-Hertogenbosch 16:460 min+2 min
Fri 30 OctHelmond 't Hout 17:14No data—
Thu 29 OctBlerick 17:330 min—
Wed 28 OctBlerick 17:390 min—
Tue 27 OctBlerick 17:550 min—
Mon 26 OctBlerick 17:39No data—
Sun 25 OctBlerick 17:43No data—
Sat 24 OctBlerick 17:390 min—
Fri 23 OctBlerick 17:430 min—
Thu 22 OctBlerick 17:390 min—
Wed 21 OctBlerick 17:39No data—
Tue 20 OctBlerick 17:400 min—
Mon 19 OctBlerick 17:420 min—
Sun 18 OctBlerick 17:40Partial coverage+1 min—
Sat 17 OctBlerick 17:39No data—