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

✓ Today’s run finished

Today, last fix heading to Lindau-Reutin at 11:54 No data

  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

Next service: tomorrow 10:19 from Ulm Hbf · Mon 16 Nov

Next departure 10:19 tomorrow · Ulm Hbf
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 25 full · 0 partial · 5 no data
On-time · 90 days
96%
53/55 runs under 3 min
RT coverage: 55 full · 0 partial · 8 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

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

Distribution · 90 days

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

  • Early 58% · 32
  • On time 38% · 21
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 100% T n=7
  • 89% W n=9
  • 100% T n=9
  • 100% F n=10
  • 100% S n=9
  • 100% S n=2

Stops and timetable

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

Last 90 days, 55 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
10:192 min early 2 min early
10:40 / 10:41≈ 2 min early ≈ 1 min early
10:57 / 10:59≈ 2 min early ≈ on time
11:11 / 11:12≈ 2 min early ≈ on time
11:24 / 11:31≈ 2 min early ≈ on time
11:38 / 11:39≈ 2 min early ≈ +1 min
11:45 / 11:46≈ 1 min early ≈ +1 min
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
Sun 15 NovLindau-Reutin 11:54No data—
Sat 14 NovMenziken 17:02−2 min—
Fri 13 NovMenziken 17:04+1 min+1 min
Thu 12 NovMenziken 17:04+1 min—
Wed 11 NovMenziken 17:04+2 min+2 min
Tue 10 NovMenziken 17:02−2 min—
Mon 9 NovMenziken 17:09+6 min+6 min
Sun 8 NovLindau-Reutin 11:54No data—
Sat 7 NovMenziken 17:02−2 min—
Fri 6 NovMenziken 17:02−2 min—
Thu 5 NovMenziken 17:03−1 min—
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