Train Arriva 37462 Leeuwarden – Groningen

Leeuwarden 16:50 → Groningen 17:36 Daily 0 h 46 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:50 from Leeuwarden · Thu 5 Nov

Next departure 16:50 today · Leeuwarden
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 6 full · 8 partial · 15 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 6 full · 10 partial · 72 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 1 Nov Max en route +4 min · last fix heading to Groningen +4 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Groningen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
16:50on time on time
16:53≈ on time ≈ on time
16:59≈ on time ≈ +1 min
17:03 / 17:04≈ on time ≈ +1 min
17:07≈ on time ≈ +1 min
17:13 / 17:14≈ on time ≈ +2 min
17:21≈ on time ≈ +2 min
17:27≈ on time ≈ +3 min
17:36on time +3 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 NovZuidhorn 17:39No data—
Tue 3 NovZuidhorn 17:39Partial coverage0 min—
Mon 2 NovZuidhorn 17:39Partial coverage0 min—
Sun 1 NovGroningen 17:55+4 min+4 min
Sat 31 OctGroningen 17:52+3 min+3 min
Fri 30 OctZuidhorn 17:43No data—
Thu 29 OctZuidhorn 17:33No data—
Wed 28 OctZuidhorn 17:43Partial coverage0 min—
Tue 27 OctZuidhorn 17:41No data—
Mon 26 OctZuidhorn 17:41No data—
Sun 25 OctGroningen 17:52No data—
Sat 24 OctGroningen 17:520 min—
Fri 23 OctZuidhorn 17:42No data—
Thu 22 OctZuidhorn 17:41No data—
Wed 21 OctZuidhorn 17:49No data—
Tue 20 OctZuidhorn 17:41No data—
Mon 19 OctZuidhorn 17:43Partial coverage0 min—
Sun 18 OctGrijpskerk 17:350 min—
Sat 17 OctGrijpskerk 17:35No data—
Fri 16 OctGrijpskerk 17:38No data—
Thu 15 OctZuidhorn 17:41No data—
Wed 14 OctZuidhorn 17:41No data—
Tue 13 OctZuidhorn 17:50No data—
Mon 12 OctZuidhorn 17:41Partial coverage0 min—
Sun 11 OctGroningen 17:52+1 min+1 min
Sat 10 OctGroningen 17:520 min—
Fri 9 OctZuidhorn 17:43Partial coverage0 min+2 min
Thu 8 OctZuidhorn 17:34Partial coverage+1 min+1 min
Wed 7 OctZuidhorn 17:41Partial coverage0 min—
Tue 6 OctZuidhorn 17:41Partial coverage0 min+3 min