S3 5748 Lustenau → Bregenz
Alerts for train 5748
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S3.
S3 5748 Lustenau–Bregenz: final delay under 3 min on 28 of its 28 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 16:41 (GMT+1).
An alert on this phone or computer when the 5748 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today it reached Bregenz at 10:10 0 min
- Lustenau09:59
- Hard-Fussach10:01
- Lauterach Unterfeld10:04
- Bregenz Riedenburg10:07
- Bregenz10:10
Next service: tomorrow 09:59 from Lustenau · Sun 22 Nov
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
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 38
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=6
- 100% W n=6
- 100% T n=4
- 100% F n=6
- 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, 38 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 |
|---|---|---|---|
| 09:59 | on time | on time | |
| 10:01 / 10:02 | ≈ on time | ≈ on time | |
| 10:04 | ≈ on time | ≈ on time | |
| 10:07 | ≈ on time | ≈ on time | |
| 10:10 | on time | on time |
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 |
|---|---|---|---|
| Sat 21 Nov | Bregenz 10:09 | 0 min | — |
| Fri 20 Nov | Bregenz 10:09 | 0 min | — |
| Thu 19 Nov | Bregenz 10:09 | No data | — |
| Wed 18 Nov | Bregenz 10:09 | 0 min | — |
| Tue 17 Nov | Bregenz 10:09 | 0 min | — |
| Mon 16 Nov | Bregenz 10:09 | 0 min | — |
| Sun 15 Nov | Bregenz 10:09 | 0 min | — |
| Sat 14 Nov | Bregenz 10:09 | 0 min | — |
| Fri 13 Nov | Bregenz 10:09 | 0 min | — |
| Thu 12 Nov | Bregenz 10:09 | 0 min | — |
| Wed 11 Nov | Bregenz 10:09 | 0 min | — |
| Tue 10 Nov | Bregenz 10:09 | 0 min | — |
| Mon 9 Nov | Bregenz 10:09 | 0 min | — |
| Sun 8 Nov | Bregenz 10:09 | 0 min | — |
| Sat 7 Nov | Bregenz 10:09 | 0 min | — |
| Fri 6 Nov | Bregenz 10:09 | 0 min | — |
| Thu 5 Nov | Bregenz 10:09 | 0 min | — |
| Wed 4 Nov | Bregenz 10:09 | 0 min | — |
| Tue 3 Nov | Bregenz 10:09 | 0 min | — |
| Mon 2 Nov | Bregenz 10:09 | 0 min | — |
| Sun 1 Nov | Bregenz 10:11 | 0 min | — |
| Sat 31 Oct | Bregenz 10:11 | 0 min | — |
| Fri 30 Oct | Bregenz 10:11 | 0 min | — |
| Thu 29 Oct | Bregenz 10:11 | No data | — |
| Wed 28 Oct | Bregenz 10:11 | 0 min | — |
| Tue 27 Oct | Bregenz 10:11 | 0 min | — |
| Mon 26 Oct | Bregenz 10:12 | 0 min | — |
| Sun 25 Oct | Bregenz 10:11 | 0 min | — |
| Sat 24 Oct | Bregenz 10:11 | 0 min | — |
| Fri 23 Oct | Bregenz 10:11 | 0 min | — |