S24 20714 Schaffhausen – Thayngen

View line S24

Schaffhausen 05:48 → Thayngen 05:56 Daily 0 h 08 min · 3 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Thayngen at 05:57 No data

  1. Schaffhausen05:48
  2. Herblingen05:52
  3. Thayngen05:56

Next service: tomorrow 05:48 from Schaffhausen · Thu 19 Nov

Next departure 05:48 tomorrow · Schaffhausen
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 46 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

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

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

  • Early 40% · 2
  • On time 60% · 3
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=1
  • 100% W n=2
  • 100% T n=1
  • — F n=0
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Last 90 days, 5 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
05:48on time on time
05:52≈ on time ≈ on time
05:561 min early 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
Wed 18 NovThayngen 05:57No data—
Tue 17 NovThayngen 05:57No data—
Mon 16 NovThayngen 05:57No data—
Sun 15 NovThayngen 05:57No data—
Sat 14 NovThayngen 05:57No data—
Fri 13 NovThayngen 05:58No data—
Thu 12 NovThayngen 05:57No data—
Wed 11 NovThayngen 05:57No data—
Tue 10 NovThayngen 05:57No data—
Mon 9 NovThayngen 05:57No data—
Sun 8 NovThayngen 05:57No data—
Sat 7 NovThayngen 05:57No data—
Fri 6 NovThayngen 05:57No data—
Thu 5 NovThayngen 05:57No data—
Wed 4 NovThayngen 05:57No data—
Tue 3 NovThayngen 05:57No data—
Mon 2 NovThayngen 05:57No data—
Sun 1 NovThayngen 05:57No data—
Sat 31 OctThayngen 05:57No data—
Fri 30 OctThayngen 05:57No data—
Thu 29 OctThayngen 05:57No data—
Wed 28 OctThayngen 05:57No data—
Tue 27 OctThayngen 05:57No data—
Mon 26 OctThayngen 05:57No data—
Sun 25 OctThayngen 05:57No data—
Sat 24 OctThayngen 05:57No data—
Fri 23 OctThayngen 05:57No data—
Thu 22 OctThayngen 05:57No data—
Wed 21 OctThayngen 05:57No data—
Tue 20 OctThayngen 05:57No data—