Train Arriva 37331 Groningen Europapark – Leeuwarden

Groningen Europapark 11:04 → Leeuwarden 11:45 Daily 0 h 41 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to Feanwâlden at 11:48 No data

  1. Groningen Europapark11:04
  2. Groningen11:07
  3. Buitenpost11:25
  4. Feanwâlden11:33
  5. Leeuwarden11:45

Next service: tomorrow 11:04 from Groningen Europapark · Fri 6 Nov

Next departure 11:04 tomorrow · Groningen Europapark
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 2 full · 11 partial · 16 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 2 full · 12 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: +2 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 +12 min · last fix heading to Groningen Europapark +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
11:04on time +1 min
11:07 / 11:09— —
11:25— —
11:33 / 11:34— —
11:45— —

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 11:48No data—
Wed 4 NovFeanwâlden 11:52Partial coverage+2 min+4 min
Tue 3 NovFeanwâlden 11:48No data—
Mon 2 NovFeanwâlden 11:48No data—
Sun 1 NovFeanwâlden 11:47+1 min+2 min
Sat 31 OctFeanwâlden 11:48Partial coverage0 min—
Fri 30 OctFeanwâlden 11:48No data—
Thu 29 OctFeanwâlden 11:50No data—
Wed 28 OctFeanwâlden 11:48Partial coverage0 min—
Tue 27 OctFeanwâlden 11:54Partial coverage0 min—
Mon 26 OctFeanwâlden 11:48No data—
Sun 25 OctFeanwâlden 11:45No data—
Sat 24 OctFeanwâlden 11:48Partial coverage0 min—
Fri 23 OctFeanwâlden 11:49No data—
Thu 22 OctFeanwâlden 11:49No data—
Wed 21 OctFeanwâlden 11:49No data—
Tue 20 OctFeanwâlden 11:51Partial coverage0 min—
Mon 19 OctFeanwâlden 11:48Partial coverage0 min—
Sat 17 OctFeanwâlden 11:48No data—
Fri 16 OctFeanwâlden 11:48No data—
Thu 15 OctFeanwâlden 11:48No data—
Wed 14 OctFeanwâlden 11:48No data—
Tue 13 OctFeanwâlden 11:48No data—
Mon 12 OctFeanwâlden 11:48No data—
Sun 11 OctFeanwâlden 11:46+2 min+2 min
Sat 10 OctFeanwâlden 11:48Partial coverage0 min—
Fri 9 OctFeanwâlden 11:49Partial coverage+1 min+2 min
Thu 8 OctFeanwâlden 11:49Partial coverage0 min+1 min
Wed 7 OctGroningen Europapark 12:01Partial coverage+12 min+12 min
Tue 6 OctFeanwâlden 11:49Partial coverage+1 min+2 min