RE3 4245 Ulm Hbf – Lindau-Reutin

View line RE3

Ulm Hbf 10:19 → Lindau-Reutin 11:55 Daily 1 h 36 min · 8 stops DB Regio Baden-Württemberg

Running now · updated 11:41

Between Langenargen and Nonnenhorn No data

Estimated arrival at Lindau-Reutin 11:55 · 66 km/h

  1. Ulm Hbf10:19
  2. Biberach (Riss)10:40
  3. Aulendorf10:57
  4. Friedrichshafen Stadt11:24
  5. Langenargen11:38
  6. Nonnenhorn11:45
  7. Lindau-Reutin11:55
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 25 full · 0 partial · 5 no data
On-time · 90 days
98%
46/47 runs under 3 min
RT coverage: 47 full · 0 partial · 7 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Wed 14 Oct Max en route +4 min · last fix heading to Menziken +4 min

Distribution · 90 days

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

  • Early 60% · 28
  • On time 38% · 18
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=6
  • 88% W n=8
  • 100% T n=7
  • 100% F n=8
  • 100% S n=8
  • 100% S n=2

Stops and timetable

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

Last 90 days, 47 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
10:192 min early 2 min earlyPassed
10:40 / 10:41≈ 2 min early ≈ 1 min earlyPassed
10:57 / 10:59≈ 2 min early ≈ on timePassed
11:11 / 11:12≈ 2 min early ≈ on timePassed
11:24 / 11:31≈ 2 min early ≈ on timePassed
11:38 / 11:39≈ 2 min early ≈ +1 minPassed
11:45 / 11:46≈ 1 min early ≈ +1 minNext
11:551 min early +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 5 NovNonnenhorn 11:39Partial coverageNo data—
Wed 4 NovMenziken 17:04+1 min+1 min
Tue 3 NovMenziken 17:03−1 min—
Mon 2 NovMenziken 17:02−2 min—
Sun 1 NovEnzisweiler 11:54No data—
Sat 31 OctMenziken 17:02−2 min—
Fri 30 OctMenziken 17:02−2 min—
Thu 29 OctMenziken 17:040 min—
Wed 28 OctMenziken 17:03−1 min—
Tue 27 OctMenziken 17:03−1 min—
Mon 26 OctMenziken 17:06+2 min+2 min
Sun 25 OctEnzisweiler 11:54No data—
Sat 24 OctMenziken 17:02−1 min—
Fri 23 OctMenziken 17:05+1 min+1 min
Thu 22 OctMenziken 17:02−2 min—
Wed 21 OctMenziken 17:03−1 min—
Tue 20 OctMenziken 17:06+1 min+1 min
Mon 19 OctMenziken 17:02−2 min—
Sun 18 OctEnzisweiler 11:53No data—
Sat 17 OctMenziken 17:05+1 min+1 min
Fri 16 OctMenziken 17:050 min—
Thu 15 OctMenziken 17:07+3 min+3 min
Wed 14 OctMenziken 17:08+4 min+4 min
Tue 13 OctMenziken 17:03−2 min—
Mon 12 OctMenziken 17:02−2 min—
Sun 11 OctEnzisweiler 11:52No data—
Sat 10 OctMenziken 17:03−1 min—
Fri 9 OctMenziken 17:03−2 min—
Thu 8 OctMenziken 17:02−2 min—
Wed 7 OctMenziken 17:03−2 min—