Train NS 3580 Venlo – Schiphol Airport

Venlo 21:03 → Schiphol Airport 23:13 Daily 2 h 10 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 21:03 from Venlo · Sat 7 Nov

Full trip card
Next departure 21:03 today · Venlo
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 15 full · 3 partial · 11 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 19 full · 3 partial · 27 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 Schiphol Airport, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 7 Oct Max en route +5 min · last fix heading to — +4 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 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 67% W n=3
  • 100% T n=5
  • 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 (11 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
Venlo
21:03on time on time
Blerick
21:06≈ on time ≈ on time
Horst-Sevenum
21:13≈ on time ≈ on time
Deurne
21:24≈ on time ≈ on time
Helmond
21:31≈ on time ≈ on time
Eindhoven Centraal
21:41 / 21:46≈ on time ≈ +1 min
's-Hertogenbosch
22:06 / 22:10≈ on time ≈ +1 min
Utrecht Centraal
22:36 / 22:41≈ on time ≈ +1 min
Amsterdam Bijlmer ArenA
22:58≈ on time ≈ +2 min
Amsterdam Zuid
23:04 / 23:07≈ on time ≈ +2 min
Schiphol Airport
23:13on 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
Fri 6 Nov— 23:140 min—
Thu 5 Nov— 23:190 min—
Wed 4 Nov— 21:440 min—
Tue 3 Nov— 23:15No data—
Mon 2 Nov— 23:140 min—
Sun 1 NovAmsterdam Zuid 23:22+2 min+5 min
Sat 31 OctAmsterdam Zuid 23:21No data—
Fri 30 Oct— 23:19No data—
Thu 29 Oct— 23:140 min—
Wed 28 Oct— 23:14No data—
Tue 27 Oct— 23:19No data—
Mon 26 Oct— 21:59No data—
Sun 25 OctAmsterdam Zuid 23:21No data—
Sat 24 Oct's-Hertogenbosch 23:140 min—
Fri 23 Oct— 23:17+2 min+2 min
Thu 22 Oct— 23:180 min—
Wed 21 Oct— 23:23No data—
Tue 20 Oct— 23:15No data—
Mon 19 Oct— 23:23No data—
Sun 18 OctAmsterdam Zuid 23:21Partial coverage0 min—
Sat 17 OctAmsterdam Zuid 23:21Partial coverage0 min—
Fri 16 Oct— 23:18+2 min+2 min
Thu 15 Oct— 23:170 min—
Wed 14 Oct— 23:140 min—
Tue 13 Oct— 23:14No data—
Mon 12 Oct— 23:150 min—
Sun 11 OctAmsterdam Zuid 23:22+2 min+2 min
Sat 10 OctEindhoven Centraal 23:15Partial coverage+1 min+1 min
Fri 9 Oct— 23:14+1 min—
Thu 8 Oct— 21:45+3 min+3 min