Train NS 3557 Delft Campus – Venlo

Delft Campus 15:03 → Venlo 17:58 Daily 2 h 55 min · 16 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Blerick at 18:09 0 min

  1. Delft Campus15:03
  2. Den Haag Laan v NOI15:18
  3. Schiphol Airport15:45
  4. Utrecht Centraal16:18
  5. Eindhoven Centraal17:14
  6. Blerick17:55
  7. Venlo17:58

Next service: tomorrow 15:03 from Delft Campus · Sun 8 Nov

Next departure 15:03 tomorrow · Delft Campus
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 18 full · 1 partial · 11 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 partial · 66 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

  • Mon 26 Oct Max en route +4 min · last fix heading to Blerick +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
15:03on time on time
15:06≈ on time ≈ on time
15:14 / 15:16≈ on time ≈ on time
15:18 / 15:19≈ on time ≈ on time
15:28 / 15:30≈ on time ≈ on time
15:45 / 15:46≈ on time ≈ on time
15:53 / 15:56≈ on time ≈ on time
16:01 / 16:02≈ on time ≈ on time
16:18 / 16:24≈ on time ≈ on time
16:51 / 16:54≈ on time ≈ on time
17:14 / 17:19≈ on time ≈ on time
17:28 / 17:29≈ on time ≈ on time
17:36≈ on time ≈ on time
17:47≈ on time ≈ +1 min
17:55≈ on time ≈ +1 min
17:58on time +1 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 18:09Partial coverage0 min—
Fri 6 NovBlerick 18:09+1 min—
Thu 5 NovBlerick 18:09No data—
Wed 4 NovBlerick 18:090 min—
Tue 3 NovBlerick 18:09No data—
Mon 2 NovBlerick 18:09No data—
Sun 1 Nov's-Hertogenbosch 17:090 min—
Sat 31 Oct's-Hertogenbosch 17:090 min—
Fri 30 OctHelmond 't Hout 17:450 min—
Thu 29 OctBlerick 18:130 min—
Wed 28 OctBlerick 18:090 min—
Tue 27 OctBlerick 18:09No data—
Mon 26 OctBlerick 18:09+4 min+4 min
Sun 25 OctBlerick 18:11No data—
Sat 24 OctBlerick 18:110 min—
Fri 23 OctBlerick 18:11No data—
Thu 22 OctBlerick 18:090 min—
Wed 21 OctBlerick 18:16No data—
Tue 20 OctBlerick 18:090 min—
Mon 19 OctBlerick 18:090 min—
Sun 18 OctBlerick 18:11+1 min+1 min
Sat 17 OctBlerick 18:13No data—
Fri 16 OctBlerick 18:090 min—
Thu 15 OctBlerick 18:090 min—
Wed 14 OctBlerick 18:12No data—
Tue 13 OctBlerick 18:06No data—
Mon 12 OctBlerick 18:090 min—
Sun 11 OctBlerick 18:090 min—
Sat 10 OctBlerick 18:12No data—
Fri 9 OctBlerick 18:090 min—