Train Arriva 37456 Leeuwarden – Groningen

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

✓ Today’s run finished

Today, last fix heading to Zuidhorn at 16:14 No data

  1. Leeuwarden15:20
  2. Leeuwarden Camminghaburen15:23
  3. Feanwâlden15:33
  4. De Westereen15:37
  5. Buitenpost15:43
  6. Zuidhorn15:57
  7. Groningen16:06

Next service: tomorrow 15:20 from Leeuwarden · Sat 7 Nov

Next departure 15:20 tomorrow · 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
93%
13/14 runs under 3 min
RT coverage: 3 full · 11 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 +16 min · last fix heading to Zuidhorn +16 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
15:20on time on time
15:23— —
15:29— —
15:33 / 15:34— —
15:37— —
15:43 / 15:44— —
15:51— —
15:57— —
16: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
Fri 6 NovZuidhorn 16:14No data—
Thu 5 NovZuidhorn 16:10No data—
Wed 4 NovZuidhorn 16:09Partial coverage0 min—
Tue 3 NovZuidhorn 16:09No data—
Sat 31 OctGroningen 16:220 min—
Fri 30 OctZuidhorn 16:11No data—
Thu 29 OctZuidhorn 16:11No data—
Wed 28 OctZuidhorn 16:11Partial coverage0 min—
Tue 27 OctZuidhorn 16:13Partial coverage0 min—
Mon 26 OctZuidhorn 16:11No data—
Sat 24 OctGroningen 16:22+1 min—
Fri 23 OctZuidhorn 16:13No data—
Thu 22 OctZuidhorn 16:12No data—
Wed 21 OctZuidhorn 16:11No data—
Tue 20 OctZuidhorn 16:35Partial coverage0 min—
Mon 19 OctZuidhorn 16:13Partial coverage0 min—
Sat 17 OctGrijpskerk 16:05No data—
Fri 16 OctGrijpskerk 16:06No data—
Thu 15 OctZuidhorn 16:11No data—
Wed 14 OctZuidhorn 16:11No data—
Tue 13 OctZuidhorn 16:15No data—
Mon 12 OctZuidhorn 16:11Partial coverage0 min—
Sat 10 OctGroningen 16:22+1 min+2 min
Fri 9 OctZuidhorn 16:29Partial coverage+16 min+16 min
Thu 8 OctZuidhorn 16:12Partial coverage+1 min+2 min
Wed 7 OctZuidhorn 16:11Partial coverage+1 min+1 min
Tue 6 OctZuidhorn 16:12Partial coverage0 min—
Mon 5 OctZuidhorn 16:11Partial coverage0 min—
Sat 3 OctGroningen 16:22No data—
Fri 2 OctZuidhorn 16:11No data—