RE3 4240 Lindau-Reutin – Ulm Hbf

View line RE3

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

✓ Today’s run finished

Today, last fix heading to Ulm Hbf at 09:39 No data

  1. Lindau-Reutin08:05
  2. Nonnenhorn08:13
  3. Langenargen08:19
  4. Ravensburg08:45
  5. Aulendorf09:00
  6. Biberach (Riss)09:17
  7. Ulm Hbf09:40

Next service: tomorrow 08:05 from Lindau-Reutin · Sun 8 Nov

Next departure 08:05 tomorrow · Lindau-Reutin
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 13 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 18 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: +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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=8
  • 100% W n=9
  • 100% T n=2
  • 100% F n=11
  • 100% S n=5
  • 100% S n=1

Stops and timetable

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

Last 90 days, 39 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
08:05on time on time
08:13 / 08:14≈ on time ≈ on time
08:19 / 08:21≈ on time ≈ on time
08:28 / 08:35≈ on time ≈ on time
08:45 / 08:46≈ on time ≈ +1 min
09:00 / 09:01≈ on time ≈ +1 min
09:17 / 09:18≈ on time ≈ +1 min
09: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
Sat 7 NovUlm Hbf 09:39No data—
Fri 6 NovAarau 14:320 min—
Thu 5 NovAarau 14:33No data—
Wed 4 NovAarau 14:330 min—
Tue 3 NovAarau 14:34+1 min—
Mon 2 NovAarau 14:33No data—
Sun 1 NovBiberach (Riss) 09:06No data—
Sat 31 OctAarau 14:330 min—
Fri 30 OctAarau 14:330 min—
Thu 29 OctAarau 14:33No data—
Wed 28 OctAarau 14:330 min—
Tue 27 OctAarau 14:33−1 min—
Mon 26 OctAarau 14:33No data—
Sun 25 OctBiberach (Riss) 09:06No data—
Sat 24 OctAarau 14:330 min—
Fri 23 OctAarau 14:330 min—
Thu 22 OctAarau 14:33No data—
Wed 21 OctAarau 14:320 min—
Tue 20 OctAarau 14:340 min—
Mon 19 OctAarau 14:33No data—
Sun 18 OctBiberach (Riss) 09:06No data—
Sat 17 OctAarau 14:330 min—
Fri 16 OctAarau 14:37+3 min+4 min
Thu 15 OctAarau 14:33No data—
Wed 14 OctAarau 14:330 min—
Tue 13 OctAarau 14:34+1 min—
Mon 12 OctAarau 14:33No data—
Sun 11 OctBiberach (Riss) 09:06No data—
Sat 10 OctAarau 14:36+2 min+2 min
Fri 9 OctAarau 14:320 min—