Train Arriva 37360 Leeuwarden – Groningen Europapark

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 16:16 from Leeuwarden · Thu 19 Nov

Next departure 16:16 today · Leeuwarden
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 6 full · 10 partial · 13 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 10 full · 17 partial · 61 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 Groningen Europapark, 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 +5 min · last fix heading to Groningen +4 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Groningen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 50% T n=2
  • 50% F n=2
  • 100% S n=3
  • 100% S n=5

Stops and timetable

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

Last 90 days, 27 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
16:16on time on time
16:25≈ on time ≈ +1 min
16:41≈ on time ≈ +1 min
16:51 / 16:52≈ on time ≈ +2 min
16:55on time +2 min

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