Train Arriva 37164 Stavoren – Leeuwarden

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

✓ Today’s run finished

Today, last fix heading to Mantgum at 17:14 No data

  1. Stavoren16:18
  2. Koudum-Molkwerum16:22
  3. Workum16:30
  4. IJlst16:40
  5. Sneek16:44
  6. Mantgum16:59
  7. Leeuwarden17:07

Next service: tomorrow 16:18 from Stavoren · Sun 8 Nov

Next departure 16:18 tomorrow · Stavoren
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%
17/17 runs under 3 min
RT coverage: 4 full · 13 partial · 64 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=4
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • 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, 17 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
16:18on time on time
16:22— —
16:26— —
16:30— —
16:40— —
16:44 / 16:48— —
16:50 / 16:51— —
16:59 / 17:00— —
17: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
Sat 7 NovMantgum 17:14No data—
Fri 6 NovMantgum 17:14Partial coverage+1 min—
Thu 5 NovMantgum 17:14No data—
Wed 4 NovMantgum 17:14No data—
Tue 3 NovMantgum 17:14Partial coverage0 min—
Mon 2 NovMantgum 17:14Partial coverage0 min—
Sun 1 NovMantgum 17:140 min—
Sat 31 OctMantgum 17:140 min—
Fri 30 OctMantgum 17:16No data—
Thu 29 OctMantgum 17:14Partial coverage0 min—
Wed 28 OctMantgum 17:14Partial coverage0 min—
Tue 27 OctMantgum 17:14Partial coverage0 min—
Mon 26 OctMantgum 17:14No data—
Sun 25 OctMantgum 17:14No data—
Sat 24 OctMantgum 17:140 min—
Fri 23 OctMantgum 17:15No data—
Thu 22 OctMantgum 17:16No data—
Wed 21 OctMantgum 17:17No data—
Tue 20 OctMantgum 17:15Partial coverage0 min—
Mon 19 OctMantgum 17:14Partial coverage0 min—
Sun 18 OctMantgum 17:140 min—
Fri 9 OctMantgum 17:16Partial coverage+2 min+2 min
Thu 8 OctMantgum 17:14Partial coverage+1 min—
Wed 7 OctMantgum 17:14Partial coverage+1 min—
Tue 6 OctMantgum 17:14Partial coverage0 min—
Mon 5 OctMantgum 17:14Partial coverage0 min—
Sun 4 OctMantgum 17:14No data—
Sat 3 OctMantgum 17:14No data—
Fri 2 OctMantgum 17:17No data—
Thu 1 OctMantgum 17:14No data—