Train Arriva 37340 Leeuwarden – Groningen Europapark

Leeuwarden 11:16 → Groningen Europapark 11:55 Daily 0 h 39 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to Groningen at 12:12 +6 min

  1. Leeuwarden11:16
  2. Feanwâlden11:25
  3. Zuidhorn11:41
  4. Groningen11:51
  5. Groningen Europapark11:55

Next service: tomorrow 11:16 from Leeuwarden · Sun 8 Nov

Next departure 11:16 tomorrow · Leeuwarden
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 2 full · 9 partial · 18 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 2 full · 11 partial · 74 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

Worst days

  • Sat 7 Nov Max en route +6 min · last fix heading to Groningen +6 min

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 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
11:16on time on time
11:25— —
11:41— —
11:51 / 11:52— —
11:55— —

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 12:12Partial coverage+6 min+6 min
Fri 6 NovGroningen 12:04No data—
Thu 5 NovGroningen 12:07No data—
Wed 4 NovGroningen 12:04Partial coverage0 min—
Tue 3 NovGroningen 12:04No data—
Mon 2 NovGroningen 12:04No data—
Sun 1 NovGroningen 12:100 min—
Sat 31 OctGroningen 12:06No data—
Fri 30 OctGroningen 12:07No data—
Thu 29 OctGroningen 12:06No data—
Wed 28 OctGroningen 12:06Partial coverage0 min—
Tue 27 OctGroningen 12:06Partial coverage0 min—
Mon 26 OctGroningen 12:06No data—
Sun 25 OctGroningen 12:09No data—
Sat 24 OctGroningen 12:08Partial coverage+2 min+2 min
Fri 23 OctGroningen 12:06No data—
Thu 22 OctGroningen 12:08No data—
Wed 21 OctGroningen 12:07No data—
Tue 20 OctGroningen 12:06Partial coverage0 min—
Mon 19 OctGroningen 12:07Partial coverage0 min—
Sat 17 OctFeanwâlden 11:40No data—
Fri 16 OctFeanwâlden 11:40No data—
Thu 15 OctGroningen 12:08No data—
Wed 14 OctGroningen 12:07No data—
Tue 13 OctGroningen 12:07No data—
Mon 12 OctGroningen 12:08No data—
Sun 11 OctGroningen 12:09+1 min—
Sat 10 OctGroningen 12:08Partial coverage+1 min+2 min
Fri 9 OctGroningen 12:06Partial coverage0 min+1 min
Thu 8 OctGroningen 12:08Partial coverage+2 min+2 min