RE3 4805 Ulm Hbf – Lindau-Reutin
Alerts for train 4805
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line RE3.
✓ Today’s run finished
Today, last fix heading to Lindau-Reutin at 12:54 No data
- Ulm Hbf11:19
- Biberach (Riss)11:40
- Aulendorf11:57
- Friedrichshafen Stadt12:25
- Kressbronn12:42
- Wasserburg (Bodensee)12:47
- Lindau-Reutin12:55
Next service: tomorrow 11:19 from Ulm Hbf · Fri 6 Nov
Last 30 days
Arrival delay at Lindau-Reutin, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 6 Sept Max en route +5 min · last fix heading to Singen (Hohentwiel) +5 min
- Fri 4 Sept Max en route +5 min · last fix heading to Aulendorf +5 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 8
- 3–10 min 20% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=2
- 100% W n=1
- 100% T n=3
- 50% F n=2
- — S n=0
- 0% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 10 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 |
|---|---|---|---|
| 11:19 | on time | on time | |
| 11:40 / 11:41 | ≈ on time | ≈ +1 min | |
| 11:57 / 11:59 | ≈ on time | ≈ +2 min | |
| 12:11 / 12:12 | ≈ on time | ≈ +3 min | |
| 12:25 / 12:31 | ≈ on time | ≈ +3 min | |
| 12:42 / 12:43 | ≈ on time | ≈ +4 min | |
| 12:47 / 12:48 | ≈ on time | ≈ +4 min | |
| 12:55 | on time | +5 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 | Lindau-Reutin 12:54 | No data | — |
| Wed 4 Nov | Lindau-Reutin 12:54 | No data | — |
| Tue 3 Nov | Lindau-Reutin 12:54 | No data | — |
| Mon 2 Nov | Enzisweiler 12:53 | No data | — |
| Sun 1 Nov | Enzisweiler 12:53 | No data | — |
| Sat 31 Oct | Enzisweiler 12:53 | No data | — |
| Fri 30 Oct | Enzisweiler 12:53 | No data | — |
| Thu 29 Oct | Enzisweiler 12:53 | No data | — |
| Wed 28 Oct | Enzisweiler 12:53 | No data | — |
| Tue 27 Oct | Enzisweiler 12:53 | No data | — |
| Mon 26 Oct | Enzisweiler 12:53 | No data | — |
| Sun 25 Oct | Enzisweiler 12:53 | No data | — |
| Sat 24 Oct | Enzisweiler 12:53 | No data | — |
| Fri 23 Oct | Enzisweiler 12:53 | No data | — |
| Thu 22 Oct | Enzisweiler 12:53 | No data | — |
| Wed 21 Oct | Enzisweiler 12:53 | No data | — |
| Tue 20 Oct | Enzisweiler 12:53 | No data | — |
| Mon 19 Oct | Enzisweiler 12:53 | No data | — |
| Sun 18 Oct | Enzisweiler 12:54 | No data | — |
| Sat 17 Oct | Enzisweiler 12:53 | No data | — |
| Fri 16 Oct | Enzisweiler 12:54 | No data | — |
| Thu 15 Oct | Enzisweiler 12:53 | No data | — |
| Wed 14 Oct | Enzisweiler 12:53 | No data | — |
| Tue 13 Oct | Enzisweiler 12:54 | No data | — |
| Mon 12 Oct | Enzisweiler 12:53 | No data | — |
| Sun 11 Oct | Enzisweiler 12:53 | No data | — |
| Sat 10 Oct | Enzisweiler 12:53 | No data | — |
| Fri 9 Oct | Enzisweiler 12:53 | No data | — |
| Thu 8 Oct | Enzisweiler 12:53 | No data | — |
| Wed 7 Oct | Enzisweiler 12:53 | No data | — |