RE3 4248 Lindau-Reutin – Ulm Hbf

View line RE3

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

Running now · updated 20:13

Between Nonnenhorn and Langenargen No data

Estimated arrival at Ulm Hbf 21:40 · 56 km/h

  1. Lindau-Reutin20:05
  2. Nonnenhorn20:12
  3. Langenargen20:19
  4. Ravensburg20:45
  5. Aulendorf21:00
  6. Biberach (Riss)21:17
  7. Ulm Hbf21:40
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 25 full · 1 partial · 4 no data
On-time · 90 days
98%
62/63 runs under 3 min
RT coverage: 62 full · 1 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Tue 15 Sept Max en route +5 min · last fix heading to Aulendorf +5 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 94% · 59
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 90% T n=10
  • 100% W n=9
  • 100% T n=9
  • 100% F n=12
  • 100% S n=11
  • 100% S n=2

Stops and timetable

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

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