Train Arriva 37469 Groningen Europapark → Leeuwarden

Groningen Europapark 20:19 → Leeuwarden 21:10 Daily 0 h 51 min · 10 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November +5 min

Next service: today 20:19 from Groningen Europapark · Sat 21 Nov

Next departure 20:19 today · Groningen Europapark
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 2 full · 3 partial · 3 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 4 full · 4 partial · 16 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sun 15 Nov Max en route +5 min · last fix heading to Leeuwarden Camminghaburen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=3
  • 80% S n=5

Stops and timetable

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

Last 90 days, 8 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
20:19on time on time
20:22 / 20:24— —
20:32— —
20:38— —
20:45— —
20:51— —
20:54 / 20:55— —
20:59 / 21:00— —
21:05— —
21:10— —

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
Sun 15 NovLeeuwarden Camminghaburen 21:24Partial coverage+5 min+5 min
Sat 14 NovLeeuwarden Camminghaburen 21:23+2 min+3 min
Sun 8 NovLeeuwarden Camminghaburen 21:22Partial coverage+1 min+3 min
Sat 7 NovLeeuwarden Camminghaburen 21:19+1 min—
Sun 1 NovLeeuwarden Camminghaburen 21:19Partial coverage+1 min+2 min
Sat 31 OctLeeuwarden Camminghaburen 21:20No data—
Sun 25 OctLeeuwarden Camminghaburen 21:24No data—
Sat 24 OctLeeuwarden Camminghaburen 21:22No data—
Sun 18 OctLeeuwarden Camminghaburen 21:200 min+1 min
Sat 17 OctLeeuwarden Camminghaburen 21:20No data—
Sun 11 OctLeeuwarden Camminghaburen 21:20Partial coverage+1 min—
Sat 10 OctLeeuwarden Camminghaburen 21:190 min—
Sun 4 OctLeeuwarden Camminghaburen 21:22No data—
Sat 3 OctLeeuwarden Camminghaburen 21:24No data—
Sun 27 SeptLeeuwarden Camminghaburen 21:20No data—
Sat 26 SeptLeeuwarden Camminghaburen 21:20No data—
Sun 20 SeptLeeuwarden Camminghaburen 21:21No data—
Sat 19 SeptLeeuwarden Camminghaburen 21:23No data—
Sun 13 SeptLeeuwarden Camminghaburen 21:20No data—
Sat 12 SeptLeeuwarden Camminghaburen 21:21No data—
Sun 6 SeptLeeuwarden Camminghaburen 21:20No data—
Sat 5 SeptLeeuwarden Camminghaburen 21:20No data—
Sun 30 AugLeeuwarden Camminghaburen 21:19No data—
Sat 29 AugLeeuwarden Camminghaburen 21:20No data—