Train Arriva 37160 Stavoren – Leeuwarden

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 15:18 from Stavoren · Sat 7 Nov

Next departure 15:18 today · Stavoren
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 3 full · 6 partial · 12 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 3 full · 10 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: 0 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

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=2
  • 100% S n=1

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
15:18on time on time
15:22— —
15:26— —
15:30— —
15:40— —
15:44 / 15:48— —
15:50 / 15:51— —
15:59 / 16:00— —
16:07— —

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