Train NS 3262 Arnhem Centraal – Schiphol Airport

Arnhem Centraal 17:51 → Schiphol Airport 19:07 Mon, Tue, Wed, Thu 1 h 16 min · 7 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 12 November 0 min

Next service: Monday 17:51 from Arnhem Centraal · Mon 16 Nov

Next departure 17:51 Monday · Arnhem Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 5 full · 7 partial · 5 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 5 full · 11 partial · 33 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: +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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=3
  • 100% T n=5
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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
17:51on time on time
18:01≈ on time ≈ on time
18:07≈ on time ≈ on time
18:26 / 18:31≈ on time ≈ +1 min
18:48≈ on time ≈ +1 min
18:54 / 19:00≈ on time ≈ +1 min
19:07on 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
Thu 12 NovVeenendaal-De Klomp 19:08Partial coverage0 min—
Wed 11 NovVeenendaal-De Klomp 19:09Partial coverage0 min—
Tue 10 NovVeenendaal-De Klomp 19:12Partial coverage+2 min+2 min
Mon 9 NovVeenendaal-De Klomp 19:09Partial coverage0 min—
Thu 5 NovVeenendaal-De Klomp 19:33No data—
Wed 4 NovVeenendaal-De Klomp 19:09No data—
Tue 3 NovVeenendaal-De Klomp 19:09No data—
Mon 2 NovArnhem Centraal 19:08Partial coverage0 min—
Thu 29 OctEde-Wageningen 19:09+2 min+3 min
Wed 28 OctVeenendaal-De Klomp 18:550 min—
Tue 27 OctEde-Wageningen 19:09No data—
Mon 26 OctVeenendaal-De Klomp 19:080 min—
Thu 22 OctUtrecht Centraal 18:460 min—
Wed 21 OctUtrecht Centraal 19:09No data—
Tue 20 OctUtrecht Centraal 19:350 min—
Mon 19 OctUtrecht Centraal 19:09Partial coverage0 min—
Thu 15 OctArnhem Centraal 19:17Partial coverage0 min—
Wed 14 OctAmsterdam Zuid 19:09No data—
Tue 13 OctUtrecht Centraal 19:09No data—
Mon 12 OctUtrecht Centraal 19:09Partial coverage0 min—
Thu 8 OctEde-Wageningen 19:09Partial coverage0 min—
Wed 7 OctVeenendaal-De Klomp 19:08Partial coverage0 min—
Tue 6 OctEde-Wageningen 19:09Partial coverage+1 min—
Thu 1 OctEde-Wageningen 18:15No data—
Wed 30 SeptVeenendaal-De Klomp 18:18No data—
Tue 29 SeptVeenendaal-De Klomp 18:21No data—
Mon 28 SeptEde-Wageningen 18:15No data—
Thu 24 SeptArnhem Centraal 18:06No data—
Wed 23 SeptVeenendaal-De Klomp 18:21No data—
Tue 22 SeptEde-Wageningen 18:15No data—