Train Arriva 37442 Leeuwarden – Groningen

Leeuwarden 11:50 → Groningen 12: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 11:50 from Leeuwarden · Fri 6 Nov

Next departure 11:50 today · Leeuwarden
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 6 full · 10 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 6 full · 13 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 10 Oct Max en route +7 min · last fix heading to Groningen +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:50on time on time
11:53≈ on time ≈ on time
11:59≈ on time ≈ +1 min
12:03 / 12:04≈ on time ≈ +1 min
12:07≈ on time ≈ +2 min
12:13 / 12:14≈ on time ≈ +2 min
12:21≈ on time ≈ +3 min
12:27≈ +1 min ≈ +4 min
12:36+1 min +5 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 12:39No data—
Wed 4 NovZuidhorn 12:42Partial coverage+1 min+1 min
Tue 3 NovZuidhorn 12:39Partial coverage0 min—
Mon 2 NovZuidhorn 12:42Partial coverage0 min—
Sun 1 NovGroningen 12:530 min—
Sat 31 OctGroningen 12:53+1 min+1 min
Fri 30 OctZuidhorn 12:41No data—
Thu 29 OctZuidhorn 12:41Partial coverage0 min—
Wed 28 OctZuidhorn 12:41Partial coverage0 min—
Tue 27 OctZuidhorn 12:43Partial coverage0 min—
Mon 26 OctZuidhorn 12:42No data—
Sun 25 OctGroningen 12:55No data—
Sat 24 OctGroningen 12:520 min—
Fri 23 OctZuidhorn 12:41No data—
Thu 22 OctZuidhorn 12:43No data—
Wed 21 OctZuidhorn 12:41No data—
Tue 20 OctZuidhorn 12:41Partial coverage0 min—
Mon 19 OctZuidhorn 12:41Partial coverage0 min—
Sun 18 OctGrijpskerk 12:350 min—
Sat 17 OctGrijpskerk 12:36No data—
Fri 16 OctGrijpskerk 12:35No data—
Thu 15 OctZuidhorn 12:41No data—
Wed 14 OctZuidhorn 12:41No data—
Tue 13 OctZuidhorn 12:42No data—
Mon 12 OctZuidhorn 12:41No data—
Sun 11 OctGroningen 12:54+3 min+3 min
Sat 10 OctGroningen 12:57+7 min+7 min
Fri 9 OctZuidhorn 12:43Partial coverage+3 min+3 min
Thu 8 OctZuidhorn 12:41Partial coverage0 min—
Wed 7 OctZuidhorn 12:43Partial coverage+2 min+2 min