Train Arriva 37444 Leeuwarden – Groningen Europapark

Leeuwarden 12:20 → Groningen Europapark 13:10 Mon, Tue, Wed, Thu, Fri, Sat 0 h 50 min · 10 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 12:20 from Leeuwarden · Thu 5 Nov

Next departure 12:20 today · Leeuwarden
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 14 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 13
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
12:20on time on time
12:23— —
12:29— —
12:33 / 12:34— —
12:37— —
12:43 / 12:44— —
12:51— —
12:57— —
13:06 / 13:08— —
13: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
Wed 4 NovGroningen 13:22Partial coverage0 min—
Tue 3 NovGroningen 13:22No data—
Mon 2 NovGroningen 13:22No data—
Sat 31 OctGroningen 13:22Partial coverage0 min—
Fri 30 OctGroningen 13:22No data—
Thu 29 OctGroningen 13:22No data—
Wed 28 OctGroningen 13:22Partial coverage0 min—
Tue 27 OctGroningen 13:22Partial coverage0 min—
Mon 26 OctGroningen 13:22No data—
Sat 24 OctGroningen 13:22Partial coverage0 min—
Fri 23 OctGroningen 13:22No data—
Thu 22 OctGroningen 13:22No data—
Wed 21 OctGroningen 13:22No data—
Tue 20 OctGroningen 13:22Partial coverage0 min—
Mon 19 OctGroningen 13:22Partial coverage0 min—
Sat 17 OctGrijpskerk 13:05No data—
Fri 16 OctGrijpskerk 13:06No data—
Thu 15 OctGroningen 13:22No data—
Wed 14 OctGroningen 13:22No data—
Tue 13 OctGroningen 13:22No data—
Mon 12 OctGroningen 13:24No data—
Sat 10 OctGroningen 13:24Partial coverage+3 min+3 min
Fri 9 OctGroningen 13:22Partial coverage+1 min+1 min
Thu 8 OctGroningen 13:22Partial coverage0 min—
Wed 7 OctGroningen 13:24Partial coverage+2 min+3 min
Tue 6 OctGroningen 13:23Partial coverage+2 min+2 min
Mon 5 OctGroningen 13:22Partial coverage0 min—
Sat 3 OctGroningen 13:22No data—
Fri 2 OctGroningen 13:22No data—
Thu 1 OctGroningen 13:22No data—