Train Arriva 37422 Leeuwarden – Groningen

Leeuwarden 06:50 → Groningen 07:36 Daily 0 h 46 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 06:50 from Leeuwarden · Thu 5 Nov

Next departure 06:50 today · Leeuwarden
On-time · 30 days
89%
25/28 runs under 3 min
RT coverage: 8 full · 20 partial · 1 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 8 full · 21 partial · 59 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
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

  • Tue 27 Oct Max en route +6 min · last fix heading to Zuidhorn +6 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Zuidhorn +5 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Zuidhorn +4 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Zuidhorn +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 25
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 60% T n=5
  • 80% W n=5
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

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