R2 5726 Schaan-Vaduz – Buchs SG
Alerts for train 5726
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R2.
It has not run yet today
Last recorded run: Monday 16 November +7 min
Next service: today 18:03 from Schaan-Vaduz · Tue 17 Nov
Last 30 days
Arrival delay at Buchs SG, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 21 Oct Max en route +13 min · last fix heading to Buchs SG +13 min
- Fri 16 Oct Max en route +13 min · last fix heading to Buchs SG +13 min
- Tue 27 Oct Max en route +12 min · last fix heading to Buchs SG +12 min
- Mon 26 Oct Max en route +10 min · last fix heading to Buchs SG +10 min
- Wed 28 Oct Max en route +9 min · last fix heading to Buchs SG +9 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 4% · 1
- On time 62% · 16
- 3–10 min 19% · 5
- 10–30 min 15% · 4
- 30+ min 0% · 0
On-time by weekday
- 60% M n=5
- 80% T n=5
- 40% W n=5
- 80% T n=5
- 60% F n=5
- — S n=0
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 26 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 |
|---|---|---|---|
| 18:03 | +1 min | +1 min | |
| 18:06 | +3 min | +11 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 16 Nov | Buchs SG 18:14 | +7 min | +7 min |
| Fri 13 Nov | Buchs SG 18:09 | +2 min | +2 min |
| Thu 12 Nov | Buchs SG 18:08 | +1 min | +3 min |
| Wed 11 Nov | Buchs SG 18:09 | +3 min | +3 min |
| Tue 10 Nov | Buchs SG 18:09 | +3 min | +3 min |
| Mon 9 Nov | Buchs SG 18:09 | +2 min | +6 min |
| Fri 6 Nov | Buchs SG 18:14 | +9 min | +9 min |
| Thu 5 Nov | Buchs SG 18:07 | 0 min | — |
| Wed 4 Nov | Buchs SG 18:09 | +2 min | +2 min |
| Tue 3 Nov | Buchs SG 18:09 | +2 min | +2 min |
| Mon 2 Nov | Buchs SG 18:08 | +1 min | +2 min |
| Fri 30 Oct | Buchs SG 18:10 | +3 min | +3 min |
| Thu 29 Oct | Buchs SG 18:09 | +2 min | +4 min |
| Wed 28 Oct | Buchs SG 18:17 | +9 min | +9 min |
| Tue 27 Oct | Buchs SG 18:19 | +12 min | +12 min |
| Mon 26 Oct | Buchs SG 18:17 | +10 min | +10 min |
| Fri 23 Oct | Buchs SG 18:10 | +3 min | +11 min |
| Thu 22 Oct | Buchs SG 18:15 | +8 min | +8 min |
| Wed 21 Oct | Buchs SG 18:20 | +13 min | +13 min |
| Tue 20 Oct | Buchs SG 18:09 | +2 min | +2 min |
| Mon 19 Oct | Buchs SG 18:07 | +1 min | +2 min |
| Fri 16 Oct | Buchs SG 18:20 | +13 min | +13 min |
| Thu 15 Oct | Buchs SG 18:10 | +3 min | +3 min |
| Sun 27 Sept | Boudry Tuilière 16:43 | +1 min | +3 min |
| Wed 23 Sept | Areuse Littorail 15:52 | +3 min | +3 min |
| Tue 22 Sept | Boudry Littorail 15:52 | −8 min | +2 min |