Train NS 3557 Dordrecht – Venlo

Dordrecht 14:34 → Venlo 17:57 Daily 3 h 23 min · 19 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Blerick at 18:08 +2 min

  1. Dordrecht14:34
  2. Schiedam Centrum14:57
  3. Den Haag Laan v NOI15:16
  4. Amsterdam Zuid15:52
  5. 's-Hertogenbosch16:52
  6. Blerick17:54
  7. Venlo17:57

Next service: tomorrow 14:34 from Dordrecht · Tue 17 Nov

Next departure 14:34 tomorrow · Dordrecht
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 31 full · 1 partial · 57 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: +4 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 15 Nov Max en route +7 min · last fix heading to Blerick +7 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Blerick +4 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Blerick +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 29
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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:34on time on time
14:45≈ on time ≈ on time
14:48 / 14:52≈ on time ≈ on time
14:57≈ on time ≈ on time
15:04≈ on time ≈ on time
15:11 / 15:13≈ on time ≈ on time
15:16≈ on time ≈ +1 min
15:25 / 15:27≈ on time ≈ +1 min
15:44 / 15:45≈ on time ≈ +1 min
15:52 / 15:56≈ on time ≈ +1 min
16:01 / 16:02≈ on time ≈ +1 min
16:18 / 16:23≈ on time ≈ +1 min
16:52 / 16:56≈ on time ≈ +2 min
17:15 / 17:19≈ on time ≈ +2 min
17:28≈ on time ≈ +2 min
17:36≈ on time ≈ +2 min
17:47≈ on time ≈ +2 min
17:54≈ on time ≈ +2 min
17: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 NovBlerick 18:08Partial coverage+2 min+2 min
Sun 15 NovBlerick 18:14+7 min+7 min
Sat 14 NovBlerick 18:090 min—
Fri 13 NovBlerick 18:09+4 min+5 min
Thu 12 NovBlerick 18:09+2 min+3 min
Wed 11 NovBlerick 18:09+1 min+2 min
Tue 10 NovBlerick 18:090 min+3 min
Mon 9 NovBlerick 18:090 min—
Sun 8 NovBlerick 18:090 min—
Sat 7 NovBlerick 18:090 min—
Fri 6 NovBlerick 18:09+1 min—
Thu 5 NovBlerick 18:09No data—
Wed 4 NovBlerick 18:090 min—
Tue 3 NovBlerick 18:09No data—
Mon 2 NovBlerick 18:09No data—
Sun 1 Nov's-Hertogenbosch 17:090 min—
Sat 31 Oct's-Hertogenbosch 17:090 min—
Fri 30 OctHelmond 't Hout 17:450 min—
Thu 29 OctBlerick 18:130 min—
Wed 28 OctBlerick 18:090 min—
Tue 27 OctBlerick 18:09No data—
Mon 26 OctBlerick 18:09+4 min+4 min
Sun 25 OctBlerick 18:11No data—
Sat 24 OctBlerick 18:110 min—
Fri 23 OctBlerick 18:11No data—
Thu 22 OctBlerick 18:090 min—
Wed 21 OctBlerick 18:16No data—
Tue 20 OctBlerick 18:090 min—
Mon 19 OctBlerick 18:090 min—
Sun 18 OctBlerick 18:11+1 min+1 min