Train NS 3513 Eindhoven Centraal – Venlo

Eindhoven Centraal 06:20 → Venlo 06:58 Mon, Tue, Wed, Thu, Fri 0 h 38 min · 6 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:20 from Eindhoven Centraal · Mon 9 Nov

Next departure 06:20 Monday · Eindhoven Centraal
On-time · 30 days
63%
12/19 runs under 3 min
RT coverage: 18 full · 1 partial · 2 no data
On-time · 90 days
68%
15/22 runs under 3 min
RT coverage: 21 full · 1 partial · 38 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +10 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

  • Thu 29 Oct Max en route +15 min · last fix heading to Blerick +15 min
  • Wed 4 Nov Max en route +13 min · last fix heading to Horst-Sevenum +13 min
  • Fri 23 Oct Max en route +9 min · last fix heading to Blerick +9 min
  • Wed 28 Oct Max en route +9 min · last fix heading to Blerick +8 min
  • Fri 30 Oct Max en route +12 min · last fix heading to Helmond 't Hout +7 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 68% · 15
  • 3–10 min 23% · 5
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 40% W n=5
  • 60% T n=5
  • 50% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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