Train Arriva 37341 Groningen Europapark – Leeuwarden

Groningen Europapark 13:34 → Leeuwarden 14:15 Mon, Tue, Wed, Thu, Fri, Sat 0 h 41 min · 5 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:34 from Groningen Europapark · Fri 6 Nov

Next departure 13:34 today · Groningen Europapark
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 17 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 63 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: 0 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

Worst days

  • Wed 7 Oct Max en route +3 min · last fix heading to Feanwâlden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 10
  • 3–10 min 9% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
13:34on time on time
13:37 / 13:39— —
13:47— —
14:03 / 14:04— —
14:15— —

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
Thu 5 NovFeanwâlden 14:18No data—
Wed 4 NovFeanwâlden 14:18Partial coverage0 min—
Tue 3 NovFeanwâlden 14:18No data—
Mon 2 NovFeanwâlden 14:18No data—
Sat 31 OctFeanwâlden 14:18Partial coverage0 min—
Fri 30 OctFeanwâlden 14:18No data—
Thu 29 OctFeanwâlden 14:18No data—
Wed 28 OctFeanwâlden 14:18Partial coverage0 min—
Tue 27 OctFeanwâlden 14:20Partial coverage0 min—
Mon 26 OctFeanwâlden 14:18No data—
Sat 24 OctFeanwâlden 14:18No data—
Fri 23 OctFeanwâlden 14:18No data—
Thu 22 OctFeanwâlden 14:20No data—
Wed 21 OctFeanwâlden 14:18No data—
Tue 20 OctFeanwâlden 14:18Partial coverage0 min—
Mon 19 OctFeanwâlden 14:18Partial coverage0 min—
Sat 17 OctFeanwâlden 14:18No data—
Fri 16 OctFeanwâlden 14:18No data—
Thu 15 OctFeanwâlden 14:21No data—
Wed 14 OctFeanwâlden 14:20No data—
Tue 13 OctFeanwâlden 14:18No data—
Mon 12 OctFeanwâlden 14:18No data—
Sat 10 OctFeanwâlden 14:18No data—
Fri 9 OctFeanwâlden 14:18Partial coverage0 min—
Thu 8 OctFeanwâlden 14:18Partial coverage0 min—
Wed 7 OctFeanwâlden 14:22Partial coverage+3 min+3 min
Tue 6 OctFeanwâlden 14:18Partial coverage0 min—
Mon 5 OctFeanwâlden 14:18Partial coverage+2 min+2 min
Sat 3 OctFeanwâlden 14:18No data—
Fri 2 OctFeanwâlden 14:18No data—