S35 6512 Lyss – Kerzers

View line S35

Lyss 08:35 → Kerzers 08:55 Daily 0 h 20 min · 8 stops BLS

✓ Today’s run finished

Today it reached Kerzers at 08:55 0 min

  1. Lyss08:35
  2. Lyss Grien08:37
  3. Aarberg08:41
  4. Kallnach08:46
  5. Fräschels08:50
  6. Kerzers Papiliorama08:52
  7. Kerzers08:55

Next service: tomorrow 08:35 from Lyss · Sat 7 Nov

Next departure 08:35 tomorrow · Lyss
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 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: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 33 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
08:35on time on time
08:37≈ on time ≈ on time
08:41≈ on time ≈ on time
08:43≈ on time ≈ on time
08:46≈ on time ≈ on time
08:50≈ on time ≈ +1 min
08:52≈ on time ≈ +1 min
08:55on 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 6 NovKerzers 08:540 min—
Thu 5 NovKerzers 08:540 min—
Wed 4 NovKerzers 08:540 min—
Tue 3 NovKerzers 08:540 min—
Mon 2 NovKerzers 08:540 min—
Sun 1 NovKerzers 08:560 min—
Sat 31 OctKerzers 08:57+1 min—
Fri 30 OctKerzers 08:560 min—
Thu 29 OctKerzers 08:560 min—
Wed 28 OctKerzers 08:57+1 min+1 min
Tue 27 OctKerzers 08:560 min—
Mon 26 OctKerzers 08:560 min—
Sun 25 OctKerzers 08:56+1 min—
Sat 24 OctKerzers 08:57+1 min—
Fri 23 OctKerzers 08:56+1 min—
Thu 22 OctKerzers 08:570 min—
Wed 21 OctKerzers 08:57+1 min—
Tue 20 OctKerzers 08:57No data—
Mon 19 OctKerzers 08:560 min—
Sun 18 OctKerzers 08:560 min—
Sat 17 OctKerzers 08:560 min—
Fri 16 OctKerzers 08:560 min—
Thu 15 OctKerzers 08:560 min—
Wed 14 OctKerzers 08:55−1 min—
Tue 13 OctKerzers 08:57+1 min—
Mon 12 OctKerzers 08:56+1 min—
Sun 11 OctKerzers 08:560 min—
Sat 10 OctKerzers 08:57+1 min—
Fri 9 OctKerzers 08:55−1 min—
Thu 8 OctKerzers 08:58+2 min+2 min