RE3 3041 Erzingen (Baden) – Singen (Hohentwiel)

View line RE3

Erzingen (Baden) 06:01 → Singen (Hohentwiel) 06:30 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 3 stops DB Regio Baden-Württemberg

✓ Today’s run finished

Today it reached Singen (Hohentwiel) at 06:33 +3 min

  1. Erzingen (Baden)06:01
  2. Schaffhausen06:14
  3. Singen (Hohentwiel)06:30

Next service: Monday 06:01 from Erzingen (Baden) · Mon 23 Nov

Next departure 06:01 Monday · Erzingen (Baden)
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 3 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 3 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: +3 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

  • Mon 19 Oct Max en route +14 min · last fix heading to Singen (Hohentwiel) +14 min
  • Fri 20 Nov Max en route +3 min · last fix heading to Singen (Hohentwiel) +3 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Singen (Hohentwiel) +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 7% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=6
  • 100% W n=6
  • 83% T n=6
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
06:01on time on time
06:14 / 06:16≈ on time ≈ +1 min
06:30on 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) 06:34+3 min+3 min
Thu 19 NovSingen (Hohentwiel) 06:290 min—
Wed 18 NovSingen (Hohentwiel) 06:290 min—
Tue 17 NovSingen (Hohentwiel) 06:290 min—
Mon 16 NovSingen (Hohentwiel) 06:290 min—
Fri 13 NovSingen (Hohentwiel) 06:34+2 min+2 min
Thu 12 NovSingen (Hohentwiel) 06:290 min+2 min
Wed 11 NovSingen (Hohentwiel) 06:290 min—
Tue 10 NovSingen (Hohentwiel) 06:290 min—
Mon 9 NovSingen (Hohentwiel) 06:29No data—
Fri 6 NovSingen (Hohentwiel) 06:29No data—
Mon 2 NovSingen (Hohentwiel) 06:29No data—
Fri 30 OctSingen (Hohentwiel) 06:310 min—
Thu 29 OctSingen (Hohentwiel) 06:34+3 min+3 min
Wed 28 OctSingen (Hohentwiel) 06:310 min—
Tue 27 OctSingen (Hohentwiel) 06:310 min—
Mon 26 OctSingen (Hohentwiel) 06:310 min—
Fri 23 OctSingen (Hohentwiel) 06:310 min—
Thu 22 OctSingen (Hohentwiel) 06:33+2 min+3 min
Wed 21 OctSingen (Hohentwiel) 06:310 min—
Tue 20 OctSingen (Hohentwiel) 06:33+2 min+2 min
Mon 19 OctSingen (Hohentwiel) 06:45+14 min+14 min
Fri 16 OctSingen (Hohentwiel) 06:33+2 min+2 min
Thu 15 OctSingen (Hohentwiel) 06:33+2 min+2 min
Wed 14 OctSingen (Hohentwiel) 06:310 min—
Tue 13 OctSingen (Hohentwiel) 06:310 min—
Mon 12 OctSingen (Hohentwiel) 06:310 min—
Fri 9 OctSingen (Hohentwiel) 06:310 min—
Thu 8 OctSingen (Hohentwiel) 06:310 min—
Wed 7 OctSingen (Hohentwiel) 06:310 min—