Train NS 3547 Dordrecht – Venlo

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

✓ Today’s run finished

Today, last fix heading to Blerick at 15:39 No data

  1. Dordrecht12:04
  2. Schiedam Centrum12:27
  3. Den Haag Laan v NOI12:46
  4. Amsterdam Zuid13:22
  5. 's-Hertogenbosch14:22
  6. Blerick15:25
  7. Venlo15:28

Next service: tomorrow 12:04 from Dordrecht · Sat 7 Nov

Next departure 12:04 tomorrow · Dordrecht
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 13 full · 6 partial · 11 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 14 full · 8 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 +14 min · last fix heading to Blerick +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
12:04on time on time
12:15≈ on time ≈ on time
12:18 / 12:22≈ on time ≈ on time
12:27≈ on time ≈ on time
12:34≈ on time ≈ on time
12:41 / 12:43≈ on time ≈ on time
12:46≈ on time ≈ on time
12:55 / 12:57≈ on time ≈ on time
13:14 / 13:15≈ on time ≈ on time
13:22 / 13:26≈ on time ≈ on time
13:31 / 13:32≈ on time ≈ on time
13:48 / 13:54≈ on time ≈ on time
14:22 / 14:25≈ on time ≈ on time
14:45 / 14:49≈ on time ≈ on time
14:58 / 14:59≈ on time ≈ on time
15:06≈ on time ≈ on time
15:17≈ on time ≈ on time
15:25≈ on time ≈ on time
15:28on time on time

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
Fri 6 NovBlerick 15:39No data—
Thu 5 NovBlerick 15:39Partial coverage0 min—
Wed 4 NovBlerick 15:39Partial coverage0 min—
Tue 3 NovBlerick 15:39No data—
Mon 2 NovBlerick 15:39No data—
Sun 1 Nov's-Hertogenbosch 14:400 min—
Sat 31 Oct's-Hertogenbosch 14:390 min—
Fri 30 OctHelmond 't Hout 15:170 min—
Thu 29 OctBlerick 15:39Partial coverage0 min—
Wed 28 OctBlerick 15:390 min—
Tue 27 OctBlerick 15:39No data—
Mon 26 OctBlerick 15:39No data—
Sun 25 OctBlerick 15:39No data—
Sat 24 OctBlerick 15:390 min—
Fri 23 OctBlerick 15:420 min—
Thu 22 OctBlerick 15:39No data—
Wed 21 OctBlerick 15:41No data—
Tue 20 OctBlerick 15:390 min—
Mon 19 OctBlerick 15:40Partial coverage0 min—
Sun 18 OctBlerick 15:52+14 min+14 min
Sat 17 OctBlerick 15:390 min—
Fri 16 OctBlerick 15:390 min—
Thu 15 OctBlerick 15:42No data—
Wed 14 OctBlerick 15:39No data—
Tue 13 OctBlerick 15:39No data—
Mon 12 OctBlerick 15:39Partial coverage0 min—
Sun 11 OctBlerick 16:040 min—
Sat 10 OctBlerick 15:390 min—
Fri 9 OctBlerick 15:390 min+1 min
Thu 8 OctBlerick 15:39Partial coverage0 min—