Train Arriva 37350 Leeuwarden – Groningen Europapark

Leeuwarden 13:46 → Groningen Europapark 14:25 Mon, Tue, Wed, Thu, Fri, Sat 0 h 39 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to Groningen at 14:37 +1 min

  1. Leeuwarden13:46
  2. Feanwâlden13:55
  3. Buitenpost14:03
  4. Groningen14:21
  5. Groningen Europapark14:25

Next service: Monday 13:46 from Leeuwarden · Mon 9 Nov

Next departure 13:46 Monday · Leeuwarden
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 18 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 65 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 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

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

  • Early 0% · 0
  • On time 100% · 11
  • 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=2
  • 100% W n=3
  • 100% T n=1
  • — F n=0
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 11 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
13:46on time on time
13:55— —
14:03— —
14:21 / 14:22— —
14:25— —

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 NovGroningen 14:37Partial coverage+1 min+1 min
Fri 6 NovGroningen 14:37No data—
Thu 5 NovGroningen 14:37No data—
Wed 4 NovGroningen 14:38Partial coverage+2 min+2 min
Tue 3 NovGroningen 14:34No data—
Mon 2 NovGroningen 14:34No data—
Sat 31 OctGroningen 14:36No data—
Fri 30 OctGroningen 14:36No data—
Thu 29 OctGroningen 14:37No data—
Wed 28 OctGroningen 14:37Partial coverage0 min—
Tue 27 OctGroningen 14:38Partial coverage0 min—
Mon 26 OctGroningen 14:36No data—
Sat 24 OctGroningen 14:37Partial coverage+1 min—
Fri 23 OctGroningen 14:37No data—
Thu 22 OctGroningen 14:38No data—
Wed 21 OctGroningen 14:36No data—
Tue 20 OctGroningen 14:36Partial coverage0 min—
Mon 19 OctGroningen 14:36Partial coverage0 min—
Sat 17 OctBuitenpost 14:20No data—
Fri 16 OctBuitenpost 14:17No data—
Thu 15 OctGroningen 14:39No data—
Wed 14 OctGroningen 14:37No data—
Tue 13 OctGroningen 14:38No data—
Mon 12 OctGroningen 14:38No data—
Sat 10 OctGroningen 14:36Partial coverage0 min—
Fri 9 OctGroningen 14:36No data—
Thu 8 OctGroningen 14:37Partial coverage+1 min+1 min
Wed 7 OctGroningen 14:39Partial coverage+2 min+3 min
Tue 6 OctGroningen 14:36No data—
Mon 5 OctGroningen 14:37Partial coverage+1 min+1 min