Train Arriva 37453 Groningen Europapark – Leeuwarden

Groningen Europapark 16:19 → Leeuwarden 17:11 Daily 0 h 52 min · 10 stops Arriva

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 16:19 from Groningen Europapark · Sun 8 Nov

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

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 95% · 18
  • 3–10 min 5% · 1
  • 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
  • 0% T n=1
  • 100% F n=2
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 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
16:19on time +1 min
16:22 / 16:23≈ on time ≈ +1 min
16:31 / 16:32≈ on time ≈ +1 min
16:38≈ on time ≈ +1 min
16:45≈ on time ≈ +2 min
16:51≈ on time ≈ +2 min
16:54 / 16:55≈ on time ≈ +2 min
17:00≈ +1 min ≈ +2 min
17:05≈ +1 min ≈ +2 min
17:11+1 min +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
Sat 7 NovLeeuwarden Camminghaburen 17:19Partial coverage+1 min—
Fri 6 NovLeeuwarden Camminghaburen 17:23+2 min+4 min
Thu 5 NovLeeuwarden Camminghaburen 17:19No data—
Wed 4 NovLeeuwarden Camminghaburen 17:190 min—
Tue 3 NovLeeuwarden Camminghaburen 17:19No data—
Mon 2 NovLeeuwarden Camminghaburen 17:19No data—
Sun 1 NovLeeuwarden Camminghaburen 17:20+1 min—
Sat 31 OctLeeuwarden Camminghaburen 17:19Partial coverage0 min—
Fri 30 OctLeeuwarden Camminghaburen 17:21No data—
Thu 29 OctLeeuwarden Camminghaburen 17:19No data—
Wed 28 OctLeeuwarden Camminghaburen 17:230 min—
Tue 27 OctLeeuwarden Camminghaburen 17:190 min—
Mon 26 OctLeeuwarden Camminghaburen 17:19No data—
Sun 25 OctLeeuwarden Camminghaburen 17:23No data—
Sat 24 OctLeeuwarden Camminghaburen 17:21Partial coverage0 min+2 min
Fri 23 OctLeeuwarden Camminghaburen 17:23No data—
Thu 22 OctLeeuwarden Camminghaburen 17:22No data—
Wed 21 OctLeeuwarden Camminghaburen 17:26No data—
Tue 20 OctLeeuwarden Camminghaburen 17:200 min—
Mon 19 OctLeeuwarden Camminghaburen 17:200 min—
Sun 18 OctLeeuwarden Camminghaburen 17:20+1 min—
Sat 17 OctLeeuwarden Camminghaburen 17:20No data—
Fri 16 OctLeeuwarden Camminghaburen 17:23No data—
Thu 15 OctLeeuwarden Camminghaburen 17:17No data—
Wed 14 OctLeeuwarden Camminghaburen 17:22No data—
Tue 13 OctLeeuwarden Camminghaburen 17:21No data—
Mon 12 OctLeeuwarden Camminghaburen 17:190 min—
Sun 11 OctLeeuwarden Camminghaburen 17:23+3 min+4 min
Sat 10 OctLeeuwarden Camminghaburen 17:20Partial coverage+1 min—
Fri 9 OctLeeuwarden Camminghaburen 17:22+1 min+2 min