Train Arriva 37015 Leeuwarden → Sneek

Leeuwarden 07:53 → Sneek 08:12 Mon, Tue, Wed, Thu, Fri, Sat 0 h 19 min · 4 stops Arriva

Arriva 37015 Leeuwarden–Sneek: final delay under 3 min on 15 of its 15 runs with data in the last 30 days (100%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 10:24 (GMT+1).

It does not run today

Last recorded run: Saturday 21 November +1 min

Next service: tomorrow 07:53 from Leeuwarden · Mon 23 Nov

Next departure 07:53 tomorrow · Leeuwarden
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 13 full · 2 partial · 10 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 18 full · 2 partial · 49 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
07:53on time on time
08:00≈ on time ≈ +1 min
08:09≈ +1 min ≈ +2 min
08:12+1 min +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
Sat 21 NovSneek Noord 08:24Partial coverage+1 min—
Fri 20 NovSneek Noord 08:24+2 min+3 min
Thu 19 NovSneek Noord 08:24+1 min+1 min
Wed 18 NovSneek Noord 08:24+1 min+1 min
Tue 17 NovSneek Noord 08:24+2 min+2 min
Mon 16 NovSneek Noord 08:27+3 min+4 min
Sat 14 NovSneek Noord 08:24Partial coverage0 min—
Fri 13 NovSneek Noord 08:24+2 min+2 min
Thu 12 NovSneek Noord 08:24+2 min+2 min
Wed 11 NovSneek Noord 08:240 min—
Tue 10 NovSneek Noord 08:24+1 min+1 min
Mon 9 NovSneek Noord 08:240 min—
Sat 7 NovSneek Noord 08:23No data—
Fri 6 NovSneek Noord 08:23No data—
Thu 5 NovSneek Noord 08:24No data—
Wed 4 NovSneek Noord 08:24+1 min—
Tue 3 NovSneek Noord 08:24No data—
Mon 2 NovSneek Noord 08:24No data—
Sat 31 OctSneek Noord 08:23No data—
Fri 30 OctSneek Noord 08:25No data—
Thu 29 OctSneek Noord 08:23No data—
Wed 28 OctSneek Noord 08:250 min—
Tue 27 OctSneek Noord 08:230 min—
Mon 26 OctSneek Noord 08:24No data—
Sat 24 OctSneek Noord 08:23No data—
Fri 23 OctSneek Noord 08:24No data—
Thu 22 OctSneek Noord 08:24No data—
Wed 21 OctSneek Noord 08:27No data—
Tue 20 OctSneek Noord 08:260 min—
Mon 19 OctSneek Noord 08:250 min—