RE3 32691 Ulm Hbf – Lindau-Reutin

View line RE3

Ulm Hbf 16:18 → Lindau-Reutin 17:55 Mon, Tue, Wed, Thu, Fri 1 h 37 min · 11 stops DB Regio Baden-Württemberg

It does not run today

Last recorded run: Friday 13 November No data

Next service: tomorrow 16:18 from Ulm Hbf · Mon 16 Nov

Next departure 16:18 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
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 30 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+11min
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 18 Sept Max en route +18 min · last fix heading to Schaffhausen +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 4
  • 3–10 min 0% · 0
  • 10–30 min 20% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • — W n=0
  • — T n=0
  • 50% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 5 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
16:18on time on time
16:39 / 16:40≈ on time ≈ +2 min
16:42≈ on time ≈ +2 min
16:52 / 16:53≈ on time ≈ +3 min
16:58 / 16:59≈ on time ≈ +4 min
17:11 / 17:12≈ +1 min ≈ +6 min
17:25 / 17:31≈ +1 min ≈ +7 min
17:38 / 17:39≈ +1 min ≈ +9 min
17:44≈ +1 min ≈ +10 min
17:47≈ +1 min ≈ +10 min
17:55+1 min +11 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 17:54No data—
Thu 12 NovLindau-Reutin 17:54No data—
Wed 11 NovLindau-Reutin 17:54No data—
Tue 10 NovLindau-Reutin 17:54No data—
Mon 9 NovLindau-Reutin 17:54No data—
Fri 6 NovLindau-Reutin 17:54No data—
Thu 5 NovLindau-Reutin 17:54No data—
Wed 4 NovLindau-Reutin 17:54No data—
Tue 3 NovLindau-Reutin 17:54No data—
Mon 2 NovEnzisweiler 17:54No data—
Fri 30 OctEnzisweiler 17:54No data—
Thu 29 OctEnzisweiler 17:54No data—
Wed 28 OctEnzisweiler 17:54No data—
Tue 27 OctEnzisweiler 17:54No data—
Mon 26 OctEnzisweiler 17:54No data—
Fri 23 OctEnzisweiler 17:54No data—
Thu 22 OctEnzisweiler 17:54No data—
Wed 21 OctEnzisweiler 17:54No data—
Tue 20 OctEnzisweiler 17:54No data—
Mon 19 OctEnzisweiler 17:54No data—
Fri 16 OctEnzisweiler 17:54No data—
Thu 15 OctEnzisweiler 17:53No data—
Wed 14 OctEnzisweiler 17:53No data—
Tue 13 OctEnzisweiler 17:53No data—
Mon 12 OctEnzisweiler 17:53No data—
Fri 9 OctEnzisweiler 17:54No data—
Thu 8 OctEnzisweiler 17:54No data—
Wed 7 OctEnzisweiler 17:54No data—
Tue 6 OctEnzisweiler 17:53No data—
Mon 5 OctEnzisweiler 17:53No data—