RE3 3067 Erzingen (Baden) – Singen (Hohentwiel)

View line RE3

Erzingen (Baden) 17:44 → Singen (Hohentwiel) 18:14 Daily 0 h 30 min · 3 stops DB Regio Baden-Württemberg

✓ Today’s run finished

Today it reached Singen (Hohentwiel) at 18:14 0 min

  1. Erzingen (Baden)17:44
  2. Schaffhausen17:58
  3. Singen (Hohentwiel)18:14

Next service: tomorrow 17:44 from Erzingen (Baden) · Sat 21 Nov

Next departure 17:44 tomorrow · Erzingen (Baden)
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 23 full · 0 partial · 4 no data
On-time · 90 days
95%
39/41 runs under 3 min
RT coverage: 41 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Singen (Hohentwiel), in minutes. One bar per run.

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

Worst days

  • Sun 25 Oct Max en route +7 min · last fix heading to Singen (Hohentwiel) +7 min
  • Sun 1 Nov Max en route +6 min · last fix heading to Singen (Hohentwiel) +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 39
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • 100% S n=5
  • 67% S n=6

Stops and timetable

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

Last 90 days, 41 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
17:44on time on time
17:58 / 18:00≈ on time ≈ +1 min
18:14on 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
Fri 20 NovSingen (Hohentwiel) 18:140 min—
Thu 19 NovSingen (Hohentwiel) 18:140 min—
Wed 18 NovSingen (Hohentwiel) 18:140 min—
Tue 17 NovSingen (Hohentwiel) 18:140 min—
Mon 16 NovSingen (Hohentwiel) 18:140 min—
Sun 15 NovSingen (Hohentwiel) 18:140 min—
Sat 14 NovSingen (Hohentwiel) 18:140 min—
Fri 13 NovSingen (Hohentwiel) 18:140 min—
Thu 12 NovSingen (Hohentwiel) 18:17+2 min+2 min
Wed 11 NovSingen (Hohentwiel) 18:140 min—
Tue 10 NovSingen (Hohentwiel) 18:140 min—
Mon 9 NovSingen (Hohentwiel) 18:140 min—
Sun 8 NovSingen (Hohentwiel) 18:14No data—
Sat 7 NovSingen (Hohentwiel) 18:14No data—
Fri 6 NovSingen (Hohentwiel) 18:14No data—
Thu 5 NovSingen (Hohentwiel) 18:14No data—
Sun 1 NovSingen (Hohentwiel) 18:21+6 min+6 min
Sat 31 OctSingen (Hohentwiel) 18:150 min—
Fri 30 OctSingen (Hohentwiel) 18:150 min—
Thu 29 OctSingen (Hohentwiel) 18:150 min—
Wed 28 OctSingen (Hohentwiel) 18:130 min—
Tue 27 OctSingen (Hohentwiel) 18:150 min—
Mon 26 OctSingen (Hohentwiel) 18:150 min—
Sun 25 OctSingen (Hohentwiel) 18:22+7 min+7 min
Sat 24 OctSingen (Hohentwiel) 18:150 min—
Fri 23 OctSingen (Hohentwiel) 18:150 min—
Thu 22 OctSingen (Hohentwiel) 18:150 min—
Wed 21 OctSingen (Hohentwiel) 18:150 min—
Tue 20 OctSingen (Hohentwiel) 18:130 min—
Mon 19 OctSingen (Hohentwiel) 18:150 min—