Train Arriva 37425 Groningen – Leeuwarden

Groningen 09:24 → Leeuwarden 10:11 Daily 0 h 47 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 09:24 from Groningen · Thu 5 Nov

Next departure 09:24 today · Groningen
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%
19/19 runs under 3 min
RT coverage: 7 full · 12 partial · 69 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

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

  • Early 0% · 0
  • On time 100% · 19
  • 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=4
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 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, 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
09:24on time on time
09:32≈ on time ≈ +1 min
09:38≈ on time ≈ +1 min
09:45≈ on time ≈ +1 min
09:51≈ on time ≈ +1 min
09:54 / 09:55≈ +1 min ≈ +1 min
10:00≈ +1 min ≈ +1 min
10:05≈ +1 min ≈ +1 min
10:11+1 min +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 NovLeeuwarden Camminghaburen 10:19Partial coverage+1 min—
Tue 3 NovLeeuwarden Camminghaburen 10:19Partial coverage0 min—
Mon 2 NovLeeuwarden Camminghaburen 10:19Partial coverage0 min—
Sun 1 NovLeeuwarden Camminghaburen 10:20+1 min—
Sat 31 OctLeeuwarden Camminghaburen 10:220 min+2 min
Fri 30 OctLeeuwarden Camminghaburen 10:21No data—
Thu 29 OctLeeuwarden Camminghaburen 10:21Partial coverage0 min—
Wed 28 OctLeeuwarden Camminghaburen 10:31Partial coverage0 min—
Tue 27 OctLeeuwarden Camminghaburen 10:32Partial coverage0 min—
Mon 26 OctLeeuwarden Camminghaburen 10:22No data—
Sun 25 OctLeeuwarden Camminghaburen 10:21No data—
Sat 24 OctLeeuwarden Camminghaburen 10:20+1 min—
Fri 23 OctLeeuwarden Camminghaburen 10:26No data—
Thu 22 OctLeeuwarden Camminghaburen 10:24No data—
Wed 21 OctLeeuwarden Camminghaburen 10:26No data—
Tue 20 OctLeeuwarden Camminghaburen 10:24Partial coverage0 min—
Mon 19 OctLeeuwarden Camminghaburen 10:22Partial coverage0 min—
Sun 18 OctLeeuwarden Camminghaburen 10:23+1 min—
Sat 17 OctLeeuwarden Camminghaburen 10:20+1 min—
Fri 16 OctLeeuwarden Camminghaburen 10:25No data—
Thu 15 OctLeeuwarden Camminghaburen 10:20No data—
Wed 14 OctLeeuwarden Camminghaburen 10:20No data—
Tue 13 OctLeeuwarden Camminghaburen 10:21No data—
Mon 12 OctLeeuwarden Camminghaburen 10:20No data—
Sun 11 OctLeeuwarden Camminghaburen 10:190 min—
Sat 10 OctLeeuwarden Camminghaburen 10:220 min+2 min
Fri 9 OctLeeuwarden Camminghaburen 10:22Partial coverage0 min+3 min
Thu 8 OctLeeuwarden Camminghaburen 10:23Partial coverage+2 min+4 min
Wed 7 OctLeeuwarden Camminghaburen 10:21Partial coverage0 min—
Tue 6 OctLeeuwarden Camminghaburen 10:21Partial coverage+1 min+1 min