Train Arriva 37432 Leeuwarden – Groningen Europapark

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 09:20 today · Leeuwarden
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 1 full · 11 partial · 13 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 1 full · 12 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Tue 6 Oct Max en route +6 min · last fix heading to Groningen +5 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Groningen +4 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 85% · 11
  • 3–10 min 15% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 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
09:20on time on time
09:23— —
09:29— —
09:33 / 09:34— —
09:37— —
09:43 / 09:44— —
09:51— —
09:57— —
10:06 / 10:08— —
10:10— —

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