Train Arriva 37145 Leeuwarden – Stavoren

Leeuwarden 15:23 → Stavoren 16:13 Daily 0 h 50 min · 9 stops Arriva

Running now · updated 16:16

Position estimated from the timetable

Heading to Stavoren +1 min

Estimated arrival at Stavoren 16:14

  1. Leeuwarden15:23
  2. Mantgum15:30
  3. Sneek15:42
  4. IJlst15:49
  5. Workum15:59
  6. Koudum-Molkwerum16:08
  7. Stavoren16:13

Today it is running worse than usual: typical arrival delay is 0 min; 94% of the last 18 runs arrived on time.

On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 0 full · 18 partial · 12 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 0 full · 24 partial · 57 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

Worst days

  • Fri 13 Nov Max en route +4 min · last fix heading to Koudum-Molkwerum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 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=5
  • 100% T n=3
  • 50% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

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