Train NS 742 Groningen – Schiphol Airport

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Zuid at 14:12 No data

  1. Groningen11:48
  2. Assen12:05
  3. Zwolle12:44
  4. Lelystad Centrum13:11
  5. Almere Centrum13:26
  6. Amsterdam Zuid13:48
  7. Schiphol Airport14:00

Next service: tomorrow 11:48 from Groningen · Fri 6 Nov

Next departure 11:48 tomorrow · Groningen
On-time · 30 days
81%
13/16 runs under 3 min
RT coverage: 3 full · 13 partial · 14 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 3 full · 15 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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

Worst days

  • Sun 18 Oct Max en route +22 min · last fix heading to Amsterdam Zuid +22 min
  • Sat 31 Oct Max en route +11 min · last fix heading to Amsterdam Zuid +8 min
  • Sat 24 Oct Max en route +7 min · last fix heading to Amsterdam Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 15
  • 3–10 min 11% · 2
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
11:48on time on time
12:05— —
12:44 / 12:46— —
13:11 / 13:12— —
13:26 / 13:28— —
13:48 / 13:54— —
14:00— —

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 NovAmsterdam Zuid 14:12No data—
Wed 4 NovAmsterdam Zuid 14:08Partial coverage0 min—
Tue 3 NovAmsterdam Zuid 14:57No data—
Mon 2 NovAmsterdam Zuid 14:08No data—
Sun 1 NovAmsterdam Zuid 14:09Partial coverage0 min—
Sat 31 OctAmsterdam Zuid 14:17Partial coverage+8 min+11 min
Fri 30 OctAmsterdam Zuid 14:38No data—
Thu 29 OctAmsterdam Zuid 14:18No data—
Wed 28 OctAmsterdam Zuid 14:08No data—
Tue 27 OctAmsterdam Zuid 14:08Partial coverage0 min—
Mon 26 OctAmsterdam Zuid 14:08No data—
Sun 25 OctAmsterdam Zuid 14:16No data—
Sat 24 OctAmsterdam Zuid 14:11+4 min+7 min
Fri 23 OctAmsterdam Zuid 14:16No data—
Thu 22 OctAmsterdam Zuid 14:08Partial coverage0 min—
Wed 21 OctAmsterdam Zuid 14:08No data—
Tue 20 OctAmsterdam Zuid 14:08Partial coverage0 min—
Mon 19 OctAmsterdam Zuid 14:08Partial coverage0 min—
Sun 18 OctAmsterdam Zuid 14:42+22 min+22 min
Sat 17 OctAmsterdam Zuid 14:080 min—
Fri 16 OctAmsterdam Zuid 14:09No data—
Thu 15 OctAmsterdam Zuid 14:08No data—
Wed 14 OctAmsterdam Zuid 14:08No data—
Tue 13 OctAmsterdam Zuid 14:08No data—
Mon 12 OctAmsterdam Zuid 14:08Partial coverage0 min—
Sun 11 OctAmsterdam Zuid 14:09Partial coverage+1 min+1 min
Sat 10 OctAmsterdam Zuid 14:09Partial coverage+1 min—
Fri 9 OctAmsterdam Zuid 14:08Partial coverage0 min—
Thu 8 OctAmsterdam Zuid 14:08Partial coverage0 min—
Wed 7 OctAmsterdam Zuid 14:08Partial coverage0 min—