Train Arriva 37359 Groningen Europapark – Leeuwarden

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:04 from Groningen Europapark · Thu 5 Nov

Next departure 18:04 today · Groningen Europapark
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 2 full · 11 partial · 14 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 2 full · 12 partial · 69 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

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 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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