Train NS 3553 Dordrecht – Venlo

Dordrecht 13:39 → Venlo 16:58 Daily 3 h 19 min · 19 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Dordrecht13:39
  2. Schiedam Centrum14:01
  3. Den Haag Laan v NOI14:20
  4. Amsterdam Zuid14:53
  5. 's-Hertogenbosch15:51
  6. Blerick16:55
  7. Venlo16:58

Next service: tomorrow 13:39 from Dordrecht · Sun 8 Nov

Next departure 13:39 tomorrow · Dordrecht
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 12 full · 4 partial · 14 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 16 full · 4 partial · 69 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

  • Tue 6 Oct Max en route +30 min · last fix heading to Blerick +30 min
  • Fri 6 Nov Max en route +5 min · last fix heading to Blerick +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:39on time on time
13:50≈ on time ≈ on time
13:53 / 13:56≈ on time ≈ on time
14:01≈ on time ≈ on time
14:08≈ on time ≈ on time
14:15 / 14:17≈ on time ≈ on time
14:20≈ on time ≈ on time
14:29 / 14:30≈ on time ≈ on time
14:45 / 14:46≈ on time ≈ on time
14:53 / 14:56≈ on time ≈ on time
15:01 / 15:02≈ on time ≈ on time
15:18 / 15:24≈ on time ≈ on time
15:51 / 15:54≈ on time ≈ on time
16:14 / 16:19≈ on time ≈ on time
16:28 / 16:29≈ on time ≈ on time
16:36≈ on time ≈ on time
16:47≈ on time ≈ on time
16:55≈ on time ≈ on time
16:58on 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
Sat 7 NovBlerick 17:090 min—
Fri 6 NovBlerick 17:14Partial coverage+5 min+5 min
Thu 5 NovBlerick 17:09No data—
Wed 4 NovBlerick 17:090 min—
Tue 3 NovBlerick 17:09No data—
Mon 2 NovBlerick 17:090 min—
Sun 1 Nov's-Hertogenbosch 16:160 min—
Sat 31 Oct's-Hertogenbosch 16:150 min—
Fri 30 OctHelmond 't Hout 16:440 min—
Thu 29 OctBlerick 17:090 min—
Wed 28 OctBlerick 17:090 min—
Tue 27 OctBlerick 17:100 min—
Mon 26 OctBlerick 17:10No data—
Sun 25 OctBlerick 17:12No data—
Sat 24 OctBlerick 17:090 min—
Fri 23 OctBlerick 17:13No data—
Thu 22 OctBlerick 17:09No data—
Wed 21 OctBlerick 17:15No data—
Tue 20 OctBlerick 17:10No data—
Mon 19 OctBlerick 17:150 min—
Sun 18 OctBlerick 17:10Partial coverage+1 min+2 min
Sat 17 OctBlerick 17:09No data—
Fri 16 OctBlerick 17:09No data—
Thu 15 OctBlerick 17:09No data—
Wed 14 OctBlerick 17:09No data—
Tue 13 OctBlerick 17:10No data—
Mon 12 OctBlerick 17:12+1 min—
Sun 11 OctBlerick 17:09Partial coverage0 min—
Sat 10 OctBlerick 17:10Partial coverageNo data—
Fri 9 OctBlerick 17:09Partial coverage0 min—