Train Arriva 37352 Leeuwarden – Groningen Europapark

Leeuwarden 14:16 → Groningen Europapark 14:55 Daily 0 h 39 min · 5 stops Arriva

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 14:16 from Leeuwarden · Tue 10 Nov

Next departure 14:16 today · Leeuwarden
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 3 full · 9 partial · 17 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 4 full · 15 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
14:16on time on time
14:25— —
14:41— —
14:51 / 14:52— —
14:55— —

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
Mon 9 NovGroningen 15:04Partial coverage0 min—
Sun 8 NovGroningen 15:080 min—
Sat 7 NovGroningen 15:04Partial coverage0 min—
Fri 6 NovGroningen 15:07No data—
Thu 5 NovGroningen 15:09No data—
Wed 4 NovGroningen 15:04Partial coverage0 min+1 min
Tue 3 NovGroningen 15:07No data—
Mon 2 NovGroningen 15:07No data—
Sun 1 NovGroningen 15:12+2 min+2 min
Sat 31 OctGroningen 15:06No data—
Fri 30 OctGroningen 15:07No data—
Thu 29 OctGroningen 15:07Partial coverage0 min—
Wed 28 OctGroningen 15:06Partial coverage0 min—
Tue 27 OctGroningen 15:07Partial coverage0 min—
Mon 26 OctGroningen 15:07No data—
Sun 25 OctGroningen 15:08No data—
Sat 24 OctGroningen 15:06Partial coverage0 min—
Fri 23 OctGroningen 15:07No data—
Thu 22 OctGroningen 15:06No data—
Wed 21 OctGroningen 15:10No data—
Tue 20 OctGroningen 15:07Partial coverage0 min—
Mon 19 OctGroningen 15:07Partial coverage0 min—
Sun 18 OctBuitenpost 14:500 min—
Sat 17 OctFeanwâlden 14:42No data—
Fri 16 OctFeanwâlden 14:40No data—
Thu 15 OctGroningen 15:06No data—
Wed 14 OctGroningen 15:09No data—
Tue 13 OctGroningen 15:07No data—
Mon 12 OctGroningen 15:06No data—
Sun 11 OctGroningen 15:10+2 min+2 min