Train NS 790 Groningen – Schiphol Airport

Groningen 23:48 → Schiphol Airport 02:06 Daily 2 h 18 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 23:48 from Groningen · Fri 13 Nov

Next departure 23:48 today · Groningen
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 10 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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
23:48on time on time
00:05≈ on time ≈ on time
00:44 / 00:46≈ on time ≈ on time
01:11 / 01:12≈ on time ≈ on time
01:26 / 01:27≈ on time ≈ on time
01:47 / 01:49≈ on time ≈ on time
01:55≈ on time ≈ on time
01:59≈ on time ≈ on time
02:06on 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 12 Nov— 00:440 min—
Wed 11 Nov— 00:440 min—
Tue 10 Nov— 00:49+2 min+3 min
Mon 9 Nov— 00:480 min—
Sun 8 NovAssen 00:440 min—
Sat 7 Nov— 02:420 min+16 min
Fri 6 Nov— 02:290 min—
Thu 5 Nov— 00:440 min—
Wed 4 Nov— 00:440 min—
Tue 3 Nov— 01:140 min—
Mon 2 Nov— 00:440 min—
Sun 1 NovAssen 00:440 min—
Sat 31 Oct— 02:120 min—
Fri 30 Oct— 02:110 min—
Thu 29 Oct— 00:450 min—
Wed 28 Oct— 00:450 min—
Tue 27 Oct— 00:460 min—
Mon 26 Oct— 00:450 min—
Sun 25 OctAssen 00:45No data—
Sat 24 Oct— 02:140 min—
Fri 23 Oct— 02:320 min—
Thu 22 Oct— 00:45No data—
Wed 21 Oct— 00:450 min—
Tue 20 Oct— 02:040 min—
Mon 19 Oct— 00:450 min—
Sun 18 OctAssen 00:190 min—
Sat 17 OctAlmere Centrum 02:400 min—
Fri 16 Oct— 02:190 min—
Thu 15 Oct— 00:450 min—
Wed 14 Oct— 00:450 min—