RE3 3079 Ulm Hbf – Lindau-Reutin

View line RE3

Ulm Hbf 08:19 → Lindau-Reutin 09:55 Mon, Tue, Wed, Thu, Fri 1 h 36 min · 8 stops DB Regio Baden-Württemberg

It does not run today

Last recorded run: Friday 13 November No data

Next service: tomorrow 08:19 from Ulm Hbf · Mon 16 Nov

Next departure 08:19 tomorrow · Ulm Hbf
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
83%
10/12 runs under 3 min
RT coverage: 12 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

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

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

  • Early 17% · 2
  • On time 67% · 8
  • 3–10 min 17% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 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, 12 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
08:19on time on time
08:40 / 08:41≈ on time ≈ +1 min
08:57 / 08:59≈ on time ≈ +1 min
09:11 / 09:12≈ on time ≈ +2 min
09:24 / 09:31≈ on time ≈ +2 min
09:38 / 09:39≈ on time ≈ +2 min
09:45 / 09:46≈ on time ≈ +3 min
09:55on 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

DateLast stopFinalMax
Fri 13 NovLindau-Reutin 09:54No data—
Thu 12 NovLindau-Reutin 09:54No data—
Wed 11 NovLindau-Reutin 09:54No data—
Tue 10 NovLindau-Reutin 09:54No data—
Mon 9 NovLindau-Reutin 09:54No data—
Fri 6 NovLindau-Reutin 09:54No data—
Thu 5 NovLindau-Reutin 09:54No data—
Wed 4 NovLindau-Reutin 09:54No data—
Tue 3 NovLindau-Reutin 09:54No data—
Mon 2 NovEnzisweiler 09:53No data—
Fri 30 OctEnzisweiler 09:53No data—
Thu 29 OctEnzisweiler 09:53No data—
Wed 28 OctEnzisweiler 09:53No data—
Tue 27 OctEnzisweiler 09:53No data—
Mon 26 OctEnzisweiler 09:54No data—
Fri 23 OctEnzisweiler 09:53No data—
Thu 22 OctEnzisweiler 09:53No data—
Wed 21 OctEnzisweiler 09:53No data—
Tue 20 OctEnzisweiler 09:54No data—
Mon 19 OctEnzisweiler 09:53No data—
Fri 16 OctEnzisweiler 09:53No data—
Thu 15 OctEnzisweiler 09:53No data—
Wed 14 OctEnzisweiler 09:53No data—
Tue 13 OctEnzisweiler 09:54No data—
Mon 12 OctEnzisweiler 09:53No data—
Fri 9 OctEnzisweiler 09:53No data—
Thu 8 OctEnzisweiler 09:53No data—
Wed 7 OctEnzisweiler 09:53No data—
Tue 6 OctEnzisweiler 09:53No data—
Mon 5 OctEnzisweiler 09:54No data—