Train Arriva 37151 Leeuwarden – Stavoren

Leeuwarden 16:53 → Stavoren 17:44 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Koudum-Molkwerum at 17:53 0 min

  1. Leeuwarden16:53
  2. Mantgum16:59
  3. Sneek17:12
  4. IJlst17:19
  5. Workum17:29
  6. Koudum-Molkwerum17:39
  7. Stavoren17:44

Next service: Monday 16:53 from Leeuwarden · Mon 23 Nov

Next departure 16:53 Monday · Leeuwarden
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 8 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 0 full · 20 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=4
  • 100% W n=5
  • 100% T n=3
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
16:53on time on time
16:59 / 17:00— —
17:08 / 17:09— —
17:12 / 17:16— —
17:19— —
17:29 / 17:31— —
17:34— —
17:39— —
17:44— —

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