Train Arriva 37456 Leeuwarden – Groningen Europapark

Leeuwarden 15:20 → Groningen Europapark 16:10 Mon, Tue, Wed, Thu, Fri, Sat 0 h 50 min · 10 stops Arriva

It does not run today

Last recorded run: Saturday 7 November +1 min

Next service: tomorrow 15:20 from Leeuwarden · Mon 9 Nov

Next departure 15:20 tomorrow · Leeuwarden
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 6 full · 4 partial · 14 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 60 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 Europapark, 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

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

  • Early 0% · 0
  • On time 93% · 14
  • 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=4
  • — S n=0

Stops and timetable

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

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