Train NS 733 Schiphol Airport – Groningen

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 10:00 from Schiphol Airport · Thu 5 Nov

Next departure 10:00 today · Schiphol Airport
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 12 full · 9 partial · 8 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 12 full · 10 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sun 11 Oct Max en route +13 min · last fix heading to Assen +13 min
  • Sun 18 Oct Max en route +16 min · last fix heading to Lelystad Centrum +12 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Assen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 19
  • 3–10 min 5% · 1
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 100% W n=3
  • 67% T n=3
  • 100% F n=2
  • 100% S n=4
  • 33% S n=3

Stops and timetable

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

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