Train Arriva 37459 Groningen Europapark – Leeuwarden

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

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 17:49 from Groningen Europapark · Mon 9 Nov

Next departure 17:49 tomorrow · Groningen Europapark
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 9 full · 3 partial · 13 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 14 full · 3 partial · 59 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 Leeuwarden, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 17
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=2
  • 100% T n=1
  • 100% F n=3
  • 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, 17 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:49on time on time
17:52 / 17:54≈ on time ≈ on time
18:02≈ on time ≈ on time
18:08≈ on time ≈ on time
18:15≈ on time ≈ on time
18:21≈ on time ≈ on time
18:24 / 18:25≈ on time ≈ on time
18:30≈ on time ≈ on time
18:35≈ on time ≈ +1 min
18:41on 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 NovLeeuwarden Camminghaburen 18:49Partial coverage0 min+1 min
Fri 6 NovLeeuwarden Camminghaburen 18:44+1 min+1 min
Thu 5 NovGrijpskerk 18:22No data—
Wed 4 NovBuitenpost 18:29No data—
Tue 3 NovGrijpskerk 18:220 min—
Mon 2 NovGrijpskerk 18:220 min—
Sat 31 OctLeeuwarden Camminghaburen 18:54Partial coverage+3 min+4 min
Fri 30 OctLeeuwarden Camminghaburen 18:49No data—
Thu 29 OctZuidhorn 18:16No data—
Wed 28 OctGrijpskerk 18:220 min—
Tue 27 OctZuidhorn 18:160 min—
Mon 26 OctGrijpskerk 18:22No data—
Sat 24 OctLeeuwarden Camminghaburen 18:52No data—
Fri 23 OctLeeuwarden Camminghaburen 18:49+1 min+3 min
Thu 22 OctLeeuwarden Camminghaburen 18:49No data—
Wed 21 OctLeeuwarden Camminghaburen 18:49No data—
Tue 20 OctLeeuwarden Camminghaburen 18:490 min—
Mon 19 OctLeeuwarden Camminghaburen 18:490 min—
Sat 17 OctLeeuwarden Camminghaburen 18:50No data—
Fri 16 OctLeeuwarden Camminghaburen 18:51No data—
Thu 15 OctHurdegaryp 18:44No data—
Wed 14 OctLeeuwarden Camminghaburen 18:49No data—
Tue 13 OctLeeuwarden Camminghaburen 18:49No data—
Mon 12 OctLeeuwarden Camminghaburen 18:490 min—
Sat 10 OctLeeuwarden Camminghaburen 18:51Partial coverage+1 min—
Fri 9 OctLeeuwarden Camminghaburen 18:490 min+1 min
Thu 8 OctZuidhorn 18:160 min—
Wed 7 OctGrijpskerk 18:220 min—
Tue 6 OctZuidhorn 18:160 min—
Mon 5 OctGrijpskerk 18:220 min—