RE3 3079 Ulm Hbf – Lindau-Reutin
Alerts for train 3079
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.
Running now · updated 09:46
Position estimated from the timetable
Between Nonnenhorn and Lindau-Reutin No data
Estimated arrival at Lindau-Reutin 09:55 · 6 km/h
- Ulm Hbf08:19
- Biberach (Riss)08:40
- Aulendorf08:57
- Friedrichshafen Stadt09:24
- Langenargen09:38
- Nonnenhorn09:45
- Lindau-Reutin09:55
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
- Fri 25 Sept Max en route +3 min · last fix heading to Bad Schussenried +3 min
- Wed 30 Sept Max en route +3 min · last fix heading to Erzingen (Baden) +3 min
Distribution · 90 days
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 15% · 2
- On time 69% · 9
- 3–10 min 15% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=1
- 50% W n=2
- 100% T n=1
- 50% F n=2
- 100% S n=3
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 13 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 | Today |
|---|---|---|---|---|
| 08:19 | on time | on time | Passed | |
| 08:40 / 08:41 | ≈ on time | ≈ +1 min | Passed | |
| 08:57 / 08:59 | ≈ on time | ≈ +1 min | Passed | |
| 09:11 / 09:12 | ≈ on time | ≈ +2 min | Passed | |
| 09:24 / 09:31 | ≈ on time | ≈ +2 min | Passed | |
| 09:38 / 09:39 | ≈ on time | ≈ +2 min | Passed | |
| 09:45 / 09:46 | ≈ on time | ≈ +3 min | Passed | |
| 09:55 | on time | +3 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 |
|---|---|---|---|
| Fri 13 Nov | Nonnenhorn 09:44Partial coverage | No data | — |
| Thu 12 Nov | Lindau-Reutin 09:54 | No data | — |
| Wed 11 Nov | Lindau-Reutin 09:54 | No data | — |
| Tue 10 Nov | Lindau-Reutin 09:54 | No data | — |
| Mon 9 Nov | Lindau-Reutin 09:54 | No data | — |
| Fri 6 Nov | Lindau-Reutin 09:54 | No data | — |
| Thu 5 Nov | Lindau-Reutin 09:54 | No data | — |
| Wed 4 Nov | Lindau-Reutin 09:54 | No data | — |
| Tue 3 Nov | Lindau-Reutin 09:54 | No data | — |
| Mon 2 Nov | Enzisweiler 09:53 | No data | — |
| Fri 30 Oct | Enzisweiler 09:53 | No data | — |
| Thu 29 Oct | Enzisweiler 09:53 | No data | — |
| Wed 28 Oct | Enzisweiler 09:53 | No data | — |
| Tue 27 Oct | Enzisweiler 09:53 | No data | — |
| Mon 26 Oct | Enzisweiler 09:54 | No data | — |
| Fri 23 Oct | Enzisweiler 09:53 | No data | — |
| Thu 22 Oct | Enzisweiler 09:53 | No data | — |
| Wed 21 Oct | Enzisweiler 09:53 | No data | — |
| Tue 20 Oct | Enzisweiler 09:54 | No data | — |
| Mon 19 Oct | Enzisweiler 09:53 | No data | — |
| Fri 16 Oct | Enzisweiler 09:53 | No data | — |
| Thu 15 Oct | Enzisweiler 09:53 | No data | — |
| Wed 14 Oct | Enzisweiler 09:53 | No data | — |
| Tue 13 Oct | Enzisweiler 09:54 | No data | — |
| Mon 12 Oct | Enzisweiler 09:53 | No data | — |
| Fri 9 Oct | Enzisweiler 09:53 | No data | — |
| Thu 8 Oct | Enzisweiler 09:53 | No data | — |
| Wed 7 Oct | Enzisweiler 09:53 | No data | — |
| Tue 6 Oct | Enzisweiler 09:53 | No data | — |
| Mon 5 Oct | Enzisweiler 09:54 | No data | — |