S62 19774 Herblingen – Schaffhausen

View line S62

Herblingen 00:21 → Schaffhausen 00:24 Daily 0 h 03 min · 2 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Schaffhausen at 00:24 −1 min

  1. Herblingen00:21
  2. Schaffhausen00:24

Next service: tomorrow 00:21 from Herblingen · Tue 17 Nov

Next departure 00:21 tomorrow · Herblingen
On-time · 30 days
92%
24/26 runs under 3 min
RT coverage: 26 full · 0 partial · 4 no data
On-time · 90 days
97%
59/61 runs under 3 min
RT coverage: 61 full · 0 partial · 10 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: +1 min

Last 30 days

Arrival delay at Schaffhausen, in minutes. One bar per run.

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

Worst days

  • Thu 5 Nov Max en route +4 min · last fix heading to Schaffhausen +4 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Schaffhausen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 59
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=9
  • 100% W n=12
  • 88% T n=8
  • 100% F n=10
  • 75% S n=4
  • 100% S n=9

Stops and timetable

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

Last 90 days, 62 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
00:21on time on time
00:24on 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
Mon 16 NovSchaffhausen 00:24−1 min—
Sun 15 NovSchaffhausen 00:240 min—
Sat 14 NovSchaffhausen 00:24No data—
Fri 13 NovSchaffhausen 00:24−1 min—
Thu 12 NovSchaffhausen 00:24−1 min—
Wed 11 NovSchaffhausen 00:240 min—
Tue 10 NovSchaffhausen 00:25+1 min+1 min
Mon 9 NovSchaffhausen 00:24−1 min—
Sun 8 NovSchaffhausen 00:24−1 min—
Sat 7 NovSchaffhausen 00:24No data—
Fri 6 NovSchaffhausen 00:24−1 min—
Thu 5 NovSchaffhausen 00:24+4 min+4 min
Wed 4 NovSchaffhausen 00:24−1 min+1 min
Tue 3 NovSchaffhausen 00:24No data—
Mon 2 NovSchaffhausen 00:240 min—
Sun 1 NovSchaffhausen 00:250 min—
Sat 31 OctSchaffhausen 00:25−1 min—
Fri 30 OctSchaffhausen 00:250 min—
Thu 29 OctSchaffhausen 00:25−1 min—
Wed 28 OctSchaffhausen 00:250 min—
Tue 27 OctSchaffhausen 00:25+1 min+1 min
Mon 26 OctSchaffhausen 00:25+1 min+1 min
Sun 25 OctSchaffhausen 01:25No data—
Sat 24 OctSchaffhausen 00:25+4 min+4 min
Fri 23 OctSchaffhausen 00:250 min—
Thu 22 OctSchaffhausen 00:26−1 min—
Wed 21 OctSchaffhausen 00:25+1 min+1 min
Tue 20 OctSchaffhausen 00:25+1 min+1 min
Mon 19 OctSchaffhausen 00:250 min—
Sun 18 OctSchaffhausen 00:25+1 min+1 min