Train NS 3531 Delft Campus – Venlo

Delft Campus 08:33 → Venlo 11:28 Daily 2 h 55 min · 16 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 08:33 from Delft Campus · Sun 8 Nov

Next departure 08:33 today · Delft Campus
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 16 full · 1 partial · 12 no data
On-time · 90 days
81%
17/21 runs under 3 min
RT coverage: 20 full · 1 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +3 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 +16 min · last fix heading to Horst-Sevenum +15 min
  • Sun 1 Nov Max en route +9 min · last fix heading to 's-Hertogenbosch +8 min
  • Thu 8 Oct Max en route +9 min · last fix heading to Blerick +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Blerick +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 17
  • 3–10 min 14% · 3
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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:33on time on time
08:36≈ on time ≈ on time
08:44 / 08:46≈ on time ≈ on time
08:48 / 08:49≈ on time ≈ on time
08:58 / 09:00≈ on time ≈ +1 min
09:15 / 09:16≈ on time ≈ +1 min
09:23 / 09:26≈ on time ≈ +1 min
09:31 / 09:32≈ on time ≈ +2 min
09:48 / 09:54≈ on time ≈ +2 min
10:21 / 10:24≈ on time ≈ +3 min
10:44 / 10:49≈ on time ≈ +4 min
10:58 / 10:59≈ on time ≈ +4 min
11:06≈ on time ≈ +5 min
11:17≈ on time ≈ +5 min
11:25≈ on time ≈ +5 min
11:28on time +5 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 7 NovBlerick 11:39Partial coverage0 min—
Fri 6 NovBlerick 11:39No data—
Thu 5 NovBlerick 11:39No data—
Wed 4 NovBlerick 11:390 min—
Tue 3 NovBlerick 11:40No data—
Mon 2 NovBlerick 11:39No data—
Sun 1 Nov's-Hertogenbosch 11:02+8 min+9 min
Sat 31 Oct's-Hertogenbosch 10:450 min—
Fri 30 OctHelmond 't Hout 11:140 min—
Thu 29 OctBlerick 11:39No data—
Wed 28 OctBlerick 11:390 min—
Tue 27 OctBlerick 11:460 min—
Mon 26 OctBlerick 11:39No data—
Sun 25 OctBlerick 11:40No data—
Sat 24 OctBlerick 11:390 min—
Fri 23 OctBlerick 11:39No data—
Thu 22 OctBlerick 11:460 min—
Wed 21 OctBlerick 12:24No data—
Tue 20 OctBlerick 11:390 min—
Mon 19 OctBlerick 11:520 min—
Sun 18 OctHorst-Sevenum 12:00+15 min+16 min
Sat 17 OctBlerick 11:390 min—
Fri 16 OctBlerick 11:390 min—
Thu 15 OctBlerick 11:39No data—
Wed 14 OctBlerick 11:39No data—
Tue 13 OctBlerick 11:41No data—
Mon 12 OctBlerick 11:410 min—
Sun 11 OctBlerick 11:390 min—
Sat 10 OctBlerick 11:390 min—
Fri 9 OctBlerick 11:42+3 min+3 min