RE3 4827 Ulm Hbf – Lindau-Reutin

View line RE3

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

✓ Today’s run finished

Today it reached Lindau-Reutin at 21:55 0 min

  1. Ulm Hbf20:19
  2. Biberach (Riss)20:40
  3. Aulendorf20:57
  4. Friedrichshafen Stadt21:25
  5. Langenargen21:39
  6. Nonnenhorn21:45
  7. Lindau-Reutin21:55

Next service: tomorrow 20:19 from Ulm Hbf · Sun 15 Nov

Next departure 20:19 tomorrow · Ulm Hbf
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
50/52 runs under 3 min
RT coverage: 52 full · 0 partial · 3 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: +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

  • Fri 30 Oct Max en route +4 min · last fix heading to Enzisweiler +4 min
  • Tue 20 Oct Max en route +3 min · last fix heading to Enzisweiler +3 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 90% · 47
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 52 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
20:19on time on time
20:40 / 20:41≈ on time ≈ +1 min
20:57 / 20:59≈ on time ≈ +1 min
21:11 / 21:12≈ on time ≈ +1 min
21:25 / 21:31≈ on time ≈ +1 min
21:39 / 21:40≈ on time ≈ +2 min
21:45 / 21:46≈ on time ≈ +2 min
21:55on 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 14 NovLindau-Reutin 21:550 min+2 min
Fri 13 NovLindau-Reutin 21:54+1 min—
Thu 12 NovLindau-Reutin 21:57+1 min+4 min
Wed 11 NovLindau-Reutin 21:54−1 min+1 min
Tue 10 NovLindau-Reutin 21:540 min+2 min
Mon 9 NovLindau-Reutin 21:54+1 min+2 min
Sun 8 NovLindau-Reutin 21:54−1 min—
Sat 7 NovLindau-Reutin 21:54+1 min+1 min
Fri 6 NovLindau-Reutin 21:57+1 min+3 min
Thu 5 NovLindau-Reutin 21:540 min—
Wed 4 NovLindau-Reutin 21:540 min+4 min
Tue 3 NovLindau-Reutin 21:540 min—
Mon 2 NovEnzisweiler 21:53+1 min+3 min
Sun 1 NovEnzisweiler 21:530 min+2 min
Sat 31 OctEnzisweiler 21:530 min+3 min
Fri 30 OctEnzisweiler 21:53+4 min+4 min
Thu 29 OctZürich HB 16:25+2 min+2 min
Wed 28 OctEnzisweiler 21:53−1 min—
Tue 27 OctEnzisweiler 21:530 min—
Mon 26 OctEnzisweiler 21:53+2 min+2 min
Sun 25 OctEnzisweiler 21:530 min—
Sat 24 OctEnzisweiler 21:530 min—
Fri 23 OctEnzisweiler 21:53+1 min+1 min
Thu 22 OctEnzisweiler 21:53+2 min+2 min
Wed 21 OctEnzisweiler 21:53+1 min+1 min
Tue 20 OctEnzisweiler 21:53+3 min+3 min
Mon 19 OctEnzisweiler 21:530 min—
Sun 18 OctEnzisweiler 21:53+1 min+2 min
Sat 17 OctEnzisweiler 21:52+3 min+3 min
Fri 16 OctEnzisweiler 21:52+2 min+2 min