Train Arriva 37474 Leeuwarden – Groningen Europapark

Leeuwarden 19:50 → Groningen Europapark 20:40 Daily 0 h 50 min · 10 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 19:50 from Leeuwarden · Tue 17 Nov

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

  • Sat 14 Nov Max en route +18 min · last fix heading to Groningen +17 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 0% · 0
  • 10–30 min 13% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=1
  • — W n=0
  • — T n=0
  • — F n=0
  • 67% S n=3
  • 100% S n=4

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
19:50on time on time
19:53— —
19:59— —
20:03 / 20:04— —
20:07— —
20:13 / 20:14— —
20:21— —
20:26— —
20:36 / 20:38— —
20:40— —

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 NovGroningen 20:54Partial coverage+3 min+3 min
Sat 14 NovGroningen 21:08+17 min+18 min
Sun 8 NovGroningen 20:52Partial coverage+1 min+1 min
Sat 7 NovGroningen 20:52No data—
Sun 1 NovGroningen 20:52Partial coverage0 min—
Sat 31 OctGroningen 20:520 min—
Sun 25 OctGroningen 20:52No data—
Sat 24 OctGroningen 20:53No data—
Tue 20 Oct— 20:410 min—
Sun 18 OctGrijpskerk 20:35No data—
Sat 17 OctGrijpskerk 20:37No data—
Fri 16 OctLeeuwarden Camminghaburen 20:07No data—
Sun 11 OctGroningen 20:52Partial coverage+1 min+1 min
Sat 10 OctGroningen 20:54+1 min+1 min
Sun 4 OctZuidhorn 20:41No data—
Sat 3 OctZuidhorn 20:46No data—
Sun 27 SeptGrijpskerk 20:37No data—
Sat 26 SeptGrijpskerk 20:37No data—
Sun 20 SeptZuidhorn 20:43No data—
Sat 19 SeptZuidhorn 20:56No data—
Sun 13 SeptZuidhorn 20:44No data—
Sat 12 SeptZuidhorn 20:46No data—
Sun 6 SeptZuidhorn 20:40No data—
Sat 5 SeptZuidhorn 20:42No data—
Sun 30 AugZuidhorn 20:41No data—
Sat 29 AugZuidhorn 20:41No data—
Sun 23 AugZuidhorn 20:41No data—
Sat 22 AugZuidhorn 20:41No data—
Fri 21 AugZuidhorn 20:41No data—