RE3 4244 Lindau-Reutin – Ulm Hbf

View line RE3

Lindau-Reutin 16:05 → Ulm Hbf 17:40 Sat, Sun 1 h 35 min · 8 stops DB Regio Baden-Württemberg

✓ Today’s run finished

Today it reached Ulm Hbf at 17:40 0 min

  1. Lindau-Reutin16:05
  2. Nonnenhorn16:12
  3. Langenargen16:19
  4. Ravensburg16:46
  5. Aulendorf17:00
  6. Biberach (Riss)17:17
  7. Ulm Hbf17:40

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

Next departure 16:05 tomorrow · Lindau-Reutin
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 4 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 9 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

Worst days

  • Fri 4 Sept Max en route +5 min · last fix heading to Buchs AG +5 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • 100% S n=8
  • — S n=0

Stops and timetable

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

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