Train Arriva 37446 Leeuwarden – Groningen

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

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 12:50 from Leeuwarden · Wed 18 Nov

Next departure 12:50 today · Leeuwarden
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 partial · 11 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 10 full · 17 partial · 61 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: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=2
  • 100% F n=2
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

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