RE3 32684 Lindau-Reutin – Ulm Hbf

View line RE3

Lindau-Reutin 15:05 → Ulm Hbf 16:40 Mon, Tue, Wed, Thu, Fri 1 h 35 min · 9 stops DB Regio Baden-Württemberg

It does not run today

Last recorded run: Friday 13 November No data

Next service: Monday 15:05 from Lindau-Reutin · Mon 16 Nov

Next departure 15:05 Monday · Lindau-Reutin
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Ulm Hbf, 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

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

  • Early 0% · 0
  • On time 100% · 6
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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
15:05on time +1 min
15:11 / 15:12≈ on time ≈ +1 min
15:16 / 15:17≈ on time ≈ +1 min
15:27 / 15:34≈ on time ≈ +1 min
15:45 / 15:46≈ on time ≈ +1 min
16:00 / 16:01≈ on time ≈ +1 min
16:04 / 16:05≈ on time ≈ +1 min
16:17 / 16:18≈ on time ≈ +1 min
16:40on time +1 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 NovUlm Hbf 16:39No data—
Thu 12 NovUlm Hbf 16:39No data—
Wed 11 NovUlm Hbf 16:39No data—
Tue 10 NovUlm Hbf 16:39No data—
Mon 9 NovUlm Hbf 16:39No data—
Fri 6 NovUlm Hbf 16:39No data—
Thu 5 NovUlm Hbf 16:39No data—
Wed 4 NovUlm Hbf 16:39No data—
Tue 3 NovUlm Hbf 16:39No data—
Mon 2 NovUlm Hbf 16:39No data—
Fri 30 OctBiberach (Riss) 16:07No data—
Thu 29 OctBiberach (Riss) 16:07No data—
Wed 28 OctBiberach (Riss) 16:07No data—
Tue 27 OctBiberach (Riss) 16:07No data—
Mon 26 OctBiberach (Riss) 16:07No data—
Fri 23 OctBiberach (Riss) 16:06No data—
Thu 22 OctBiberach (Riss) 16:07No data—
Wed 21 OctBiberach (Riss) 16:07No data—
Tue 20 OctBiberach (Riss) 16:07No data—
Mon 19 OctBiberach (Riss) 16:07No data—
Fri 16 OctBiberach (Riss) 16:07No data—
Thu 15 OctBiberach (Riss) 16:07No data—
Wed 14 OctBiberach (Riss) 16:06No data—
Tue 13 OctBiberach (Riss) 16:07No data—
Mon 12 OctBiberach (Riss) 16:06No data—
Fri 9 OctBiberach (Riss) 16:06No data—
Thu 8 OctBiberach (Riss) 16:07No data—
Wed 7 OctBiberach (Riss) 16:06No data—
Tue 6 OctBiberach (Riss) 16:07No data—
Mon 5 OctBad Schussenried 16:05No data—