RE3 3074 Singen (Hohentwiel) – Erzingen (Baden)

View line RE3

Singen (Hohentwiel) 21:45 → Erzingen (Baden) 22:13 Daily 0 h 28 min · 3 stops DB Regio Baden-Württemberg

✓ Today’s run finished

Today it reached Erzingen (Baden) at 22:18 +5 min

  1. Singen (Hohentwiel)21:45
  2. Schaffhausen21:58
  3. Erzingen (Baden)22:13

Next service: tomorrow 21:45 from Singen (Hohentwiel) · Sat 21 Nov

Next departure 21:45 tomorrow · Singen (Hohentwiel)
On-time · 30 days
67%
18/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
66%
33/50 runs under 3 min
RT coverage: 50 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +12 min

Last 30 days

Arrival delay at Erzingen (Baden), in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 20 Oct Max en route +117 min · last fix heading to Erzingen (Baden) +117 min
  • Thu 22 Oct Max en route +34 min · last fix heading to Erzingen (Baden) +34 min
  • Fri 23 Oct Max en route +31 min · last fix heading to Erzingen (Baden) +31 min
  • Tue 8 Sept Max en route +19 min · last fix heading to Singen (Hohentwiel) +19 min
  • Sun 1 Nov Max en route +14 min · last fix heading to Erzingen (Baden) +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 66% · 33
  • 3–10 min 22% · 11
  • 10–30 min 6% · 3
  • 30+ min 6% · 3

On-time by weekday

  • 100% M n=7
  • 75% T n=8
  • 75% W n=8
  • 75% T n=8
  • 57% F n=7
  • 33% S n=6
  • 33% S n=6

Stops and timetable

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

Last 90 days, 50 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
21:45on time +4 min
21:58 / 22:00≈ on time ≈ +8 min
22:13on time +10 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
Fri 20 NovErzingen (Baden) 22:19+5 min+5 min
Thu 19 NovErzingen (Baden) 22:140 min+3 min
Wed 18 NovErzingen (Baden) 22:140 min—
Tue 17 NovErzingen (Baden) 22:140 min+2 min
Mon 16 NovErzingen (Baden) 22:13−1 min—
Sun 15 NovErzingen (Baden) 22:140 min—
Sat 14 NovErzingen (Baden) 22:140 min+2 min
Fri 13 NovErzingen (Baden) 22:140 min—
Thu 12 NovErzingen (Baden) 22:14−1 min—
Wed 11 NovErzingen (Baden) 22:17+3 min+4 min
Tue 10 NovErzingen (Baden) 22:130 min—
Mon 9 NovErzingen (Baden) 22:15+1 min+1 min
Sun 8 NovErzingen (Baden) 22:14No data—
Sat 7 NovErzingen (Baden) 22:14No data—
Fri 6 NovErzingen (Baden) 22:14No data—
Thu 5 NovErzingen (Baden) 22:14+1 min—
Wed 4 NovSchaffhausen 21:59+1 min+1 min
Tue 3 NovSchaffhausen 21:590 min—
Mon 2 NovSchaffhausen 21:59+1 min+1 min
Sun 1 NovErzingen (Baden) 22:14+14 min+14 min
Sat 31 OctErzingen (Baden) 22:140 min—
Fri 30 OctErzingen (Baden) 22:23+9 min+10 min
Thu 29 OctErzingen (Baden) 22:17+3 min+3 min
Wed 28 OctErzingen (Baden) 22:13−1 min—
Tue 27 OctErzingen (Baden) 22:13−1 min—
Mon 26 OctErzingen (Baden) 22:13−1 min—
Sun 25 OctErzingen (Baden) 22:14+6 min+6 min
Sat 24 OctErzingen (Baden) 22:24+10 min+10 min
Fri 23 OctErzingen (Baden) 22:45+31 min+31 min
Thu 22 OctErzingen (Baden) 22:48+34 min+34 min