Train Arriva 37166 Stavoren → Leeuwarden
Arriva 37166 Stavoren–Leeuwarden: final delay under 3 min on 12 of its 13 runs with data in the last 30 days (92%). Median final delay: +2 min. TrainsRadar data as of 22 Nov 2026, 16:35 (GMT+1).
An alert on this phone or computer when the 37166 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Friday 20 November +2 min
Next service: tomorrow 16:48 from Stavoren · Mon 23 Nov
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
- Fri 9 Oct Max en route +5 min · last fix heading to Mantgum +5 min
- Fri 13 Nov Max en route +4 min · last fix heading to Mantgum +4 min
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 90% · 18
- 3–10 min 10% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=4
- 100% W n=5
- 100% T n=3
- 50% 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, 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 16:48 | on time | on time | |
| 16:52 | — | — | |
| 16:56 | — | — | |
| 17:00 | — | — | |
| 17:10 | — | — | |
| 17:14 / 17:18 | — | — | |
| 17:20 / 17:21 | — | — | |
| 17:29 / 17:30 | — | — | |
| 17:37 | — | — |
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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 20 Nov | Mantgum 17:44Partial coverage | +2 min | +2 min |
| Thu 19 Nov | Mantgum 17:44Partial coverage | +2 min | +2 min |
| Wed 18 Nov | Mantgum 17:44Partial coverage | 0 min | — |
| Tue 17 Nov | Mantgum 17:44Partial coverage | +2 min | +2 min |
| Mon 16 Nov | Mantgum 17:45Partial coverage | +2 min | +2 min |
| Fri 13 Nov | Mantgum 17:48Partial coverage | +4 min | +4 min |
| Thu 12 Nov | Mantgum 17:44Partial coverage | +2 min | +2 min |
| Wed 11 Nov | Mantgum 17:44Partial coverage | +1 min | +1 min |
| Tue 10 Nov | Mantgum 17:44Partial coverage | +2 min | +2 min |
| Mon 9 Nov | Mantgum 17:44Partial coverage | 0 min | — |
| Fri 6 Nov | Mantgum 17:44Partial coverage | +1 min | — |
| Thu 5 Nov | Mantgum 17:44 | No data | — |
| Wed 4 Nov | Mantgum 17:44Partial coverage | 0 min | — |
| Tue 3 Nov | Mantgum 17:44 | No data | — |
| Mon 2 Nov | Mantgum 17:39 | No data | — |
| Fri 30 Oct | Mantgum 17:45 | No data | — |
| Thu 29 Oct | Mantgum 17:44 | No data | — |
| Wed 28 Oct | Mantgum 17:44Partial coverage | 0 min | — |
| Tue 27 Oct | Mantgum 17:44 | No data | — |
| Mon 26 Oct | Mantgum 17:44 | No data | — |
| Fri 23 Oct | Mantgum 17:45 | No data | — |
| Thu 22 Oct | Mantgum 17:44 | No data | — |
| Wed 21 Oct | Mantgum 17:44 | No data | — |
| Tue 20 Oct | Mantgum 17:44Partial coverage | 0 min | — |
| Mon 19 Oct | Sneek Noord 17:35Partial coverage | 0 min | — |
| Fri 9 Oct | Mantgum 17:44Partial coverage | +5 min | +5 min |
| Thu 8 Oct | Mantgum 17:45Partial coverage | +1 min | — |
| Wed 7 Oct | Mantgum 17:44Partial coverage | +1 min | — |
| Tue 6 Oct | Mantgum 17:44Partial coverage | +3 min | +4 min |
| Mon 5 Oct | Mantgum 17:44Partial coverage | 0 min | — |