Train Arriva 37157 Leeuwarden – Stavoren

Leeuwarden 18:23 → Stavoren 19:14 Daily 0 h 51 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Leeuwarden at 18:37 0 min

  1. Leeuwarden18:23
  2. Mantgum18:30
  3. Sneek18:42
  4. IJlst18:49
  5. Workum18:59
  6. Koudum-Molkwerum19:09
  7. Stavoren19:14

Next service: tomorrow 18:23 from Leeuwarden · Wed 18 Nov

Next departure 18:23 tomorrow · Leeuwarden
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 6 full · 7 partial · 5 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 7 full · 8 partial · 32 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: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=2
  • — W n=0
  • — T n=0
  • 100% F n=4
  • 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, 15 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
18:23on time on time
18:30≈ on time ≈ on time
18:38 / 18:39≈ on time ≈ on time
18:42 / 18:46≈ on time ≈ +1 min
18:49≈ on time ≈ +1 min
18:59 / 19:01≈ on time ≈ +1 min
19:04≈ on time ≈ +1 min
19:09≈ on time ≈ +1 min
19:14on time +2 min

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
Tue 17 NovLeeuwarden 18:37Partial coverage0 min—
Mon 16 NovLeeuwarden 18:35Partial coverage0 min—
Sun 15 NovKoudum-Molkwerum 19:230 min—
Sat 14 NovKoudum-Molkwerum 19:24+1 min+1 min
Fri 13 NovIJlst 19:03Partial coverage0 min+2 min
Sun 8 NovKoudum-Molkwerum 19:220 min—
Sat 7 NovKoudum-Molkwerum 19:220 min—
Fri 6 NovSneek 18:59Partial coverage+3 min+3 min
Sun 1 NovKoudum-Molkwerum 19:220 min—
Sat 31 OctKoudum-Molkwerum 19:24+2 min+2 min
Fri 30 OctIJlst 19:03No data—
Sun 25 OctKoudum-Molkwerum 19:22No data—
Sat 24 OctKoudum-Molkwerum 19:24No data—
Fri 23 OctKoudum-Molkwerum 19:23Partial coverage+1 min—
Thu 22 OctSneek Noord 18:53No data—
Wed 21 OctSneek Noord 18:53No data—
Tue 20 OctSneek 18:50Partial coverage0 min—
Mon 19 OctSneek Noord 18:53Partial coverage0 min—
Sun 18 OctKoudum-Molkwerum 19:220 min—
Fri 9 OctMantgum 18:44Partial coverage0 min—
Sun 4 OctKoudum-Molkwerum 19:22No data—
Sat 3 OctKoudum-Molkwerum 19:22No data—
Fri 2 OctSneek 19:00No data—
Sun 27 SeptKoudum-Molkwerum 19:24No data—
Sat 26 SeptKoudum-Molkwerum 19:22No data—
Fri 25 SeptMantgum 18:44No data—
Sun 20 SeptSneek Noord 18:54No data—
Sat 19 SeptSneek Noord 18:53No data—
Fri 18 SeptSneek 19:00No data—
Sun 13 SeptKoudum-Molkwerum 19:22No data—