Train NS 3577 Dordrecht – Venlo

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

It has not run yet today

Last recorded run: Saturday 14 November +1 min

Next service: today 19:39 from Dordrecht · Sun 15 Nov

Next departure 19:39 today · Dordrecht
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 18 full · 1 partial · 9 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 27 full · 1 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 13 Nov Max en route +16 min · last fix heading to — +16 min
  • Wed 11 Nov Max en route +6 min · last fix heading to — +6 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min
  • Mon 12 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 24
  • 3–10 min 11% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 67% W n=3
  • 100% T n=3
  • 60% F n=5
  • 100% S n=6
  • 100% S n=3

Stops and timetable

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

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