S35 6532 Lyss – Kerzers

View line S35

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

✓ Today’s run finished

Today it reached Kerzers at 18:55 0 min

  1. Lyss18:35
  2. Lyss Grien18:37
  3. Aarberg18:41
  4. Kallnach18:46
  5. Fräschels18:50
  6. Kerzers Papiliorama18:52
  7. Kerzers18:55

Next service: tomorrow 18:35 from Lyss · Sun 8 Nov

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

Worst days

  • Mon 5 Oct Max en route +8 min · last fix heading to Kerzers +8 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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