Train Arriva 37124 Stavoren – Leeuwarden

Stavoren 06:18 → Leeuwarden 07:07 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Mantgum at 07:14 0 min

  1. Stavoren06:18
  2. Koudum-Molkwerum06:22
  3. Workum06:30
  4. IJlst06:40
  5. Sneek06:44
  6. Mantgum06:59
  7. Leeuwarden07:07

Next service: tomorrow 06:18 from Stavoren · Thu 19 Nov

Next departure 06:18 tomorrow · Stavoren
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 0 full · 20 partial · 2 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 0 full · 25 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Tue 20 Oct Max en route +4 min · last fix heading to Mantgum +4 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Mantgum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 83% T n=6
  • 100% W n=6
  • 75% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
06:18on time on time
06:22— —
06:26— —
06:30— —
06:40— —
06:44 / 06:48— —
06:50 / 06:51— —
06:59 / 07:00— —
07: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
Wed 18 NovMantgum 07:14Partial coverage0 min—
Tue 17 NovMantgum 07:14Partial coverage0 min—
Mon 16 NovMantgum 07:14Partial coverage+3 min+3 min
Fri 13 NovMantgum 07:14Partial coverage+2 min+2 min
Thu 12 NovMantgum 07:14Partial coverage+4 min+4 min
Wed 11 NovMantgum 07:14Partial coverage0 min—
Tue 10 NovMantgum 07:14Partial coverage+1 min+1 min
Mon 9 NovMantgum 07:14Partial coverage0 min—
Fri 6 NovMantgum 07:14No data—
Thu 5 NovMantgum 07:14No data—
Wed 4 NovMantgum 07:14Partial coverage+1 min+1 min
Tue 3 NovMantgum 07:14Partial coverage0 min—
Mon 2 NovMantgum 07:14Partial coverage0 min—
Fri 30 OctMantgum 07:14Partial coverage+2 min+2 min
Thu 29 OctMantgum 07:14Partial coverage0 min—
Wed 28 OctMantgum 07:14Partial coverage0 min—
Tue 27 OctMantgum 07:14Partial coverage0 min—
Mon 26 OctMantgum 07:14Partial coverage+1 min+1 min
Fri 23 OctMantgum 07:15Partial coverage0 min—
Thu 22 OctMantgum 07:14Partial coverage+2 min+2 min
Wed 21 OctMantgum 07:14Partial coverage0 min—
Tue 20 OctMantgum 07:14Partial coverage+4 min+4 min
Mon 19 OctMantgum 07:14Partial coverage0 min—
Fri 9 OctMantgum 07:14Partial coverage0 min—
Thu 8 OctMantgum 07:14Partial coverage0 min—
Wed 7 OctMantgum 07:14Partial coverage0 min—
Tue 6 OctMantgum 07:15Partial coverage+1 min+1 min
Mon 5 OctMantgum 07:15No data—
Fri 2 OctMantgum 07:14No data—
Thu 1 OctMantgum 07:14No data—