Train Arriva 37066 Sneek – Leeuwarden

Sneek 17:18 → Leeuwarden 17:38 Sat 0 h 20 min · 4 stops Arriva

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: Saturday 17:18 from Sneek · Sat 14 Nov

Full trip card
Next departure 17:18 Saturday · Sneek
On-time · 30 days
—
Too little data (1/3 runs with data)
RT coverage: 0 full · 1 partial · 2 no data
On-time · 90 days
—
Too little data (1/11 runs with data)
RT coverage: 0 full · 1 partial · 10 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

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

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

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

On-time by weekday

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

Stops and timetable

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

Not enough runs yet to work out the usual delay by stop.

StopSched.
Sneek
17:18
Sneek Noord
17:21
Mantgum
17:29 / 17:30
Leeuwarden
17: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.

Recent runs

DateLast stopFinalMax
Sat 7 NovMantgum 17:44Partial coverage0 min—
Sat 31 OctMantgum 17:44No data—
Sat 24 OctMantgum 17:44No data—
Sat 3 OctMantgum 17:44No data—
Sat 26 SeptMantgum 17:44No data—
Sat 19 SeptMantgum 17:44No data—
Sat 12 SeptMantgum 17:44No data—
Sat 5 SeptMantgum 17:44No data—
Sat 29 AugMantgum 17:45No data—
Sat 22 AugMantgum 17:44No data—
Sat 15 AugMantgum 17:44No data—