S5 15781 Neuchâtel – Kerzers

View line S5

Neuchâtel 16:04 → Kerzers 16:27 Daily 0 h 23 min · 8 stops BLS

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 16:04 from Neuchâtel · Thu 19 Nov

Next departure 16:04 today · Neuchâtel
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
98%
52/53 runs under 3 min
RT coverage: 53 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Wed 30 Sept Max en route +4 min · last fix heading to Kerzers +3 min

Distribution · 90 days

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

  • Early 23% · 12
  • On time 75% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=6
  • 89% W n=9
  • 100% T n=6
  • 100% F n=7
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 53 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
16:04on time on time
16:07≈ on time ≈ on time
16:10≈ on time ≈ on time
16:11≈ on time ≈ on time
16:14≈ on time ≈ on time
16:18≈ on time ≈ on time
16:20≈ on time ≈ on time
16:27on 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
Wed 18 NovKerzers 21:270 min—
Tue 17 NovKerzers 21:28−1 min—
Mon 16 NovKerzers 21:27−1 min—
Sun 15 NovKerzers 21:270 min—
Sat 14 NovKerzers 21:24−1 min—
Fri 13 NovKerzers 21:27−1 min—
Thu 12 NovKerzers 21:27−1 min—
Wed 11 NovKerzers 21:27−1 min—
Tue 10 NovKerzers 21:270 min—
Mon 9 NovKerzers 21:27−1 min—
Sun 8 NovKerzers 21:280 min—
Sat 7 NovKerzers 21:29+3 min+3 min
Fri 6 NovKerzers 21:270 min—
Thu 5 NovKerzers 21:24−1 min—
Wed 4 NovKerzers 21:24−1 min—
Tue 3 NovKerzers 21:280 min—
Mon 2 NovKerzers 21:280 min—
Sun 1 NovKerzers 21:27−2 min—
Sat 31 OctKerzers 21:280 min—
Fri 30 OctKerzers 21:29+1 min+2 min
Thu 29 OctKerzers 21:27−1 min—
Wed 28 OctKerzers 21:280 min—
Tue 27 OctKerzers 21:28No data—
Mon 26 OctKerzers 21:280 min—
Sun 25 OctKerzers 21:27−1 min—
Sat 24 OctKerzers 21:280 min—
Fri 23 OctKerzers 21:280 min—
Thu 22 OctKerzers 21:27−1 min—
Wed 21 OctKerzers 21:27−1 min—
Tue 20 OctKerzers 21:27−1 min—