S2 5706 Schaan-Vaduz – Buchs SG
Alerts for train 5706
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S2.
✓ Today’s run finished
Today it reached Buchs SG at 07:44 +3 min
- Schaan-Vaduz07:37
- Buchs SG07:41
Next service: tomorrow 07:37 from Schaan-Vaduz · Fri 6 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
- Tue 3 Nov Max en route +11 min · last fix heading to Buchs SG +11 min
- Wed 4 Nov Max en route +10 min · last fix heading to Buchs SG +10 min
- Thu 22 Oct Max en route +10 min · last fix heading to Buchs SG +10 min
- Tue 20 Oct Max en route +8 min · last fix heading to Buchs SG +8 min
- Tue 27 Oct Max en route +7 min · last fix heading to Buchs SG +7 min
Distribution · 90 days
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 25% · 7
- On time 29% · 8
- 3–10 min 39% · 11
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 50% M n=4
- 57% T n=7
- 60% W n=5
- 40% T n=5
- 57% F n=7
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 28 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 |
|---|---|---|---|
| 07:37 | on time | on time | |
| 07:41 | +2 min | +8 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 |
|---|---|---|---|
| Thu 5 Nov | Buchs SG 07:44 | +3 min | +3 min |
| Wed 4 Nov | Buchs SG 07:52 | +10 min | +10 min |
| Tue 3 Nov | Buchs SG 07:54 | +11 min | +11 min |
| Mon 2 Nov | Buchs SG 07:49 | +7 min | +7 min |
| Fri 30 Oct | Buchs SG 07:47 | +5 min | +5 min |
| Thu 29 Oct | Buchs SG 07:48 | +6 min | +6 min |
| Wed 28 Oct | Buchs SG 07:42 | 0 min | — |
| Tue 27 Oct | Buchs SG 07:49 | +7 min | +7 min |
| Mon 26 Oct | Buchs SG 07:47 | +5 min | +5 min |
| Fri 23 Oct | Buchs SG 07:45 | +3 min | +3 min |
| Thu 22 Oct | Buchs SG 07:52 | +10 min | +10 min |
| Wed 21 Oct | Buchs SG 07:47 | +5 min | +5 min |
| Tue 20 Oct | Buchs SG 07:50 | +8 min | +8 min |
| Mon 19 Oct | Buchs SG 07:43 | +1 min | — |
| Fri 16 Oct | Buchs SG 07:46 | +4 min | +4 min |
| Thu 15 Oct | Buchs SG 07:47 | +5 min | +5 min |
| Wed 14 Oct | Feldkirch 07:07 | No data | — |
| Tue 13 Oct | Feldkirch 07:07 | No data | — |
| Mon 12 Oct | Feldkirch 07:07 | No data | — |
| Fri 9 Oct | Feldkirch 07:07 | No data | — |
| Thu 8 Oct | Feldkirch 07:07 | No data | — |
| Wed 7 Oct | Feldkirch 07:07 | No data | — |
| Tue 6 Oct | Feldkirch 07:07 | No data | — |
| Mon 5 Oct | Feldkirch 07:08 | No data | — |
| Fri 2 Oct | Feldkirch 07:05 | No data | — |
| Thu 1 Oct | Feldkirch 07:06 | No data | — |
| Wed 30 Sept | Feldkirch 07:05 | −2 min | — |
| Tue 29 Sept | Feldkirch 07:06 | No data | — |
| Mon 28 Sept | Feldkirch 07:05 | No data | — |
| Fri 25 Sept | Feldkirch 07:05 | −3 min | — |