Train NS 3521 Eindhoven Centraal – Venlo

Eindhoven Centraal 08:19 → Venlo 08:58 Daily 0 h 39 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Blerick at 09:09 +1 min

  1. Eindhoven Centraal08:19
  2. Helmond08:28
  3. Deurne08:36
  4. Horst-Sevenum08:47
  5. Blerick08:55
  6. Venlo08:58

Next service: tomorrow 08:19 from Eindhoven Centraal · Sun 8 Nov

Next departure 08:19 tomorrow · Eindhoven Centraal
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 19 full · 6 partial · 3 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 22 full · 6 partial · 57 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 18 Oct Max en route +9 min · last fix heading to Blerick +9 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Blerick +6 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 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
08:19on time on time
08:28 / 08:29≈ on time ≈ on time
08:36≈ on time ≈ on time
08:47≈ on time ≈ on time
08:55≈ on time ≈ on time
08: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 09:09Partial coverage+1 min+1 min
Fri 6 NovBlerick 09:09No data—
Thu 5 NovBlerick 09:090 min—
Wed 4 NovBlerick 09:09+1 min+1 min
Tue 3 NovBlerick 09:190 min—
Mon 2 NovBlerick 09:12No data—
Fri 30 OctHelmond 't Hout 08:470 min—
Thu 29 OctBlerick 09:120 min—
Wed 28 OctBlerick 09:090 min—
Tue 27 OctBlerick 09:090 min—
Mon 26 OctBlerick 09:100 min—
Sun 25 OctBlerick 09:14No data—
Sat 24 OctBlerick 09:09Partial coverage0 min+1 min
Fri 23 OctBlerick 09:090 min—
Thu 22 OctBlerick 09:090 min—
Wed 21 OctBlerick 09:090 min—
Tue 20 OctBlerick 09:090 min—
Mon 19 OctBlerick 09:090 min—
Sun 18 OctBlerick 09:18Partial coverage+9 min+9 min
Sat 17 OctBlerick 09:09Partial coverage0 min+1 min
Fri 16 OctBlerick 09:090 min—
Thu 15 OctBlerick 09:090 min—
Wed 14 OctBlerick 09:090 min—
Tue 13 OctBlerick 09:120 min—
Mon 12 OctBlerick 09:120 min—
Sun 11 OctBlerick 09:10Partial coverage+1 min+1 min
Sat 10 OctBlerick 09:09Partial coverage0 min—
Fri 9 OctBlerick 09:090 min—
Thu 8 OctBlerick 09:15+6 min+6 min
Wed 7 OctBlerick 09:090 min—