Train Arriva 37473 Groningen – Leeuwarden

Groningen 21:24 → Leeuwarden 22:11 Daily 0 h 47 min · 9 stops Arriva

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 21:24 from Groningen · Sun 8 Nov

Next departure 21:24 today · Groningen
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 4 full · 2 partial · 4 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 4 full · 2 partial · 20 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: +4 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

Worst days

  • Sun 11 Oct Max en route +5 min · last fix heading to Leeuwarden Camminghaburen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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
21:24on time on time
21:32— —
21:38— —
21:45— —
21:51— —
21:54 / 21:55— —
22:00— —
22:05— —
22:11— —

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
Sat 7 NovLeeuwarden Camminghaburen 22:19Partial coverage+1 min—
Sun 1 NovLeeuwarden Camminghaburen 22:19+2 min+2 min
Sat 31 OctLeeuwarden Camminghaburen 22:19No data—
Mon 26 Oct— 22:140 min—
Sun 25 OctLeeuwarden Camminghaburen 22:20No data—
Sat 24 OctLeeuwarden Camminghaburen 22:19No data—
Sun 18 OctLeeuwarden Camminghaburen 22:190 min—
Sat 17 OctLeeuwarden Camminghaburen 22:20No data—
Sun 11 OctLeeuwarden Camminghaburen 22:25+5 min+5 min
Sat 10 OctLeeuwarden Camminghaburen 22:19Partial coverage+1 min+2 min
Sun 4 OctLeeuwarden Camminghaburen 22:19No data—
Sat 3 OctLeeuwarden Camminghaburen 22:17No data—
Sun 27 SeptLeeuwarden Camminghaburen 22:21No data—
Sat 26 SeptLeeuwarden Camminghaburen 22:57No data—
Sun 20 SeptLeeuwarden Camminghaburen 22:19No data—
Sat 19 SeptLeeuwarden Camminghaburen 22:19No data—
Sun 13 SeptLeeuwarden Camminghaburen 22:19No data—
Sat 12 SeptLeeuwarden Camminghaburen 22:20No data—
Sun 6 SeptLeeuwarden Camminghaburen 22:20No data—
Sat 5 SeptLeeuwarden Camminghaburen 22:19No data—
Sun 30 AugLeeuwarden Camminghaburen 22:21No data—
Sat 29 AugLeeuwarden Camminghaburen 22:19No data—
Sun 23 AugLeeuwarden Camminghaburen 22:20No data—
Sat 22 AugLeeuwarden Camminghaburen 22:19No data—
Sun 16 AugLeeuwarden Camminghaburen 22:20No data—
Sat 15 AugLeeuwarden Camminghaburen 22:15No data—