Train Arriva 37347 Groningen Europapark – Leeuwarden

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 15:04 from Groningen Europapark · Sat 7 Nov

Next departure 15:04 today · Groningen Europapark
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 3 full · 9 partial · 17 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 3 full · 12 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Thu 8 Oct Max en route +6 min · last fix heading to Feanwâlden +6 min
  • Mon 5 Oct Max en route +7 min · last fix heading to Feanwâlden +5 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 87% · 13
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=2
  • 50% T n=2
  • 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, 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
15:04on time on time
15:07 / 15:09— —
15:25— —
15:33 / 15:34— —
15: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
Fri 6 NovFeanwâlden 15:52No data—
Thu 5 NovFeanwâlden 15:48No data—
Wed 4 NovFeanwâlden 15:49Partial coverage0 min+1 min
Tue 3 NovFeanwâlden 15:49No data—
Mon 2 NovFeanwâlden 15:49No data—
Sun 1 NovFeanwâlden 15:48+2 min+2 min
Sat 31 OctFeanwâlden 15:48Partial coverage0 min—
Fri 30 OctFeanwâlden 15:49No data—
Thu 29 OctFeanwâlden 15:48Partial coverage0 min—
Wed 28 OctFeanwâlden 15:48Partial coverage0 min—
Tue 27 OctFeanwâlden 15:49No data—
Mon 26 OctFeanwâlden 15:48No data—
Sun 25 OctFeanwâlden 15:46No data—
Sat 24 OctFeanwâlden 15:48Partial coverage0 min—
Fri 23 OctFeanwâlden 15:48No data—
Thu 22 OctFeanwâlden 15:49No data—
Wed 21 OctFeanwâlden 15:49No data—
Tue 20 OctFeanwâlden 15:49Partial coverage0 min—
Mon 19 OctFeanwâlden 15:49Partial coverage0 min—
Sun 18 OctFeanwâlden 15:45No data—
Sat 17 OctFeanwâlden 15:49No data—
Fri 16 OctFeanwâlden 15:48No data—
Thu 15 OctFeanwâlden 15:48No data—
Wed 14 OctFeanwâlden 15:48No data—
Tue 13 OctFeanwâlden 15:50No data—
Mon 12 OctFeanwâlden 15:48Partial coverage0 min—
Sun 11 OctFeanwâlden 15:46+1 min+2 min
Sat 10 OctFeanwâlden 15:51Partial coverage+2 min+3 min
Fri 9 OctFeanwâlden 15:490 min—
Thu 8 OctFeanwâlden 15:52Partial coverage+6 min+6 min