Train Arriva 37188 Stavoren – Leeuwarden

Stavoren 22:18 → Leeuwarden 23:08 Daily 0 h 50 min · 9 stops Arriva

Running now · updated 22:24

Position estimated from the timetable

Heading to Leeuwarden 0 min

Estimated arrival at Leeuwarden 23:08 · 70 km/h

  1. Stavoren22:18
  2. Koudum-Molkwerum22:22
  3. Workum22:30
  4. IJlst22:40
  5. Sneek22:44
  6. Mantgum22:59
  7. Leeuwarden23:08

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

On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 2 full · 3 partial · 4 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 2 full · 3 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 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, 5 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
22:18on time on time
22:22— —
22:26— —
22:30— —
22:40— —
22:44 / 22:48— —
22:51— —
22:59 / 23:00— —
23:08— —

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
Sun 15 NovKoudum-Molkwerum 22:19Partial coverage0 min—
Sat 14 NovMantgum 23:140 min—
Sun 8 NovMantgum 23:14Partial coverage0 min—
Sat 7 NovMantgum 23:140 min—
Sun 1 NovMantgum 23:14No data—
Sat 31 OctMantgum 23:14No data—
Sun 25 OctMantgum 23:14No data—
Sat 24 OctWorkum 22:45No data—
Sun 18 OctMantgum 23:14Partial coverage0 min—
Sun 4 OctMantgum 23:14No data—
Sat 3 OctMantgum 23:14No data—
Sun 27 SeptMantgum 23:14No data—
Sat 26 SeptMantgum 23:14No data—
Sun 20 SeptMantgum 23:14No data—
Sat 19 SeptMantgum 23:08No data—
Sun 13 SeptMantgum 23:14No data—
Sat 12 SeptMantgum 23:14No data—
Sun 6 SeptMantgum 23:14No data—
Sat 5 SeptSneek Noord 23:05No data—
Sun 30 AugMantgum 23:14No data—
Sat 29 AugIJlst 22:54No data—
Sun 23 AugMantgum 23:14No data—
Sat 22 AugMantgum 23:14No data—