S3 5788 Lustenau → Bregenz

View line S3

Lustenau 19:59 → Bregenz 20:10 Daily 0 h 11 min · 5 stops ÖBB

S3 5788 Lustenau–Bregenz: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 21:10 (GMT+1).

✓ Today’s run finished

Today it reached Bregenz at 20:10 0 min

  1. Lustenau19:59
  2. Hard-Fussach20:01
  3. Lauterach Unterfeld20:04
  4. Bregenz Riedenburg20:07
  5. Bregenz20:10

Next service: tomorrow 19:59 from Lustenau · Sun 22 Nov

Next departure 19:59 tomorrow · Lustenau
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
41/42 runs under 3 min
RT coverage: 42 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Bregenz, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 29 Oct Max en route +12 min · last fix heading to Boudry Littorail +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 41
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 83% T n=6
  • 100% F n=7
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 42 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
19:59on time on time
20:01 / 20:02≈ on time ≈ +1 min
20:04≈ on time ≈ +1 min
20:07≈ on time ≈ +1 min
20:10on time +1 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
Sat 21 NovBregenz 20:090 min—
Fri 20 NovBoudry Littorail 20:47+1 min+2 min
Thu 19 NovBoudry Littorail 20:48+1 min+2 min
Wed 18 NovBoudry Littorail 20:47+1 min—
Tue 17 NovBoudry Littorail 20:49+2 min+2 min
Mon 16 NovBoudry Littorail 20:470 min—
Sun 15 NovBregenz 20:090 min—
Sat 14 NovBregenz 20:090 min—
Fri 13 NovBoudry Littorail 20:48+1 min+2 min
Thu 12 NovBoudry Littorail 20:480 min+2 min
Wed 11 NovBoudry Littorail 20:48+2 min+2 min
Tue 10 NovBoudry Littorail 20:48+1 min+2 min
Mon 9 NovBoudry Littorail 20:47+1 min+2 min
Sun 8 NovBregenz 20:090 min—
Sat 7 NovBregenz 20:090 min—
Fri 6 NovBoudry Littorail 20:470 min—
Thu 5 NovBoudry Littorail 20:470 min—
Wed 4 NovBoudry Littorail 20:49+2 min+2 min
Tue 3 NovBoudry Littorail 20:48+1 min+2 min
Mon 2 NovBoudry Littorail 20:470 min—
Sun 1 NovBregenz 20:090 min—
Sat 31 OctBregenz 20:110 min—
Fri 30 OctBoudry Littorail 20:470 min—
Thu 29 OctBoudry Littorail 20:59+12 min+12 min
Wed 28 OctBoudry Littorail 20:470 min—
Tue 27 OctBoudry Littorail 20:48+1 min+2 min
Mon 26 OctBoudry Littorail 20:49+1 min+2 min
Sun 25 OctBregenz 20:110 min—
Sat 24 OctBregenz 20:110 min—
Fri 23 OctBoudry Littorail 20:46−1 min—