Train Arriva 37460 Leeuwarden – Groningen

Leeuwarden 16:20 → Groningen 17:06 Mon, Tue, Wed, Thu, Fri, Sat 0 h 46 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 16:20 today · Leeuwarden
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 3 full · 8 partial · 14 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 3 full · 10 partial · 62 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

  • Wed 7 Oct Max en route +11 min · last fix heading to Zuidhorn +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 0% · 0
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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:20on time +1 min
16:23— —
16:29— —
16:33 / 16:34— —
16:37— —
16:43 / 16:44— —
16:51— —
16:57— —
17:06— —

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:09Partial coverage0 min—
Tue 3 NovZuidhorn 17:09No data—
Mon 2 NovZuidhorn 17:14No data—
Sat 31 OctGroningen 17:22No data—
Fri 30 OctZuidhorn 17:11No data—
Thu 29 OctZuidhorn 17:11Partial coverage0 min—
Wed 28 OctZuidhorn 17:11Partial coverage0 min—
Tue 27 OctZuidhorn 17:11No data—
Mon 26 OctZuidhorn 17:12No data—
Sat 24 OctGroningen 17:220 min+2 min
Fri 23 OctZuidhorn 17:12No data—
Thu 22 OctZuidhorn 17:11No data—
Wed 21 OctZuidhorn 17:11No data—
Tue 20 OctZuidhorn 17:11Partial coverage0 min—
Mon 19 OctZuidhorn 17:12Partial coverage0 min—
Sat 17 OctGrijpskerk 17:05No data—
Fri 16 OctGrijpskerk 17:10No data—
Thu 15 OctZuidhorn 17:17No data—
Wed 14 OctZuidhorn 17:11No data—
Tue 13 OctZuidhorn 17:11No data—
Mon 12 OctZuidhorn 17:11Partial coverage0 min—
Sat 10 OctGroningen 17:23+1 min+2 min
Fri 9 OctZuidhorn 17:14+2 min+3 min
Thu 8 OctZuidhorn 17:12Partial coverage+2 min+3 min
Wed 7 OctZuidhorn 17:19Partial coverage+11 min+11 min
Tue 6 OctZuidhorn 17:12Partial coverage0 min—
Mon 5 OctZuidhorn 17:13Partial coverage0 min—
Sat 3 OctGroningen 17:23No data—
Fri 2 OctZuidhorn 17:12No data—
Thu 1 OctZuidhorn 17:11No data—