Train Arriva 37113 Leeuwarden – Stavoren

Leeuwarden 07:23 → Stavoren 08:14 Mon, Tue, Wed, Thu, Fri, Sat 0 h 51 min · 8 stops Arriva

✓ Today’s run finished

Today, last fix heading to Koudum-Molkwerum at 08:24 +1 min

  1. Leeuwarden07:23
  2. Mantgum07:30
  3. Sneek07:41
  4. Workum07:59
  5. Hindeloopen08:04
  6. Koudum-Molkwerum08:09
  7. Stavoren08:14

Next service: tomorrow 07:23 from Leeuwarden · Fri 20 Nov

Next departure 07:23 tomorrow · Leeuwarden
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 2 full · 15 partial · 9 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 2 full · 20 partial · 47 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Stavoren, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 12 Nov Max en route +7 min · last fix heading to Koudum-Molkwerum +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 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
  • 67% T n=3
  • 100% F n=4
  • 100% S n=2
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
07:23on time on time
07:30— —
07:41 / 07:46— —
07:49— —
07:59 / 08:01— —
08:04— —
08:09— —
08:14— —

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
Thu 19 NovKoudum-Molkwerum 08:24Partial coverage+1 min+1 min
Wed 18 NovKoudum-Molkwerum 08:24Partial coverage+1 min—
Tue 17 NovKoudum-Molkwerum 08:24Partial coverage+2 min+2 min
Mon 16 NovKoudum-Molkwerum 08:24Partial coverage+2 min+2 min
Sat 14 NovKoudum-Molkwerum 08:24+2 min+2 min
Fri 13 NovKoudum-Molkwerum 08:24Partial coverage+2 min+2 min
Thu 12 NovKoudum-Molkwerum 08:29Partial coverage+7 min+7 min
Wed 11 NovKoudum-Molkwerum 08:24Partial coverage+1 min+1 min
Tue 10 NovKoudum-Molkwerum 08:24Partial coverage+1 min—
Mon 9 NovKoudum-Molkwerum 08:23Partial coverage0 min—
Sat 7 NovKoudum-Molkwerum 08:22No data—
Fri 6 NovKoudum-Molkwerum 08:23No data—
Thu 5 NovKoudum-Molkwerum 08:27No data—
Wed 4 NovKoudum-Molkwerum 08:24Partial coverage+1 min+2 min
Tue 3 NovKoudum-Molkwerum 08:24No data—
Mon 2 NovKoudum-Molkwerum 08:24No data—
Sat 31 OctKoudum-Molkwerum 08:22No data—
Fri 30 OctKoudum-Molkwerum 08:24Partial coverage0 min—
Thu 29 OctKoudum-Molkwerum 08:24No data—
Wed 28 OctKoudum-Molkwerum 08:24Partial coverage0 min—
Tue 27 OctKoudum-Molkwerum 08:24Partial coverage0 min—
Mon 26 OctKoudum-Molkwerum 08:24Partial coverage0 min—
Sat 24 OctKoudum-Molkwerum 08:220 min—
Fri 23 OctKoudum-Molkwerum 08:23Partial coverage0 min—
Thu 22 OctKoudum-Molkwerum 08:24No data—
Wed 21 OctKoudum-Molkwerum 08:23No data—
Tue 20 OctKoudum-Molkwerum 08:25Partial coverage0 min—
Mon 19 OctKoudum-Molkwerum 08:24Partial coverage0 min—
Fri 9 OctKoudum-Molkwerum 08:23Partial coverage0 min—
Thu 8 OctKoudum-Molkwerum 08:25Partial coverage+1 min+1 min