Train NS 785 Schiphol Airport – Groningen

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

Running now · updated 23:05

Heading to Groningen 0 min

Estimated arrival at Groningen 01:12 · 26 km/h

  1. Schiphol Airport22:59
  2. Amsterdam Zuid23:06
  3. Almere Centrum23:31
  4. Lelystad Centrum23:46
  5. Zwolle00:14
  6. Assen00:55
  7. Groningen01:12

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

On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 26 full · 1 partial · 1 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 28 full · 2 partial · 16 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 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

  • Fri 9 Oct Max en route +23 min · last fix heading to — +23 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
22:59on time on time
23:06 / 23:11≈ on time ≈ on time
23:31 / 23:33≈ on time ≈ on time
23:46 / 23:48≈ on time ≈ on time
00:14 / 00:16≈ on time ≈ on time
00:55≈ on time ≈ on time
01: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
Fri 6 Nov— 23:040 min—
Thu 5 Nov— 01:290 min—
Wed 4 Nov— 02:340 min—
Tue 3 Nov— 01:180 min—
Sun 1 NovAssen 01:140 min—
Sat 31 OctAmsterdam Zuid 01:130 min—
Fri 30 Oct— 01:130 min—
Thu 29 Oct— 01:140 min—
Tue 27 Oct— 01:320 min—
Mon 26 OctZwolle 01:16Partial coverage0 min—
Sun 25 OctAssen 01:130 min—
Sat 24 Oct— 01:30No data—
Fri 23 Oct— 01:140 min—
Thu 22 Oct— 01:150 min—
Wed 21 Oct— 02:050 min—
Tue 20 Oct— 01:130 min—
Mon 19 Oct— 02:240 min—
Sun 18 OctAssen 01:130 min+2 min
Sat 17 OctAssen 01:200 min—
Fri 16 Oct— 01:160 min—
Thu 15 Oct— 01:140 min—
Wed 14 Oct— 01:140 min—
Tue 13 Oct— 01:180 min—
Mon 12 Oct— 01:130 min+2 min
Sun 11 OctAlmere Centrum 23:480 min—
Sat 10 Oct— 01:140 min—
Fri 9 Oct— 01:59+23 min+23 min
Thu 8 Oct— 01:140 min—
Wed 7 Oct— 01:140 min—
Tue 6 Oct— 01:130 min—