Train NS 730 Groningen – Schiphol Airport

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Zuid at 11:08 +3 min

  1. Groningen08:48
  2. Assen09:05
  3. Zwolle09:44
  4. Lelystad Centrum10:11
  5. Almere Centrum10:26
  6. Amsterdam Zuid10:48
  7. Schiphol Airport11:00

Next service: tomorrow 08:48 from Groningen · Tue 10 Nov

Next departure 08:48 tomorrow · Groningen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 6 full · 12 partial · 12 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 10 full · 16 partial · 63 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

  • Sun 11 Oct Max en route +32 min · last fix heading to Amsterdam Zuid +32 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Amsterdam Zuid +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • 100% F n=3
  • 100% S n=5
  • 75% 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 10
08:48on time on time
09:05≈ on time ≈ +1 min
09:44 / 09:46≈ on time ≈ +2 min
10:11 / 10:12≈ on time ≈ +2 min
10:26 / 10:28≈ on time ≈ +3 min
10:48 / 10:54≈ on time ≈ +4 min
11:00on time +4 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
Mon 9 NovAmsterdam Zuid 11:08Partial coverage+3 min+3 min
Sun 8 NovAmsterdam Zuid 11:08Partial coverage0 min—
Sat 7 NovAmsterdam Zuid 11:08Partial coverage+1 min+1 min
Fri 6 NovAmsterdam Zuid 11:08No data—
Thu 5 NovAmsterdam Zuid 11:08No data—
Wed 4 NovAmsterdam Zuid 11:08Partial coverage+2 min+2 min
Tue 3 NovAmsterdam Zuid 11:08No data—
Mon 2 NovAmsterdam Zuid 11:08No data—
Sun 1 NovLeiden Centraal 11:33+1 min+1 min
Sat 31 OctAmsterdam Zuid 11:08Partial coverage+1 min—
Fri 30 OctAmsterdam Zuid 11:08No data—
Thu 29 OctAmsterdam Zuid 11:080 min—
Wed 28 OctAmsterdam Zuid 11:20Partial coverage0 min—
Tue 27 OctAmsterdam Zuid 11:08Partial coverage0 min—
Mon 26 OctAmsterdam Zuid 11:08Partial coverage0 min—
Sun 25 OctAmsterdam Zuid 11:08No data—
Sat 24 OctAmsterdam Zuid 11:080 min—
Fri 23 OctAmsterdam Zuid 11:18No data—
Thu 22 OctAmsterdam Zuid 11:08No data—
Wed 21 OctAmsterdam Zuid 11:11No data—
Tue 20 OctAmsterdam Zuid 11:09Partial coverage0 min—
Mon 19 OctAmsterdam Zuid 11:08Partial coverage0 min—
Sun 18 OctAmsterdam Zuid 11:080 min—
Sat 17 OctAmsterdam Zuid 11:080 min—
Fri 16 OctAmsterdam Zuid 11:08No data—
Thu 15 OctAmsterdam Zuid 11:08No data—
Wed 14 OctAmsterdam Zuid 11:08Partial coverage0 min—
Tue 13 OctAmsterdam Zuid 11:08No data—
Mon 12 OctAmsterdam Zuid 11:22Partial coverage0 min—
Sun 11 OctAmsterdam Zuid 12:04+32 min+32 min