S14 23873 Konstanz – Berg

View line S14

Konstanz 15:24 → Berg 15:42 Daily 0 h 18 min · 7 stops Thurbo

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 15:24 from Konstanz · Sat 7 Nov

Next departure 15:24 today · Konstanz
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
42/42 runs under 3 min
RT coverage: 42 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 Berg, 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

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

  • Early 2% · 1
  • On time 98% · 41
  • 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=5
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

Last 90 days, 42 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
15:24on time +1 min
15:26 / 15:27≈ on time ≈ +1 min
15:29≈ on time ≈ +1 min
15:32≈ on time ≈ +1 min
15:35 / 15:36≈ on time ≈ +1 min
15:39≈ on time ≈ +1 min
15:42on 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 NovBerg 15:430 min—
Thu 5 NovBerg 15:44+1 min—
Wed 4 NovBerg 15:44+1 min—
Tue 3 NovBerg 15:44+1 min—
Mon 2 NovBerg 15:42−1 min—
Sun 1 NovBerg 15:44+1 min—
Sat 31 OctBerg 15:430 min—
Fri 30 OctBerg 15:44+1 min—
Thu 29 OctBerg 15:430 min—
Wed 28 OctBerg 15:44+1 min—
Tue 27 OctBerg 15:430 min—
Mon 26 OctBerg 15:430 min—
Sun 25 OctBerg 15:430 min—
Sat 24 OctBerg 15:42−1 min—
Fri 23 OctBerg 15:43+1 min—
Thu 22 OctBerg 15:44+1 min—
Wed 21 OctBerg 15:430 min—
Tue 20 OctBerg 15:45+1 min+2 min
Mon 19 OctBerg 15:43+1 min—
Sun 18 OctWeinfelden 15:57+2 min+2 min
Sat 17 OctWeinfelden 15:54−1 min—
Fri 16 OctWeinfelden 15:57+1 min+1 min
Thu 15 OctWeinfelden 15:550 min—
Wed 14 OctWeinfelden 15:54−1 min—
Tue 13 OctWeinfelden 15:54−1 min—
Mon 12 OctWeinfelden 15:54−1 min—
Sun 11 OctWeinfelden 15:550 min—
Sat 10 OctWeinfelden 15:550 min—
Fri 9 OctWeinfelden 15:550 min—
Thu 8 OctWeinfelden 15:57+2 min+2 min