Train Arriva 37156 Stavoren – Leeuwarden

Stavoren 14:18 → Leeuwarden 15:07 Daily 0 h 49 min · 9 stops Arriva

Running now · updated 14:07

Position estimated from the timetable

Heading to Leeuwarden No data

Estimated arrival at Leeuwarden 15:07

  1. Stavoren14:18
  2. Koudum-Molkwerum14:22
  3. Workum14:30
  4. IJlst14:40
  5. Sneek14:44
  6. Mantgum14:59
  7. Leeuwarden15:07
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 6 full · 13 partial · 11 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 7 full · 19 partial · 55 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 Leeuwarden, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
14:18on time on time
14:22≈ on time ≈ on time
14:26≈ on time ≈ on time
14:30≈ on time ≈ on time
14:40≈ on time ≈ on time
14:44 / 14:48≈ on time ≈ on time
14:50 / 14:51≈ on time ≈ on time
14:59 / 15:00≈ on time ≈ on time
15:07on time on time

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 NovStavoren 14:04No data—
Tue 17 NovMantgum 15:14Partial coverage+1 min+1 min
Mon 16 NovMantgum 15:15Partial coverage0 min—
Sun 15 NovMantgum 15:140 min—
Sat 14 NovMantgum 15:140 min—
Fri 13 NovMantgum 15:14Partial coverage+2 min+2 min
Thu 12 NovMantgum 15:15Partial coverage+1 min—
Wed 11 NovMantgum 15:14Partial coverage0 min—
Tue 10 NovMantgum 15:14Partial coverage+1 min+1 min
Mon 9 NovMantgum 15:14Partial coverage0 min—
Sun 8 NovMantgum 15:140 min—
Sat 7 NovMantgum 15:140 min—
Fri 6 NovMantgum 15:14No data—
Thu 5 NovMantgum 15:14No data—
Wed 4 NovMantgum 15:14Partial coverage0 min—
Tue 3 NovMantgum 15:15Partial coverage0 min—
Mon 2 NovMantgum 15:14Partial coverage0 min—
Sun 1 NovMantgum 15:150 min—
Sat 31 OctMantgum 15:140 min—
Fri 30 OctMantgum 15:14No data—
Thu 29 OctMantgum 15:14Partial coverage0 min—
Wed 28 OctMantgum 15:14Partial coverage0 min—
Tue 27 OctMantgum 15:15No data—
Mon 26 OctMantgum 15:14No data—
Sun 25 OctMantgum 15:14No data—
Sat 24 OctMantgum 15:14No data—
Fri 23 OctMantgum 15:14No data—
Thu 22 OctMantgum 15:14No data—
Wed 21 OctMantgum 15:14No data—
Tue 20 OctMantgum 15:45Partial coverage0 min—