S65 8381 Schaffhausen – Jestetten

View line S65

Schaffhausen 20:27 → Jestetten 20:37 Daily 0 h 10 min · 4 stops Thurbo

It has not run yet today

Last recorded run: Thursday 19 November +3 min

Next service: today 20:27 from Schaffhausen · Fri 20 Nov

Next departure 20:27 today · Schaffhausen
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Jestetten, 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 19 Nov Max en route +3 min · last fix heading to Jestetten +3 min

Distribution · 90 days

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

  • Early 8% · 4
  • On time 90% · 43
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=8
  • 88% T n=8
  • 100% F n=5
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 48 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
20:27on time +1 min
20:30≈ on time ≈ +1 min
20:31≈ on time ≈ +1 min
20:37on time +2 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 NovJestetten 20:39+3 min+3 min
Wed 18 NovJestetten 20:37−1 min—
Tue 17 NovJestetten 20:39+1 min+1 min
Mon 16 NovJestetten 20:370 min—
Sun 15 NovJestetten 20:37−1 min—
Sat 14 NovJestetten 20:37−1 min—
Fri 13 NovJestetten 20:37−1 min—
Thu 12 NovJestetten 20:39+1 min—
Wed 11 NovJestetten 20:370 min—
Tue 10 NovJestetten 20:37−1 min—
Mon 9 NovJestetten 20:37−1 min—
Sat 7 NovJestetten 20:39+2 min+3 min
Thu 5 NovJestetten 20:38+1 min+1 min
Wed 4 NovJestetten 20:380 min—
Tue 3 NovJestetten 20:39+1 min+1 min
Mon 2 NovJestetten 20:380 min—
Sun 1 NovJestetten 20:37−1 min—
Sat 31 OctJestetten 20:37−1 min—
Fri 30 OctJestetten 20:37−1 min—
Thu 29 OctJestetten 20:41+3 min+3 min
Wed 28 OctJestetten 20:390 min—
Tue 27 OctJestetten 20:380 min—
Mon 26 OctJestetten 20:38−1 min—
Sun 25 OctJestetten 20:36−2 min—
Sat 24 OctJestetten 20:37−1 min—
Fri 23 OctJestetten 20:41+3 min+3 min
Thu 22 OctJestetten 20:40+1 min+2 min
Wed 21 OctJestetten 20:39+2 min+2 min
Tue 20 OctJestetten 20:380 min—
Mon 19 OctJestetten 20:40+2 min+3 min