S62 19747 Herblingen – Singen (Hohentwiel)

View line S62

Herblingen 17:10 → Singen (Hohentwiel) 17:25 Daily 0 h 15 min · 5 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Singen (Hohentwiel) at 17:24 No data

  1. Herblingen17:10
  2. Thayngen17:14
  3. Bietingen17:17
  4. Gottmadingen17:20
  5. Singen (Hohentwiel)17:25

Next service: tomorrow 17:10 from Herblingen · Fri 20 Nov

Next departure 17:10 tomorrow · Herblingen
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 12 full · 0 partial · 18 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 35 full · 0 partial · 18 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: 0 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 21 Sept Max en route +5 min · last fix heading to Singen (Hohentwiel) +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 34
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

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