S52 16269 Ins – Kerzers

View line S52

Ins 18:50 → Kerzers 18:57 Mon, Tue, Wed, Thu, Fri 0 h 07 min · 3 stops BLS

It does not run today

Last recorded run: Friday 13 November +1 min

Next service: tomorrow 18:50 from Ins · Mon 16 Nov

Next departure 18:50 tomorrow · Ins
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Kerzers, 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 +16 min · last fix heading to Kerzers +16 min
  • Tue 3 Nov Max en route +6 min · last fix heading to Kerzers +6 min
  • Mon 19 Oct Max en route +3 min · last fix heading to Kerzers +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 32
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 88% T n=8
  • 100% W n=6
  • 100% T n=6
  • 86% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 35 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
18:50+1 min +1 min
18:53≈ +1 min ≈ +1 min
18:57+1 min +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 NovKerzers 18:59+1 min+1 min
Thu 12 NovKerzers 18:58+1 min—
Wed 11 NovKerzers 18:580 min—
Tue 10 NovKerzers 18:59+1 min—
Mon 9 NovKerzers 18:580 min—
Fri 6 NovKerzers 18:59+1 min+1 min
Thu 5 NovKerzers 18:580 min—
Wed 4 NovKerzers 18:59+1 min—
Tue 3 NovKerzers 19:04+6 min+6 min
Mon 2 NovKerzers 18:59+2 min+2 min
Fri 30 OctKerzers 18:59+1 min—
Thu 29 OctKerzers 19:00+2 min+2 min
Wed 28 OctKerzers 18:59+1 min—
Tue 27 OctKerzers 18:59+1 min—
Mon 26 OctKerzers 18:59+1 min—
Fri 23 OctKerzers 19:14+16 min+16 min
Thu 22 OctKerzers 18:580 min—
Wed 21 OctKerzers 18:59+1 min+1 min
Tue 20 OctKerzers 18:59+1 min—
Mon 19 OctKerzers 19:01+3 min+3 min
Fri 16 OctKerzers 18:59+1 min—
Thu 15 OctKerzers 19:00+2 min+2 min
Wed 14 OctKerzers 18:59+1 min—
Tue 13 OctKerzers 18:59+1 min—
Mon 12 OctKerzers 18:59+1 min+1 min
Fri 9 OctKerzers 18:59+1 min—
Thu 8 OctKerzers 18:59+1 min+1 min
Wed 7 OctKerzers 18:590 min—
Tue 6 OctKerzers 18:59+1 min—
Mon 5 OctKerzers 18:590 min—