Train Arriva 37435 Groningen Europapark – Leeuwarden

Groningen Europapark 11:49 → Leeuwarden 12:41 Mon, Tue, Wed, Thu, Fri, Sat 0 h 52 min · 10 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 11:49 from Groningen Europapark · Sat 7 Nov

Next departure 11:49 today · Groningen Europapark
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 15 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Leeuwarden, 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=2
  • 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, 14 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:49on time on time
11:52 / 11:54— —
12:02— —
12:08— —
12:15— —
12:21— —
12:24 / 12:25— —
12:30— —
12:35— —
12:41— —

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
Fri 6 NovLeeuwarden Camminghaburen 12:49No data—
Thu 5 NovLeeuwarden Camminghaburen 12:49No data—
Wed 4 NovLeeuwarden Camminghaburen 12:49Partial coverage+1 min—
Tue 3 NovLeeuwarden Camminghaburen 12:52No data—
Mon 2 NovLeeuwarden Camminghaburen 12:49No data—
Sat 31 OctLeeuwarden Camminghaburen 12:50Partial coverage+1 min—
Fri 30 OctLeeuwarden Camminghaburen 12:50No data—
Thu 29 OctLeeuwarden Camminghaburen 12:50Partial coverage0 min—
Wed 28 OctLeeuwarden Camminghaburen 12:52Partial coverage0 min—
Tue 27 OctLeeuwarden Camminghaburen 12:52Partial coverage0 min—
Mon 26 OctLeeuwarden Camminghaburen 12:50No data—
Sat 24 OctLeeuwarden Camminghaburen 12:49Partial coverage0 min—
Fri 23 OctLeeuwarden Camminghaburen 12:50No data—
Thu 22 OctLeeuwarden Camminghaburen 12:51No data—
Wed 21 OctLeeuwarden Camminghaburen 12:50No data—
Tue 20 OctLeeuwarden Camminghaburen 12:50Partial coverage0 min—
Mon 19 OctLeeuwarden Camminghaburen 12:50Partial coverage0 min—
Sat 17 OctLeeuwarden Camminghaburen 12:49No data—
Fri 16 OctLeeuwarden Camminghaburen 12:49No data—
Thu 15 OctLeeuwarden Camminghaburen 12:52No data—
Wed 14 OctLeeuwarden Camminghaburen 12:50No data—
Tue 13 OctLeeuwarden Camminghaburen 12:50No data—
Mon 12 OctLeeuwarden Camminghaburen 12:50No data—
Sat 10 OctLeeuwarden Camminghaburen 12:50Partial coverage+1 min—
Fri 9 OctLeeuwarden Camminghaburen 12:49Partial coverage0 min—
Thu 8 OctLeeuwarden Camminghaburen 12:52Partial coverage0 min+2 min
Wed 7 OctLeeuwarden Camminghaburen 12:50Partial coverage0 min—
Tue 6 OctLeeuwarden Camminghaburen 12:50Partial coverage+1 min—
Mon 5 OctLeeuwarden Camminghaburen 12:50Partial coverage0 min—
Sat 3 OctLeeuwarden Camminghaburen 12:51No data—