Train Arriva 37149 Leeuwarden – Stavoren

Leeuwarden 16:23 → Stavoren 17:14 Daily 0 h 51 min · 9 stops Arriva

Running now · updated 17:05

Heading to Stavoren No data

Estimated arrival at Stavoren 17:14 · 60 km/h

  1. Leeuwarden16:23
  2. Mantgum16:30
  3. Sneek16:42
  4. IJlst16:49
  5. Workum16:59
  6. Koudum-Molkwerum17:09
  7. Stavoren17:14
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 4 full · 9 partial · 9 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 4 full · 11 partial · 66 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

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

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

On-time by weekday

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

Stops and timetable

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

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