S62 19711 Herblingen – Konstanz

View line S62

Herblingen 08:10 → Konstanz 08:52 Daily 0 h 42 min · 8 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Konstanz at 08:53 No data

  1. Herblingen08:10
  2. Thayngen08:14
  3. Bietingen08:17
  4. Singen (Hohentwiel)08:25
  5. Radolfzell08:35
  6. Konstanz-Petershausen08:47
  7. Konstanz08:52

Next service: tomorrow 08:10 from Herblingen · Fri 6 Nov

Next departure 08:10 tomorrow · Herblingen
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 9 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: 0 min

Last 30 days

Arrival delay at Konstanz, 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

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

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

On-time by weekday

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

Stops and timetable

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

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