R2 5726 Schaan-Vaduz – Buchs SG

View line R2

Schaan-Vaduz 18:03 → Buchs SG 18:06 Mon, Tue, Wed, Thu, Fri 0 h 03 min · 2 stops ÖBB

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

Next departure 18:03 today · Schaan-Vaduz
On-time · 30 days
67%
14/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
65%
17/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: +10 min

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.

StopSched.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

DateLast stopFinalMax
Mon 16 NovBuchs SG 18:14+7 min+7 min
Fri 13 NovBuchs SG 18:09+2 min+2 min
Thu 12 NovBuchs SG 18:08+1 min+3 min
Wed 11 NovBuchs SG 18:09+3 min+3 min
Tue 10 NovBuchs SG 18:09+3 min+3 min
Mon 9 NovBuchs SG 18:09+2 min+6 min
Fri 6 NovBuchs SG 18:14+9 min+9 min
Thu 5 NovBuchs SG 18:070 min—
Wed 4 NovBuchs SG 18:09+2 min+2 min
Tue 3 NovBuchs SG 18:09+2 min+2 min
Mon 2 NovBuchs SG 18:08+1 min+2 min
Fri 30 OctBuchs SG 18:10+3 min+3 min
Thu 29 OctBuchs SG 18:09+2 min+4 min
Wed 28 OctBuchs SG 18:17+9 min+9 min
Tue 27 OctBuchs SG 18:19+12 min+12 min
Mon 26 OctBuchs SG 18:17+10 min+10 min
Fri 23 OctBuchs SG 18:10+3 min+11 min
Thu 22 OctBuchs SG 18:15+8 min+8 min
Wed 21 OctBuchs SG 18:20+13 min+13 min
Tue 20 OctBuchs SG 18:09+2 min+2 min
Mon 19 OctBuchs SG 18:07+1 min+2 min
Fri 16 OctBuchs SG 18:20+13 min+13 min
Thu 15 OctBuchs SG 18:10+3 min+3 min
Sun 27 SeptBoudry Tuilière 16:43+1 min+3 min
Wed 23 SeptAreuse Littorail 15:52+3 min+3 min
Tue 22 SeptBoudry Littorail 15:52−8 min+2 min