S52 16272 Kerzers – Ins

View line S52

Kerzers 19:01 → Ins 19:09 Mon, Tue, Wed, Thu, Fri 0 h 08 min · 3 stops BLS

It does not run today

Last recorded run: Friday 13 November −1 min

Next service: tomorrow 19:01 from Kerzers · Mon 16 Nov

Next departure 19:01 tomorrow · Kerzers
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 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 Ins, in minutes. One bar per run.

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

Worst days

  • Fri 23 Oct Max en route +11 min · last fix heading to Ins +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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
19:01on time on time
19:04≈ on time ≈ +1 min
19:09on 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
Fri 13 NovIns 19:09−1 min—
Thu 12 NovIns 19:100 min—
Wed 11 NovIns 19:090 min—
Tue 10 NovIns 19:090 min—
Mon 9 NovIns 19:09−1 min—
Fri 6 NovIns 19:09+2 min+2 min
Thu 5 NovIns 19:090 min—
Wed 4 NovIns 19:090 min—
Tue 3 NovIns 19:13+3 min+3 min
Mon 2 NovIns 19:090 min—
Fri 30 OctIns 19:100 min—
Thu 29 OctIns 19:100 min—
Wed 28 OctIns 19:100 min—
Tue 27 OctIns 19:10−1 min—
Mon 26 OctIns 19:11+1 min—
Fri 23 OctIns 19:21+11 min+11 min
Thu 22 OctIns 19:110 min—
Wed 21 OctIns 19:12+2 min+2 min
Tue 20 OctIns 19:100 min—
Mon 19 OctIns 19:100 min—
Fri 16 OctIns 19:10−1 min—
Thu 15 OctIns 19:09−1 min—
Wed 14 OctIns 19:09−1 min—
Tue 13 OctIns 19:100 min—
Mon 12 OctIns 19:09−1 min—
Fri 9 OctIns 19:110 min—
Thu 8 OctIns 19:100 min—
Wed 7 OctIns 19:100 min—
Tue 6 OctIns 19:100 min—
Mon 5 OctIns 19:100 min—