Train NS 3526 Venlo – Delft Campus

Venlo 07:33 → Delft Campus 10:25 Daily 2 h 52 min · 16 stops NS (Nederlandse Spoorwegen)

Running now · updated 10:27

Heading to Delft Campus +2 min

Estimated arrival at Delft Campus 10:27 10:25 · 1 km/h

  1. Venlo07:33
  2. Deurne07:54
  3. Eindhoven Centraal08:11
  4. Amsterdam Bijlmer ArenA09:28
  5. Schiphol Airport09:43
  6. Den Haag HS10:14
  7. Delft Campus10:25

Today it is running worse than usual: typical arrival delay is 0 min; 95% of the last 21 runs arrived on time.

On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 9 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Delft Campus, 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 +5 min · last fix heading to 's-Hertogenbosch +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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 10Today
07:33on time on time
07:36≈ on time ≈ on time
07:43≈ on time ≈ on time
07:54≈ on time ≈ on time
08:01≈ on time ≈ on time
08:11 / 08:16≈ on time ≈ on time
08:36 / 08:40≈ on time ≈ +1 min
09:06 / 09:11≈ on time ≈ +1 min
09:28≈ on time ≈ +1 min
09:34 / 09:37≈ on time ≈ +1 min
09:43 / 09:44≈ on time ≈ +1 min
10:00 / 10:02≈ on time ≈ +2 min
10:10 / 10:11≈ on time ≈ +2 min
10:14 / 10:15≈ on time ≈ +2 min
10:22≈ on time ≈ +2 min
10:25on time +2 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 NovDelft 10:24Partial coverage+2 min+5 min
Fri 6 NovRotterdam Blaak 10:57No data—
Thu 5 NovRotterdam Blaak 10:590 min—
Wed 4 NovRotterdam Blaak 10:59+1 min+1 min
Tue 3 NovRotterdam Blaak 10:59No data—
Mon 2 NovRotterdam Blaak 11:08No data—
Sun 1 Nov's-Hertogenbosch 09:010 min—
Sat 31 OctRotterdam Blaak 10:55+1 min—
Fri 30 OctRotterdam Blaak 10:580 min—
Thu 29 OctRotterdam Blaak 11:000 min—
Wed 28 OctRotterdam Blaak 10:590 min—
Tue 27 OctRotterdam Blaak 10:590 min—
Mon 26 OctRotterdam Blaak 11:010 min—
Sun 25 Oct's-Hertogenbosch 10:31No data—
Sat 24 OctRotterdam Blaak 10:560 min—
Fri 23 OctRotterdam Blaak 10:570 min—
Thu 22 OctRotterdam Blaak 10:590 min—
Wed 21 OctRotterdam Blaak 11:01No data—
Tue 20 OctRotterdam Blaak 10:59No data—
Mon 19 OctRotterdam Blaak 10:590 min—
Sun 18 Oct's-Hertogenbosch 11:03+5 min+5 min
Sat 17 OctRotterdam Blaak 10:55+2 min+2 min
Fri 16 OctRotterdam Blaak 10:550 min—
Thu 15 OctRotterdam Blaak 10:59No data—
Wed 14 OctRotterdam Blaak 11:15No data—
Tue 13 OctRotterdam Blaak 10:59No data—
Mon 12 OctRotterdam Blaak 11:040 min—
Sun 11 Oct's-Hertogenbosch 09:080 min—
Sat 10 OctRotterdam Blaak 10:570 min+1 min
Fri 9 OctRotterdam Blaak 10:550 min—