S62 19753 Herblingen – Singen (Hohentwiel)

View line S62

Herblingen 18:40 → Singen (Hohentwiel) 18:55 Daily 0 h 15 min · 5 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Singen (Hohentwiel) at 18:54 No data

  1. Herblingen18:40
  2. Thayngen18:44
  3. Bietingen18:47
  4. Gottmadingen18:50
  5. Singen (Hohentwiel)18:55

Next service: tomorrow 18:40 from Herblingen · Sat 21 Nov

Next departure 18:40 tomorrow · Herblingen
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 11 full · 0 partial · 19 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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
18:40on time +1 min
18:44 / 18:45≈ on time ≈ +1 min
18:47≈ on time ≈ +1 min
18:50≈ on time ≈ on time
18:55on time on time

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:54No data—
Thu 19 NovSingen (Hohentwiel) 18:54No data—
Wed 18 NovSingen (Hohentwiel) 18:54No data—
Tue 17 NovSingen (Hohentwiel) 18:54No data—
Mon 16 NovSingen (Hohentwiel) 18:54No data—
Sun 15 NovSingen (Hohentwiel) 18:54No data—
Sat 14 NovSingen (Hohentwiel) 18:54No data—
Fri 13 NovSingen (Hohentwiel) 18:54No data—
Thu 12 NovSingen (Hohentwiel) 18:54No data—
Wed 11 NovSingen (Hohentwiel) 18:54No data—
Tue 10 NovSingen (Hohentwiel) 18:54No data—
Mon 9 NovSingen (Hohentwiel) 18:54No data—
Sun 8 NovSingen (Hohentwiel) 18:54No data—
Sat 7 NovSingen (Hohentwiel) 18:54No data—
Fri 6 NovSingen (Hohentwiel) 18:54No data—
Thu 5 NovSingen (Hohentwiel) 18:54No data—
Wed 4 NovSingen (Hohentwiel) 18:54No data—
Tue 3 NovSingen (Hohentwiel) 18:54No data—
Mon 2 NovSingen (Hohentwiel) 18:54No data—
Sun 1 NovSingen (Hohentwiel) 18:540 min+1 min
Sat 31 OctSingen (Hohentwiel) 18:55−1 min+1 min
Fri 30 OctSingen (Hohentwiel) 18:55−1 min+1 min
Thu 29 OctSingen (Hohentwiel) 18:57+1 min+1 min
Wed 28 OctSingen (Hohentwiel) 18:560 min—
Tue 27 OctSingen (Hohentwiel) 18:560 min—
Mon 26 OctSingen (Hohentwiel) 18:560 min—
Sun 25 OctSingen (Hohentwiel) 18:55−1 min+1 min
Sat 24 OctSingen (Hohentwiel) 18:560 min—
Fri 23 OctSingen (Hohentwiel) 18:560 min+1 min
Thu 22 OctSingen (Hohentwiel) 18:57+1 min+1 min