Train NS 773 Schiphol Airport – Groningen

Schiphol Airport 19:59 → Groningen 22:12 Daily 2 h 13 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +24 min

Next service: today 19:59 from Schiphol Airport · Thu 5 Nov

Next departure 19:59 today · Schiphol Airport
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 13 full · 2 partial · 12 no data
On-time · 90 days
76%
13/17 runs under 3 min
RT coverage: 15 full · 2 partial · 36 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +11 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 +24 min · last fix heading to — +24 min
  • Fri 23 Oct Max en route +15 min · last fix heading to — +15 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 13
  • 3–10 min 12% · 2
  • 10–30 min 12% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 0% T n=1
  • 50% W n=2
  • 67% T n=3
  • 67% F n=3
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
19:59on time on time
20:06 / 20:11≈ on time ≈ +1 min
20:31 / 20:33≈ on time ≈ +3 min
20:46 / 20:48≈ on time ≈ +4 min
21:14 / 21:16≈ +1 min ≈ +6 min
21:55≈ +1 min ≈ +9 min
22:12+1 min +11 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 4 Nov— 22:44+24 min+24 min
Sun 1 NovAssen 22:14+1 min—
Sat 31 OctAssen 22:13Partial coverage0 min—
Fri 30 Oct— 22:13No data—
Thu 29 Oct— 22:17+4 min+4 min
Wed 28 Oct— 22:14No data—
Tue 27 Oct— 22:14No data—
Mon 26 Oct— 22:130 min—
Sun 25 OctAssen 22:18No data—
Sat 24 OctAssen 22:19No data—
Fri 23 Oct— 22:40+15 min+15 min
Thu 22 Oct— 22:14No data—
Wed 21 Oct— 22:13No data—
Tue 20 Oct— 22:13No data—
Mon 19 Oct— 22:45No data—
Sun 18 OctAssen 22:18+2 min+2 min
Sat 17 OctAssen 22:13No data—
Fri 16 Oct— 22:15+1 min+1 min
Thu 15 Oct— 22:470 min—
Wed 14 Oct— 22:13No data—
Tue 13 Oct— 22:14No data—
Mon 12 Oct— 22:130 min—
Sun 11 OctAssen 22:20+2 min+3 min
Sat 10 OctAssen 22:09Partial coverage0 min—
Fri 9 Oct— 22:140 min+1 min
Thu 8 Oct— 22:14+1 min—
Wed 7 Oct— 22:14+1 min+2 min
Tue 6 Oct— 22:20+4 min+4 min
Mon 5 Oct— 22:130 min—
Sun 4 OctAssen 22:09No data—