Train Arriva 37488 Leeuwarden – Groningen

Leeuwarden 23:19 → Groningen 00:05 Mon, Tue, Wed, Thu, Fri, Sat 0 h 46 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November +3 min

Next service: today 23:19 from Leeuwarden · Thu 5 Nov

Next departure 23:19 today · Leeuwarden
On-time · 30 days
—
Too little data (1/3 runs with data)
RT coverage: 1 full · 0 partial · 2 no data
On-time · 90 days
—
Too little data (1/9 runs with data)
RT coverage: 1 full · 0 partial · 8 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

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

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

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

On-time by weekday

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

Stops and timetable

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

Not enough runs yet to work out the usual delay by stop.

StopSched.
23:19
23:22
23:29
23:32 / 23:33
23:36
23:42 / 23:43
23:50
23:56
00:05

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.

Recent runs

DateLast stopFinalMax
Wed 4 Nov— 00:09+3 min+3 min
Sat 31 OctLeeuwarden Camminghaburen 23:36No data—
Sat 17 OctGrijpskerk 00:04No data—
Sat 3 OctZuidhorn 00:10No data—
Sat 26 SeptBuitenpost 23:57No data—
Sat 12 SeptBuitenpost 23:57No data—
Sat 22 AugZuidhorn 00:10No data—
Sat 15 AugLeeuwarden Camminghaburen 23:36No data—
Sat 8 AugLeeuwarden Camminghaburen 23:36No data—