Train Arriva 37463 Groningen → Leeuwarden

Groningen 18:54 → Leeuwarden 19:41 Mon, Tue, Wed, Thu, Fri, Sat 0 h 47 min · 9 stops Arriva

It has not run yet today

Last recorded run: Friday 20 November +4 min

Next service: today 18:54 from Groningen · Sat 21 Nov

Next departure 18:54 today · Groningen
On-time · 30 days
60%
3/5 runs under 3 min
RT coverage: 2 full · 3 partial · 3 no data
On-time · 90 days
67%
4/6 runs under 3 min
RT coverage: 3 full · 3 partial · 14 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +3 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Fri 13 Nov Max en route +8 min · last fix heading to Groningen +8 min
  • Fri 20 Nov Max en route +4 min · last fix heading to Buitenpost +4 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 67% · 4
  • 3–10 min 33% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
18:54on time +1 min
19:02— —
19:08— —
19:15— —
19:21— —
19:24 / 19:25— —
19:30— —
19:35— —
19:41— —

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
Fri 20 NovBuitenpost 19:29Partial coverage+4 min+4 min
Sat 14 NovFeanwâlden 19:39No data—
Fri 13 NovGroningen 19:08Partial coverage+8 min+8 min
Sat 7 NovLeeuwarden Camminghaburen 19:49+1 min—
Sat 31 OctLeeuwarden Camminghaburen 19:52+1 min+3 min
Fri 30 OctGroningen 19:08No data—
Sat 24 OctLeeuwarden Camminghaburen 19:53No data—
Fri 23 OctFeanwâlden 19:39Partial coverage+3 min+3 min
Sat 17 OctLeeuwarden Camminghaburen 19:50No data—
Fri 16 OctLeeuwarden Camminghaburen 19:49No data—
Wed 14 OctLeeuwarden Camminghaburen 19:49No data—
Sat 10 OctLeeuwarden Camminghaburen 19:500 min—
Sat 3 OctLeeuwarden Camminghaburen 19:50No data—
Sat 26 SeptLeeuwarden Camminghaburen 19:50No data—
Sat 19 SeptLeeuwarden Camminghaburen 19:51No data—
Sat 12 SeptLeeuwarden Camminghaburen 20:00No data—
Sat 5 SeptLeeuwarden Camminghaburen 19:50No data—
Sat 29 AugLeeuwarden Camminghaburen 19:52No data—
Fri 28 AugFeanwâlden 19:39No data—
Wed 26 AugGrijpskerk 19:22No data—