Train Arriva 38055 Leeuwarden – Sneek

Leeuwarden 17:37 → Sneek 17:54 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 3 stops Arriva

It does not run today

Last recorded run: Friday 6 November +8 min

Next service: tomorrow 17:37 from Leeuwarden · Mon 9 Nov

Next departure 17:37 tomorrow · Leeuwarden
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 0 full · 5 partial · 9 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 1 full · 9 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Sneek, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 6 Nov Max en route +8 min · last fix heading to Sneek Noord +8 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Sneek Noord +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 8
  • 3–10 min 20% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 10 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
17:37on time +2 min
17:51 / 17:52— —
17:54— —

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 NovSneek Noord 18:04Partial coverage+8 min+8 min
Thu 5 NovSneek Noord 18:04No data—
Wed 4 NovSneek Noord 18:04Partial coverage0 min—
Tue 3 NovSneek Noord 18:04No data—
Mon 2 NovSneek Noord 18:04No data—
Fri 30 OctSneek Noord 18:06No data—
Thu 29 OctSneek Noord 18:06No data—
Wed 28 OctSneek Noord 18:06Partial coverage0 min—
Tue 27 OctSneek Noord 18:06Partial coverage0 min—
Mon 26 OctSneek Noord 18:06No data—
Fri 23 OctSneek Noord 18:06No data—
Thu 22 OctSneek Noord 18:06No data—
Wed 21 OctSneek Noord 18:06No data—
Mon 19 OctSneek Noord 18:06Partial coverage0 min—
Fri 9 OctSneek Noord 18:06Partial coverage+4 min+4 min
Thu 8 OctSneek Noord 18:070 min—
Wed 7 OctSneek Noord 18:06Partial coverage0 min—
Tue 6 OctSneek Noord 18:06Partial coverage+2 min+2 min
Mon 5 OctSneek Noord 18:06Partial coverage0 min—
Fri 2 OctSneek Noord 18:06No data—
Thu 1 OctSneek Noord 18:06No data—
Wed 30 SeptSneek Noord 18:06No data—
Tue 29 SeptSneek Noord 18:06No data—
Mon 28 SeptSneek Noord 18:06No data—
Fri 25 SeptSneek Noord 18:06No data—
Thu 24 SeptSneek Noord 18:07No data—
Wed 23 SeptSneek Noord 18:06No data—
Tue 22 SeptSneek Noord 18:06No data—
Mon 21 SeptSneek Noord 18:06No data—
Fri 18 SeptSneek Noord 18:06No data—