Train Arriva 37042 Sneek – Leeuwarden

Sneek 11:18 → Leeuwarden 11:38 Mon, Tue, Wed, Thu, Fri, Sat 0 h 20 min · 4 stops Arriva

✓ Today’s run finished

Today, last fix heading to Mantgum at 11:44 No data

  1. Sneek11:18
  2. Sneek Noord11:21
  3. Mantgum11:29
  4. Leeuwarden11:38

Next service: tomorrow 11:18 from Sneek · Sat 7 Nov

Next departure 11:18 tomorrow · Sneek
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 14 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 63 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

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=2
  • — T n=0
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 6 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
11:18on time on time
11:21— —
11:29 / 11:30— —
11:38— —

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 11:44No data—
Thu 5 NovMantgum 11:44No data—
Wed 4 NovMantgum 11:44Partial coverage0 min—
Tue 3 NovMantgum 11:44No data—
Mon 2 NovMantgum 11:44No data—
Sat 31 OctMantgum 11:44No data—
Fri 30 OctMantgum 11:44No data—
Thu 29 OctMantgum 11:44No data—
Wed 28 OctMantgum 11:44Partial coverage0 min—
Tue 27 OctMantgum 11:44Partial coverage0 min—
Mon 26 OctMantgum 11:45No data—
Sat 24 OctMantgum 11:44No data—
Fri 23 OctMantgum 11:44No data—
Thu 22 OctMantgum 11:44No data—
Wed 21 OctMantgum 11:44No data—
Tue 20 OctMantgum 11:44Partial coverage0 min—
Mon 19 OctMantgum 11:44Partial coverage0 min—
Fri 9 OctMantgum 11:45No data—
Thu 8 OctMantgum 11:44No data—
Wed 7 OctSneek 12:01No data—
Tue 6 OctMantgum 11:45Partial coverage0 min—
Mon 5 OctMantgum 11:46No data—
Sat 3 OctMantgum 11:44No data—
Fri 2 OctMantgum 11:44No data—
Thu 1 OctMantgum 11:44No data—
Wed 30 SeptMantgum 11:45No data—
Tue 29 SeptMantgum 11:44No data—
Mon 28 SeptMantgum 11:44No data—
Sat 26 SeptMantgum 11:44No data—
Fri 25 SeptMantgum 11:44No data—