RE3 4801 Enzisweiler – Ulm Hbf

View line RE3

Enzisweiler 14:07 → Ulm Hbf 15:41 Mon, Sat, Sun 1 h 34 min · 9 stops DB Regio Baden-Württemberg

It does not run today

Last recorded run: Sunday 8 November No data

Next service: tomorrow 14:07 from Enzisweiler · Sat 14 Nov

Next departure 14:07 tomorrow · Enzisweiler
On-time · 30 days
—
Too little data (0/8 runs with data)
RT coverage: 0 full · 0 partial · 8 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

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

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

  • Early 30% · 3
  • On time 70% · 7
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

Last 90 days, 10 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
14:07on time on time
14:10≈ on time ≈ on time
14:12≈ on time ≈ on time
14:19 / 14:20≈ on time ≈ +1 min
14:27 / 14:34≈ on time ≈ +1 min
14:45 / 14:46≈ on time ≈ +1 min
15:00 / 15:01≈ on time ≈ +1 min
15:17 / 15:18≈ on time ≈ +1 min
15:41on 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
Sun 8 NovLindau-Reutin 08:57Partial coverageNo data—
Sat 7 NovLindau-Reutin 08:54Partial coverageNo data—
Sun 1 NovEnzisweiler 08:53No data—
Sat 31 OctEnzisweiler 08:53No data—
Sun 25 OctEnzisweiler 08:53No data—
Sat 24 OctEnzisweiler 08:53No data—
Sun 18 OctEnzisweiler 08:52No data—
Sat 17 OctEnzisweiler 08:52No data—
Sun 11 OctEnzisweiler 08:52No data—
Sat 10 OctEnzisweiler 08:53No data—
Sun 4 OctEnzisweiler 08:52No data—
Sun 27 SeptSingen (Hohentwiel) 21:39+1 min+2 min
Sat 26 SeptSingen (Hohentwiel) 21:390 min+2 min
Mon 31 AugAulendorf 23:290 min+11 min
Sun 30 AugAulendorf 21:29−1 min—
Sat 29 AugAulendorf 23:29−1 min+2 min
Fri 28 AugAulendorf 23:290 min+1 min
Thu 27 AugAulendorf 23:29+2 min+2 min
Wed 26 AugAulendorf 23:29−1 min—
Tue 25 AugAulendorf 23:29−1 min+3 min
Tue 18 AugBad Schussenried 23:340 min+4 min