S65 8389 Schaffhausen – Jestetten

View line S65

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

✓ Today’s run finished

Today it reached Jestetten at 22:37 0 min

  1. Schaffhausen22:27
  2. Neuhausen22:30
  3. Neuhausen Rheinfall22:31
  4. Jestetten22:37

Next service: tomorrow 22:27 from Schaffhausen · Sat 21 Nov

Next departure 22:27 tomorrow · Schaffhausen
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 48 full · 0 partial · 1 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: 0 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

Distribution · 90 days

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

  • Early 15% · 7
  • On time 85% · 41
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 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
22:27on time +1 min
22:30≈ on time ≈ +1 min
22:31≈ on time ≈ +1 min
22:37on 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
Fri 20 NovJestetten 22:380 min—
Thu 19 NovJestetten 22:39+1 min—
Wed 18 NovJestetten 22:380 min—
Tue 17 NovJestetten 22:39+1 min—
Mon 16 NovJestetten 22:37−1 min—
Sun 15 NovJestetten 22:37−1 min—
Sat 14 NovJestetten 22:380 min—
Fri 13 NovJestetten 22:380 min—
Thu 12 NovJestetten 22:380 min—
Wed 11 NovJestetten 22:37−1 min—
Tue 10 NovJestetten 22:370 min—
Mon 9 NovJestetten 22:38−1 min—
Sat 7 NovJestetten 22:39+2 min+3 min
Fri 6 NovJestetten 22:39No data—
Thu 5 NovJestetten 22:380 min—
Wed 4 NovJestetten 22:380 min—
Tue 3 NovJestetten 22:380 min—
Mon 2 NovJestetten 22:37−1 min—
Sun 1 NovJestetten 22:38−1 min—
Sat 31 OctJestetten 22:37−1 min—
Fri 30 OctJestetten 22:37−1 min—
Thu 29 OctJestetten 22:37−1 min—
Wed 28 OctJestetten 22:380 min—
Tue 27 OctJestetten 22:380 min—
Mon 26 OctJestetten 22:37−1 min—
Sun 25 OctJestetten 22:37−1 min—
Sat 24 OctJestetten 22:380 min—
Fri 23 OctJestetten 22:37−1 min—
Thu 22 OctJestetten 22:37−1 min—
Wed 21 OctJestetten 22:380 min—