Train NS 754 Groningen – Schiphol Airport

Groningen 14:48 → Schiphol Airport 17:00 Daily 2 h 12 min · 7 stops NS (Nederlandse Spoorwegen)

Running now · updated 14:40

Position estimated from the timetable

Heading to Schiphol Airport 0 min

Estimated arrival at Schiphol Airport 17:00

  1. Groningen14:48
  2. Assen15:05
  3. Zwolle15:44
  4. Lelystad Centrum16:11
  5. Almere Centrum16:26
  6. Amsterdam Zuid16:48
  7. Schiphol Airport17:00

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

On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 5 full · 13 partial · 12 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 7 full · 19 partial · 63 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 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

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

  • Early 0% · 0
  • On time 100% · 26
  • 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=4
  • 100% W n=5
  • 100% T n=2
  • 100% F n=2
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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
14:48on time on time
15:05≈ on time ≈ on time
15:44 / 15:46≈ on time ≈ +1 min
16:11 / 16:12≈ on time ≈ +1 min
16:26 / 16:28≈ on time ≈ +1 min
16:48 / 16:54≈ on time ≈ +1 min
17:00on 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
Wed 11 NovGroningen 14:39Partial coverage0 min—
Tue 10 NovAmsterdam Zuid 17:08Partial coverage+1 min+1 min
Mon 9 NovAmsterdam Zuid 17:08Partial coverage0 min—
Sun 8 NovAmsterdam Zuid 17:09Partial coverage0 min—
Sat 7 NovLelystad Centrum 16:27Partial coverage0 min—
Fri 6 NovAmsterdam Zuid 17:08Partial coverage0 min—
Thu 5 NovAmsterdam Zuid 17:08No data—
Wed 4 NovAmsterdam Zuid 17:08Partial coverage0 min—
Tue 3 NovAmsterdam Zuid 17:08No data—
Mon 2 NovAmsterdam Zuid 17:08No data—
Sun 1 NovAmsterdam Zuid 17:08Partial coverage0 min—
Sat 31 OctAmsterdam Zuid 17:08Partial coverage0 min—
Fri 30 OctAmsterdam Zuid 17:08No data—
Thu 29 OctAmsterdam Zuid 17:08Partial coverage0 min—
Wed 28 OctAmsterdam Zuid 17:080 min—
Tue 27 OctAmsterdam Zuid 17:37No data—
Mon 26 OctAmsterdam Zuid 17:08Partial coverage0 min—
Sun 25 OctAmsterdam Zuid 17:08No data—
Sat 24 OctAmsterdam Zuid 17:09+1 min—
Fri 23 OctAmsterdam Zuid 17:08No data—
Thu 22 OctAmsterdam Zuid 17:08No data—
Wed 21 OctAmsterdam Zuid 17:08No data—
Tue 20 OctAmsterdam Zuid 17:08Partial coverage0 min—
Mon 19 OctAmsterdam Zuid 17:26Partial coverage0 min—
Sun 18 OctAmsterdam Zuid 17:080 min—
Sat 17 OctAmsterdam Zuid 17:08No data—
Fri 16 OctAmsterdam Zuid 17:08No data—
Thu 15 OctAmsterdam Zuid 17:24No data—
Wed 14 OctAmsterdam Zuid 17:080 min—
Tue 13 OctAmsterdam Zuid 17:180 min—