Train Arriva 37450 Leeuwarden – Groningen

Leeuwarden 13:50 → Groningen 14:36 Daily 0 h 46 min · 9 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:50 from Leeuwarden · Fri 6 Nov

Next departure 13:50 today · Leeuwarden
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 5 full · 6 partial · 18 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 5 full · 9 partial · 74 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Groningen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 5 Oct Max en route +15 min · last fix heading to Zuidhorn +15 min
  • Wed 7 Oct Max en route +7 min · last fix heading to Zuidhorn +7 min

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

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
13:50on time on time
13:53≈ on time ≈ on time
13:59≈ on time ≈ on time
14:03 / 14:04≈ on time ≈ on time
14:07≈ on time ≈ on time
14:13 / 14:14≈ on time ≈ on time
14:21≈ on time ≈ +1 min
14:27≈ on time ≈ +1 min
14:36on time +1 min

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
Thu 5 NovZuidhorn 14:39No data—
Wed 4 NovZuidhorn 14:39Partial coverage0 min—
Tue 3 NovZuidhorn 14:39No data—
Mon 2 NovZuidhorn 14:43No data—
Sun 1 NovGroningen 14:53No data—
Sat 31 OctGroningen 14:520 min—
Fri 30 OctZuidhorn 14:41No data—
Thu 29 OctZuidhorn 14:41No data—
Wed 28 OctZuidhorn 14:41Partial coverage0 min—
Tue 27 OctZuidhorn 14:42No data—
Mon 26 OctZuidhorn 14:41No data—
Sun 25 OctGroningen 14:53No data—
Sat 24 OctGroningen 14:53+1 min+1 min
Fri 23 OctZuidhorn 14:41No data—
Thu 22 OctZuidhorn 14:43No data—
Wed 21 OctZuidhorn 14:41No data—
Tue 20 OctZuidhorn 14:42Partial coverage0 min—
Mon 19 OctZuidhorn 14:42Partial coverage0 min—
Sun 18 OctGrijpskerk 14:350 min—
Sat 17 OctGrijpskerk 14:35No data—
Fri 16 OctGrijpskerk 14:36No data—
Thu 15 OctZuidhorn 14:42No data—
Wed 14 OctZuidhorn 14:41No data—
Tue 13 OctZuidhorn 14:41No data—
Mon 12 OctZuidhorn 14:41No data—
Sun 11 OctGroningen 14:520 min—
Sat 10 OctGroningen 14:520 min—
Fri 9 OctZuidhorn 14:41Partial coverage0 min—
Thu 8 OctZuidhorn 14:41Partial coverage0 min—
Wed 7 OctZuidhorn 14:47Partial coverage+7 min+7 min