Train Arriva 37109 Leeuwarden – Stavoren

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

✓ Today’s run finished

Today, last fix heading to Koudum-Molkwerum at 07:24 0 min

  1. Leeuwarden06:23
  2. Mantgum06:30
  3. Sneek06:42
  4. IJlst06:49
  5. Workum06:59
  6. Koudum-Molkwerum07:09
  7. Stavoren07:14

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

Next departure 06:23 tomorrow · Leeuwarden
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 4 full · 19 partial · 3 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 4 full · 25 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
06:23on time on time
06:30— —
06:38 / 06:39— —
06:42 / 06:46— —
06:49— —
06:59 / 07:01— —
07:04— —
07:09— —
07: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 07:24Partial coverage0 min—
Wed 18 NovKoudum-Molkwerum 07:24Partial coverage0 min—
Tue 17 NovKoudum-Molkwerum 07:23Partial coverage0 min—
Mon 16 NovKoudum-Molkwerum 07:24Partial coverage+2 min+2 min
Sat 14 NovKoudum-Molkwerum 07:220 min—
Fri 13 NovKoudum-Molkwerum 07:24Partial coverage+2 min+2 min
Thu 12 NovKoudum-Molkwerum 07:24Partial coverage+2 min+3 min
Wed 11 NovKoudum-Molkwerum 07:24Partial coverage0 min—
Tue 10 NovKoudum-Molkwerum 07:24Partial coverage+2 min+2 min
Mon 9 NovKoudum-Molkwerum 07:23Partial coverage0 min—
Sat 7 NovKoudum-Molkwerum 07:220 min—
Fri 6 NovKoudum-Molkwerum 07:23No data—
Thu 5 NovKoudum-Molkwerum 07:23No data—
Wed 4 NovKoudum-Molkwerum 07:24Partial coverage+1 min—
Tue 3 NovKoudum-Molkwerum 07:24Partial coverage+1 min+1 min
Mon 2 NovKoudum-Molkwerum 07:24No data—
Sat 31 OctKoudum-Molkwerum 07:23+1 min+1 min
Fri 30 OctKoudum-Molkwerum 07:25Partial coverage+2 min+2 min
Thu 29 OctKoudum-Molkwerum 07:24Partial coverage+1 min+1 min
Wed 28 OctKoudum-Molkwerum 07:24Partial coverage+1 min—
Tue 27 OctKoudum-Molkwerum 07:23Partial coverage0 min—
Mon 26 OctKoudum-Molkwerum 07:23Partial coverage0 min—
Sat 24 OctKoudum-Molkwerum 07:220 min—
Fri 23 OctKoudum-Molkwerum 07:24Partial coverage0 min—
Thu 22 OctKoudum-Molkwerum 07:23Partial coverage0 min—
Wed 21 OctKoudum-Molkwerum 07:25Partial coverage+1 min+1 min
Tue 20 OctKoudum-Molkwerum 07:24Partial coverage+1 min+1 min
Mon 19 OctKoudum-Molkwerum 07:23Partial coverage0 min—
Fri 9 OctKoudum-Molkwerum 07:23Partial coverage0 min—
Thu 8 OctKoudum-Molkwerum 07:23Partial coverage+1 min—