Train Arriva 37464 Leeuwarden – Groningen Europapark

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

✓ Today’s run finished

Today, last fix heading to Groningen at 18:22 +1 min

  1. Leeuwarden17:20
  2. Hurdegaryp17:29
  3. Feanwâlden17:33
  4. Buitenpost17:43
  5. Grijpskerk17:51
  6. Groningen18:06
  7. Groningen Europapark18:10

Next service: Monday 17:20 from Leeuwarden · Mon 9 Nov

Next departure 17:20 Monday · Leeuwarden
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 7 full · 4 partial · 15 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 62 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

  • Sat 31 Oct Max en route +4 min · last fix heading to Groningen +3 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 7% · 1
  • 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=2
  • 75% 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
17:20on time on time
17:23≈ on time ≈ on time
17:29≈ on time ≈ on time
17:33 / 17:34≈ on time ≈ on time
17:37≈ on time ≈ on time
17:43 / 17:44≈ on time ≈ +1 min
17:51≈ on time ≈ +1 min
17:57≈ on time ≈ +1 min
18:06 / 18:08≈ on time ≈ +1 min
18: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 18:22Partial coverage+1 min+1 min
Fri 6 NovZuidhorn 18:09+1 min+1 min
Thu 5 NovZuidhorn 18:09No data—
Wed 4 NovZuidhorn 18:09No data—
Tue 3 NovZuidhorn 18:09No data—
Mon 2 NovZuidhorn 18:09No data—
Sat 31 OctGroningen 18:24Partial coverage+3 min+4 min
Fri 30 OctZuidhorn 18:11No data—
Thu 29 OctZuidhorn 18:11No data—
Wed 28 OctZuidhorn 18:110 min—
Tue 27 OctZuidhorn 18:11No data—
Mon 26 OctZuidhorn 18:11+1 min—
Sat 24 OctGroningen 18:22Partial coverage0 min—
Fri 23 OctZuidhorn 18:12No data—
Thu 22 OctZuidhorn 18:11No data—
Wed 21 OctZuidhorn 18:11No data—
Tue 20 OctZuidhorn 18:110 min—
Mon 19 OctZuidhorn 18:110 min—
Sat 17 OctGrijpskerk 18:06No data—
Fri 16 OctGrijpskerk 18:07No data—
Thu 15 OctZuidhorn 18:11No data—
Wed 14 OctZuidhorn 18:11No data—
Tue 13 OctZuidhorn 18:06No data—
Mon 12 OctZuidhorn 18:110 min—
Sat 10 OctGroningen 18:22Partial coverage0 min—
Fri 9 OctZuidhorn 18:11+1 min+1 min
Thu 8 OctZuidhorn 18:12+1 min+1 min
Wed 7 OctZuidhorn 18:110 min—
Tue 6 OctZuidhorn 18:110 min—
Mon 5 OctZuidhorn 18:110 min—