S5 15717 Neuchâtel – Kerzers

View line S5

Neuchâtel 05:02 → Kerzers 05:24 Mon, Tue, Wed, Thu, Fri 0 h 22 min · 8 stops BLS

✓ Today’s run finished

Today it reached Kerzers at 05:24 0 min

  1. Neuchâtel05:02
  2. St-Blaise-Lac05:05
  3. Marin-Epagnier05:09
  4. Gampelen05:12
  5. Ins05:16
  6. Müntschemier05:19
  7. Kerzers05:24

Next service: tomorrow 05:02 from Neuchâtel · Thu 19 Nov

Next departure 05:02 tomorrow · Neuchâtel
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 28 Oct Max en route +4 min · last fix heading to Kerzers +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=10
  • 89% W n=9
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 38 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
05:02on time on time
05:05≈ on time ≈ on time
05:09≈ on time ≈ +1 min
05:10≈ on time ≈ +1 min
05:12≈ on time ≈ +1 min
05:16 / 05:17≈ on time ≈ +1 min
05:19≈ on time ≈ +1 min
05:24on time +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
Wed 18 NovKerzers 05:240 min—
Tue 17 NovKerzers 05:240 min—
Mon 16 NovKerzers 05:240 min—
Fri 13 NovKerzers 05:250 min—
Thu 12 NovKerzers 05:240 min—
Wed 11 NovKerzers 05:240 min—
Tue 10 NovKerzers 05:240 min—
Mon 9 NovKerzers 05:240 min—
Fri 6 NovKerzers 05:28+2 min+2 min
Thu 5 NovKerzers 05:240 min—
Wed 4 NovKerzers 05:240 min—
Tue 3 NovKerzers 05:27+1 min+1 min
Mon 2 NovKerzers 05:240 min—
Fri 30 OctKerzers 05:26+1 min—
Thu 29 OctKerzers 05:26+1 min—
Wed 28 OctKerzers 05:29+4 min+4 min
Tue 27 OctKerzers 05:26+1 min—
Mon 26 OctKerzers 05:26+1 min+1 min
Fri 23 OctKerzers 05:250 min—
Thu 22 OctKerzers 05:250 min—
Wed 21 OctKerzers 05:27+2 min+2 min
Tue 20 OctKerzers 05:25+1 min—
Mon 19 OctKerzers 05:27+2 min+2 min
Fri 16 OctKerzers 05:25+1 min—
Thu 15 OctKerzers 05:27+2 min+2 min
Wed 14 OctKerzers 05:26+1 min—
Tue 13 OctKerzers 05:25+1 min—
Mon 12 OctKerzers 05:26+1 min—
Fri 9 OctKerzers 05:26+1 min—
Thu 8 OctKerzers 05:260 min—