Train Arriva 37117 Leeuwarden – Stavoren

Leeuwarden 08:23 → Stavoren 09:13 Daily 0 h 50 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Koudum-Molkwerum at 09:22 No data

  1. Leeuwarden08:23
  2. Mantgum08:30
  3. Sneek08:42
  4. IJlst08:49
  5. Workum08:59
  6. Koudum-Molkwerum09:08
  7. Stavoren09:13

Next service: tomorrow 08:23 from Leeuwarden · Sat 7 Nov

Next departure 08:23 tomorrow · Leeuwarden
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 3 full · 8 partial · 11 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 3 full · 10 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=1
  • 100% S n=2

Stops and timetable

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

Last 90 days, 13 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
08:23on time on time
08:30— —
08:38 / 08:39— —
08:42 / 08:46— —
08:49— —
08:59— —
09:03— —
09:08— —
09:13— —

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 6 NovKoudum-Molkwerum 09:22No data—
Thu 5 NovKoudum-Molkwerum 09:24No data—
Wed 4 NovKoudum-Molkwerum 09:22Partial coverage0 min—
Tue 3 NovKoudum-Molkwerum 09:19No data—
Mon 2 NovKoudum-Molkwerum 09:23No data—
Sun 1 NovKoudum-Molkwerum 09:220 min—
Sat 31 OctKoudum-Molkwerum 09:230 min—
Fri 30 OctKoudum-Molkwerum 09:23No data—
Thu 29 OctKoudum-Molkwerum 09:22No data—
Wed 28 OctKoudum-Molkwerum 09:22Partial coverage0 min—
Tue 27 OctKoudum-Molkwerum 09:22Partial coverage0 min—
Mon 26 OctKoudum-Molkwerum 09:22Partial coverage0 min—
Sun 25 OctKoudum-Molkwerum 09:22No data—
Sat 24 OctKoudum-Molkwerum 09:22No data—
Fri 23 OctKoudum-Molkwerum 09:22No data—
Thu 22 OctKoudum-Molkwerum 09:22No data—
Wed 21 OctKoudum-Molkwerum 09:22No data—
Tue 20 OctKoudum-Molkwerum 09:22Partial coverage0 min—
Mon 19 OctKoudum-Molkwerum 09:24Partial coverage0 min—
Sun 18 OctKoudum-Molkwerum 09:220 min—
Fri 9 OctKoudum-Molkwerum 09:23Partial coverage0 min—
Thu 8 OctKoudum-Molkwerum 09:22Partial coverage0 min—
Wed 7 OctKoudum-Molkwerum 09:22Partial coverage0 min—
Tue 6 OctKoudum-Molkwerum 09:22Partial coverage0 min—
Mon 5 OctKoudum-Molkwerum 09:22No data—
Sun 4 OctKoudum-Molkwerum 09:22No data—
Sat 3 OctKoudum-Molkwerum 09:22No data—
Fri 2 OctKoudum-Molkwerum 09:28No data—
Thu 1 OctKoudum-Molkwerum 09:22No data—
Wed 30 SeptKoudum-Molkwerum 09:22No data—