Train NS 3555 Dordrecht – Venlo

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

✓ Today’s run finished

Today, last fix heading to Blerick at 17:39 0 min

  1. Dordrecht14:04
  2. Schiedam Centrum14:27
  3. Den Haag Laan v NOI14:46
  4. Amsterdam Zuid15:22
  5. 's-Hertogenbosch16:22
  6. Blerick17:25
  7. Venlo17:28

Next service: tomorrow 14:04 from Dordrecht · Fri 6 Nov

Next departure 14:04 tomorrow · Dordrecht
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 13 full · 8 partial · 9 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 14 full · 9 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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 1 Nov Max en route +12 min · last fix heading to 's-Hertogenbosch +11 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 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • 100% S n=2
  • 67% 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
14:04on time on time
14:15≈ on time ≈ on time
14:18 / 14:22≈ on time ≈ on time
14:27≈ on time ≈ on time
14:34≈ on time ≈ on time
14:41 / 14:43≈ on time ≈ on time
14:46≈ on time ≈ on time
14:55 / 14:57≈ on time ≈ on time
15:14 / 15:15≈ on time ≈ on time
15:22 / 15:26≈ on time ≈ on time
15:31 / 15:32≈ on time ≈ on time
15:48 / 15:54≈ on time ≈ on time
16:22 / 16:25≈ on time ≈ on time
16:45 / 16:49≈ on time ≈ on time
16:58 / 16:59≈ on time ≈ +1 min
17:06≈ on time ≈ +1 min
17:17≈ on time ≈ +1 min
17:25≈ on time ≈ +1 min
17:28on time +1 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
Thu 5 NovBlerick 17:39Partial coverage0 min—
Wed 4 NovBlerick 17:39Partial coverage0 min—
Tue 3 NovBlerick 17:39No data—
Mon 2 NovBlerick 17:39Partial coverage0 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:33Partial coverage0 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:42Partial coverage0 min—
Sun 18 OctBlerick 17:40+1 min—
Sat 17 OctBlerick 17:39No data—
Fri 16 OctBlerick 17:400 min—
Thu 15 OctHorst-Sevenum 17:46No data—
Wed 14 OctBlerick 17:39Partial coverage0 min—
Tue 13 OctBlerick 17:39No data—
Mon 12 OctBlerick 17:400 min—
Sun 11 OctBlerick 17:390 min—
Sat 10 OctBlerick 17:41No data—
Fri 9 OctBlerick 17:400 min—
Thu 8 OctBlerick 17:34Partial coverage+1 min+1 min
Wed 7 OctBlerick 17:39Partial coverage0 min—