Train NS 721 Schiphol Airport – Groningen

Schiphol Airport 07:00 → Groningen 09:12 Mon, Tue, Wed, Thu, Fri, Sat 2 h 12 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Assen at 09:29 No data

  1. Schiphol Airport07:00
  2. Amsterdam Zuid07:07
  3. Almere Centrum07:31
  4. Lelystad Centrum07:46
  5. Zwolle08:14
  6. Assen08:55
  7. Groningen09:12

Next service: tomorrow 07:00 from Schiphol Airport · Fri 6 Nov

Next departure 07:00 tomorrow · Schiphol Airport
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 13 full · 11 partial · 2 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 13 full · 12 partial · 51 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 Groningen, 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 4 Nov Max en route +12 min · last fix heading to Assen +11 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Assen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
07:00on time on time
07:07 / 07:11≈ on time ≈ on time
07:31 / 07:33≈ on time ≈ on time
07:46 / 07:48≈ on time ≈ on time
08:14 / 08:16≈ on time ≈ on time
08:55≈ on time ≈ on time
09:12on 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
Thu 5 NovAssen 09:29No data—
Wed 4 NovAssen 09:34Partial coverage+11 min+12 min
Tue 3 NovAssen 09:090 min—
Mon 2 NovAssen 09:14Partial coverage0 min—
Sat 31 OctAssen 09:130 min—
Fri 30 OctAssen 09:110 min—
Thu 29 OctAssen 09:13Partial coverage0 min—
Wed 28 OctAssen 09:13Partial coverage+3 min+3 min
Tue 27 OctAssen 09:14Partial coverage0 min—
Mon 26 OctSchiphol Airport 09:13No data—
Sat 24 OctAssen 09:20+4 min+4 min
Fri 23 OctAssen 09:130 min—
Thu 22 OctAssen 09:14Partial coverage0 min—
Wed 21 OctAssen 09:10Partial coverage0 min—
Tue 20 OctAssen 09:140 min—
Mon 19 OctAssen 09:180 min—
Sat 17 OctSchiphol Airport 09:100 min+2 min
Fri 16 OctAssen 09:130 min+11 min
Thu 15 OctAssen 10:580 min—
Wed 14 OctAssen 09:13Partial coverage0 min—
Tue 13 OctAssen 09:16Partial coverage0 min—
Mon 12 OctAssen 09:140 min—
Sat 10 OctAssen 09:130 min—
Fri 9 OctAssen 09:090 min—
Thu 8 OctAssen 09:13Partial coverage0 min—
Wed 7 OctSchiphol Airport 09:14Partial coverage0 min—
Tue 6 OctAssen 09:14Partial coverage+1 min+1 min
Mon 5 OctAssen 09:10No data—
Sat 3 OctAssen 09:09No data—
Fri 2 OctAssen 09:10No data—