Train Arriva 37490 Leeuwarden – Groningen Europapark

Leeuwarden 23:50 → Groningen Europapark 00:40 Daily 0 h 50 min · 10 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November +5 min

Next service: today 23:50 from Leeuwarden · Fri 20 Nov

Next departure 23:50 today · Leeuwarden
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 0 full · 3 partial · 1 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 1 full · 4 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 4
  • 3–10 min 20% · 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
  • — S n=0
  • 80% S n=5

Stops and timetable

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

Last 90 days, 5 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
23:50on time on time
23:53— —
23:59— —
00:03 / 00:04— —
00:07— —
00:13 / 00:14— —
00:21— —
00:26— —
00:37 / 00:38— —
00: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 00:54Partial coverage+5 min+5 min
Sun 8 NovGroningen 00:52Partial coverage0 min—
Sun 1 NovGroningen 00:52Partial coverage0 min—
Sun 25 OctGroningen 00:54No data—
Sun 18 OctGrijpskerk 00:360 min—
Sat 17 OctGrijpskerk 00:35No data—
Sun 11 OctGroningen 00:52Partial coverage0 min—
Sun 4 OctGroningen 00:54No data—
Sat 3 OctZuidhorn 00:40No data—
Sun 27 SeptGrijpskerk 00:36No data—
Sun 20 SeptGroningen 00:52No data—
Sun 13 SeptGroningen 00:52No data—
Sun 6 SeptGroningen 00:52No data—
Sun 30 AugGroningen 00:53No data—
Sun 23 AugGroningen 00:52No data—