RE3 4816 Lindau-Reutin – Ulm Hbf

View line RE3

Lindau-Reutin 17:05 → Ulm Hbf 18:40 Daily 1 h 35 min · 8 stops DB Regio Baden-Württemberg

✓ Today’s run finished

Today it reached Ulm Hbf at 18:40 0 min

  1. Lindau-Reutin17:05
  2. Wasserburg (Bodensee)17:11
  3. Kressbronn17:16
  4. Ravensburg17:45
  5. Aulendorf18:00
  6. Biberach (Riss)18:17
  7. Ulm Hbf18:40

Next service: tomorrow 17:05 from Lindau-Reutin · Fri 13 Nov

Next departure 17:05 tomorrow · Lindau-Reutin
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
96%
46/48 runs under 3 min
RT coverage: 48 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

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

Worst days

  • Sun 25 Oct Max en route +29 min · last fix heading to Biberach (Riss) +24 min
  • Sat 7 Nov Max en route +7 min · last fix heading to Ulm Hbf +6 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 92% · 44
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • 86% S n=7
  • 83% S n=6

Stops and timetable

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

Last 90 days, 48 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
17:05on time on time
17:11 / 17:12≈ on time ≈ on time
17:16 / 17:17≈ on time ≈ on time
17:27 / 17:34≈ on time ≈ on time
17:45 / 17:46≈ on time ≈ +1 min
18:00 / 18:01≈ on time ≈ +1 min
18:17 / 18:18≈ on time ≈ +1 min
18: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
Thu 12 NovUlm Hbf 18:390 min—
Wed 11 NovUlm Hbf 18:390 min—
Tue 10 NovUlm Hbf 18:390 min+2 min
Mon 9 NovUlm Hbf 18:390 min+1 min
Sun 8 NovUlm Hbf 18:390 min—
Sat 7 NovUlm Hbf 18:39+6 min+7 min
Fri 6 NovUlm Hbf 18:390 min+2 min
Thu 5 NovUlm Hbf 18:390 min—
Wed 4 NovUlm Hbf 18:390 min+1 min
Tue 3 NovUlm Hbf 18:390 min+2 min
Mon 2 NovUlm Hbf 18:420 min—
Sun 1 NovUlm Hbf 18:42+1 min+1 min
Sat 31 OctBiberach (Riss) 18:060 min—
Fri 30 OctBiberach (Riss) 18:060 min+1 min
Thu 29 OctBiberach (Riss) 18:06+2 min+2 min
Wed 28 OctBiberach (Riss) 18:06+1 min+1 min
Tue 27 OctBiberach (Riss) 18:060 min—
Mon 26 OctBiberach (Riss) 18:06No data—
Sun 25 OctBiberach (Riss) 18:06+24 min+29 min
Sat 24 OctBiberach (Riss) 18:060 min—
Fri 23 OctBiberach (Riss) 18:06+3 min+3 min
Thu 22 OctBiberach (Riss) 18:060 min—
Wed 21 OctBiberach (Riss) 18:060 min—
Tue 20 OctBiberach (Riss) 18:06+1 min—
Mon 19 OctBiberach (Riss) 18:06+1 min—
Sun 18 OctBiberach (Riss) 18:060 min—
Sat 17 OctBiberach (Riss) 18:060 min—
Fri 16 OctBiberach (Riss) 18:070 min—
Thu 15 OctBiberach (Riss) 18:060 min—
Wed 14 OctBiberach (Riss) 18:06+1 min+2 min