RE3 4818 Lindau-Reutin – Ulm Hbf

View line RE3

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

It has not run yet today

Last recorded run: Thursday 19 November No data

Next service: today 19:05 from Lindau-Reutin · Fri 20 Nov

Next departure 19:05 today · Lindau-Reutin
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 10 no data
On-time · 90 days
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 17 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

  • Wed 14 Oct Max en route +10 min · last fix heading to Biberach (Riss) +10 min
  • Wed 11 Nov Max en route +7 min · last fix heading to Ulm Hbf +7 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 93% · 37
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=7
  • 67% W n=6
  • 100% T n=1
  • 100% F n=7
  • 100% S n=9
  • 100% S n=8

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
19:05on time on time
19:11 / 19:12≈ on time ≈ on time
19:16 / 19:17≈ on time ≈ on time
19:27 / 19:34≈ on time ≈ on time
19:45 / 19:46≈ on time ≈ +1 min
20:00 / 20:01≈ on time ≈ +1 min
20:17 / 20:18≈ on time ≈ +1 min
20: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
Thu 19 NovUlm Hbf 20:39No data—
Wed 18 NovUlm Hbf 20:39No data—
Tue 17 NovUlm Hbf 20:39+1 min—
Mon 16 NovUlm Hbf 20:39No data—
Sun 15 NovUlm Hbf 20:390 min—
Sat 14 NovUlm Hbf 20:390 min—
Fri 13 NovUlm Hbf 20:390 min—
Thu 12 NovUlm Hbf 20:42No data—
Wed 11 NovUlm Hbf 20:39+7 min+7 min
Tue 10 NovUlm Hbf 20:390 min—
Mon 9 NovUlm Hbf 20:39No data—
Sun 8 NovUlm Hbf 20:390 min—
Sat 7 NovUlm Hbf 20:390 min—
Fri 6 NovUlm Hbf 20:39+1 min—
Thu 5 NovUlm Hbf 20:39No data—
Wed 4 NovUlm Hbf 20:390 min—
Tue 3 NovUlm Hbf 20:390 min—
Mon 2 NovUlm Hbf 20:39No data—
Sun 1 NovUlm Hbf 20:390 min—
Sat 31 OctBiberach (Riss) 20:060 min—
Fri 30 OctBiberach (Riss) 20:06+1 min+1 min
Thu 29 OctBiberach (Riss) 20:06No data—
Wed 28 OctBiberach (Riss) 20:06+1 min+1 min
Tue 27 OctBiberach (Riss) 20:060 min—
Mon 26 OctBiberach (Riss) 20:06No data—
Sun 25 OctBiberach (Riss) 20:06+2 min+2 min
Sat 24 OctBiberach (Riss) 20:060 min—
Fri 23 OctBiberach (Riss) 20:060 min—
Thu 22 OctBiberach (Riss) 20:06No data—
Wed 21 OctBiberach (Riss) 20:060 min—