Train Arriva 37430 Leeuwarden – Groningen Europapark

Leeuwarden 08:50 → Groningen Europapark 09:40 Daily 0 h 50 min · 10 stops Arriva

✓ Today’s run finished

Today, last fix heading to Groningen at 09:52 0 min

  1. Leeuwarden08:50
  2. Hurdegaryp08:59
  3. Feanwâlden09:03
  4. Buitenpost09:13
  5. Grijpskerk09:21
  6. Groningen09:36
  7. Groningen Europapark09:40

Next service: tomorrow 08:50 from Leeuwarden · Sun 8 Nov

Next departure 08:50 tomorrow · Leeuwarden
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 10 full · 3 partial · 17 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 13 full · 3 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 17 Oct Max en route +6 min · last fix heading to Grijpskerk +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 75% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 16 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
08:50on time on time
08:53≈ on time ≈ on time
08:59≈ on time ≈ +1 min
09:03 / 09:04≈ on time ≈ +1 min
09:07≈ on time ≈ +1 min
09:13 / 09:14≈ on time ≈ +1 min
09:21≈ on time ≈ +1 min
09:27≈ +1 min ≈ +2 min
09:36 / 09:38≈ +1 min ≈ +2 min
09:40+1 min +2 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 09:52Partial coverage0 min—
Fri 6 NovZuidhorn 09:39No data—
Thu 5 NovZuidhorn 09:43No data—
Wed 4 NovZuidhorn 09:390 min—
Tue 3 NovZuidhorn 09:44No data—
Mon 2 NovZuidhorn 09:42No data—
Sun 1 NovGroningen 09:530 min—
Sat 31 OctGroningen 09:52No data—
Fri 30 OctZuidhorn 09:41No data—
Thu 29 OctZuidhorn 09:42No data—
Wed 28 OctZuidhorn 09:590 min—
Tue 27 OctZuidhorn 10:060 min—
Mon 26 OctZuidhorn 09:55No data—
Sun 25 OctGroningen 09:52No data—
Sat 24 OctGroningen 09:52Partial coverage0 min—
Fri 23 OctZuidhorn 09:45No data—
Thu 22 OctZuidhorn 09:43No data—
Wed 21 OctZuidhorn 09:41No data—
Tue 20 OctZuidhorn 09:500 min—
Mon 19 OctZuidhorn 09:420 min—
Sun 18 OctLeeuwarden Camminghaburen 09:05+1 min—
Sat 17 OctGrijpskerk 09:41+6 min+6 min
Fri 16 OctGrijpskerk 09:36No data—
Thu 15 OctZuidhorn 09:41No data—
Wed 14 OctZuidhorn 09:41No data—
Tue 13 OctZuidhorn 09:41No data—
Mon 12 OctZuidhorn 09:42No data—
Sun 11 OctGroningen 09:52+1 min+2 min
Sat 10 OctGroningen 09:52Partial coverage0 min—
Fri 9 OctZuidhorn 09:42+1 min+1 min