Train NS 3195 Den Haag Centraal – Schiphol Airport

Den Haag Centraal 00:31 → Schiphol Airport 01:02 Daily 0 h 31 min · 3 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:14 No data

  1. Den Haag Centraal00:31
  2. Leiden Centraal00:42
  3. Schiphol Airport01:02

Next service: tomorrow 00:31 from Den Haag Centraal · Sat 7 Nov

Next departure 00:31 tomorrow · Den Haag Centraal
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 23 full · 3 partial · 3 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 25 full · 3 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
00:31on time on time
00:42 / 00:47≈ on time ≈ on time
01:02on time on time

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— 01:14No data—
Thu 5 Nov— 01:040 min—
Wed 4 Nov— 01:030 min—
Tue 3 Nov— 01:030 min—
Mon 2 NovLeiden Centraal 01:04Partial coverage0 min—
Sun 1 Nov— 01:070 min—
Fri 30 Oct— 01:030 min—
Thu 29 Oct— 02:070 min—
Wed 28 Oct— 01:030 min—
Tue 27 Oct— 01:030 min—
Mon 26 OctLeiden Centraal 01:05Partial coverage0 min—
Sun 25 Oct— 01:05No data—
Sat 24 Oct— 01:050 min—
Fri 23 Oct— 01:040 min—
Thu 22 Oct— 01:040 min—
Wed 21 Oct— 01:030 min—
Tue 20 Oct— 01:060 min—
Mon 19 OctLeiden Centraal 01:040 min—
Sun 18 OctLeiden Centraal 01:04No data—
Sat 17 Oct— 01:040 min—
Fri 16 Oct— 01:030 min—
Thu 15 Oct— 01:030 min—
Wed 14 Oct— 01:040 min—
Tue 13 Oct— 01:060 min—
Mon 12 OctDen Haag Centraal 01:03Partial coverage0 min—
Sun 11 Oct— 01:050 min—
Sat 10 Oct— 01:050 min—
Fri 9 Oct— 01:060 min—
Thu 8 Oct— 01:040 min—
Wed 7 Oct— 01:04+1 min—