Train Arriva 37355 Groningen Europapark – Leeuwarden

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

It has not run yet today

Last recorded run: Thursday 19 November +5 min

Next service: today 17:04 from Groningen Europapark · Fri 20 Nov

Next departure 17:04 today · Groningen Europapark
On-time · 30 days
75%
15/20 runs under 3 min
RT coverage: 9 full · 11 partial · 9 no data
On-time · 90 days
83%
25/30 runs under 3 min
RT coverage: 12 full · 18 partial · 58 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 13 Nov Max en route +8 min · last fix heading to Feanwâlden +7 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Feanwâlden +6 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Feanwâlden +5 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Feanwâlden +4 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Feanwâlden +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 25
  • 3–10 min 17% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 75% T n=4
  • 100% W n=5
  • 67% T n=3
  • 67% F n=3
  • 100% S n=5
  • 50% S n=4

Stops and timetable

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

Last 90 days, 30 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
17:04on time on time
17:07 / 17:09≈ on time ≈ +1 min
17:25≈ on time ≈ +2 min
17:33 / 17:34≈ on time ≈ +3 min
17:45on time +4 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
Thu 19 NovFeanwâlden 17:48Partial coverage+5 min+5 min
Wed 18 NovFeanwâlden 17:49Partial coverage+1 min+2 min
Tue 17 NovFeanwâlden 17:48Partial coverage+1 min+1 min
Mon 16 NovFeanwâlden 17:48Partial coverage+3 min+3 min
Sun 15 NovFeanwâlden 17:440 min—
Sat 14 NovFeanwâlden 17:480 min—
Fri 13 NovFeanwâlden 17:52+7 min+8 min
Thu 12 NovFeanwâlden 17:48Partial coverage+3 min+3 min
Wed 11 NovFeanwâlden 17:48Partial coverage+1 min+1 min
Tue 10 NovFeanwâlden 17:48Partial coverage+6 min+6 min
Mon 9 NovFeanwâlden 17:48Partial coverage0 min+1 min
Sun 8 NovFeanwâlden 17:48+4 min+4 min
Sat 7 NovFeanwâlden 17:49+1 min+3 min
Fri 6 NovFeanwâlden 17:480 min+2 min
Thu 5 NovFeanwâlden 17:48No data—
Wed 4 NovFeanwâlden 17:48Partial coverage0 min—
Tue 3 NovFeanwâlden 17:48No data—
Mon 2 NovFeanwâlden 17:48No data—
Sun 1 NovFeanwâlden 17:49+4 min+5 min
Sat 31 OctFeanwâlden 17:480 min—
Fri 30 OctFeanwâlden 17:49No data—
Thu 29 OctFeanwâlden 17:48No data—
Wed 28 OctFeanwâlden 17:48Partial coverage0 min—
Tue 27 OctFeanwâlden 17:48No data—
Mon 26 OctFeanwâlden 17:48Partial coverage+1 min+1 min
Sun 25 OctFeanwâlden 17:45No data—
Sat 24 OctFeanwâlden 17:480 min—
Fri 23 OctFeanwâlden 17:49No data—
Thu 22 OctFeanwâlden 17:44No data—
Wed 21 OctFeanwâlden 17:48No data—