S35 6542 Lyss – Kerzers

View line S35

Lyss 23:36 → Kerzers 23:55 Daily 0 h 19 min · 8 stops BLS

It has not run yet today

Last recorded run: Thursday 12 November +1 min

Next service: today 23:36 from Lyss · Fri 13 Nov

Next departure 23:36 today · Lyss
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
93%
54/58 runs under 3 min
RT coverage: 58 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

  • Thu 27 Aug Max en route +25 min · last fix heading to Kerzers +25 min
  • Wed 21 Oct Max en route +7 min · last fix heading to Kerzers +7 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Kerzers +7 min
  • Fri 30 Oct Max en route +7 min · last fix heading to Kerzers +6 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=11
  • 100% T n=6
  • 88% W n=8
  • 88% T n=8
  • 83% F n=6
  • 100% S n=8
  • 91% S n=11

Stops and timetable

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

Last 90 days, 58 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
23:36+1 min +1 min
23:38≈ +1 min ≈ +1 min
23:42≈ +1 min ≈ +1 min
23:44≈ +1 min ≈ +2 min
23:47≈ +1 min ≈ +2 min
23:50≈ +1 min ≈ +2 min
23:52≈ +1 min ≈ +2 min
23:55+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
Thu 12 NovKerzers 23:57+1 min—
Wed 11 NovKerzers 23:57+1 min+1 min
Tue 10 NovKerzers 23:58+1 min+1 min
Mon 9 NovKerzers 23:58+2 min+2 min
Sun 8 NovKerzers 23:59+3 min+3 min
Sat 7 NovKerzers 23:54+1 min—
Fri 6 NovKerzers 23:59+2 min+2 min
Thu 5 NovKerzers 23:57+1 min—
Wed 4 NovKerzers 23:58+2 min+2 min
Tue 3 NovKerzers 23:57+1 min+1 min
Mon 2 NovKerzers 23:57+1 min+1 min
Sun 1 NovKerzers 23:570 min—
Sat 31 OctKerzers 23:57+1 min—
Fri 30 OctKerzers 00:01+6 min+7 min
Thu 29 OctKerzers 23:57+1 min—
Wed 28 OctKerzers 23:560 min—
Tue 27 OctKerzers 23:570 min—
Mon 26 OctKerzers 23:57+1 min+1 min
Sun 25 OctKerzers 23:57+2 min+2 min
Sat 24 OctKerzers 23:58+2 min+2 min
Fri 23 OctKerzers 23:58+2 min+2 min
Thu 22 OctKerzers 23:57+1 min—
Wed 21 OctKerzers 00:03+7 min+7 min
Tue 20 OctKerzers 23:570 min—
Mon 19 OctKerzers 23:56+1 min—
Sun 18 OctKerzers 00:03+7 min+7 min
Sat 17 OctKerzers 23:58+2 min+2 min
Fri 16 OctKerzers 23:570 min—
Thu 15 OctKerzers 23:59+3 min+3 min
Wed 14 OctKerzers 23:57+1 min+2 min