S14 23901 Konstanz – Berg

View line S14

Konstanz 19:54 → Berg 20:12 Daily 0 h 18 min · 7 stops Thurbo

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 19:54 from Konstanz · Fri 6 Nov

Next departure 19:54 today · Konstanz
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
100%
41/41 runs under 3 min
RT coverage: 41 full · 0 partial · 0 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: +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

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

  • Early 10% · 4
  • On time 90% · 37
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 41 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
19:54on time +1 min
19:56 / 19:57≈ on time ≈ +1 min
19:59≈ on time ≈ +1 min
20:02≈ on time ≈ +1 min
20:05 / 20:06≈ on time ≈ +1 min
20:09≈ on time ≈ +1 min
20:12on 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
Thu 5 NovBerg 20:130 min—
Wed 4 NovBerg 20:14+1 min—
Tue 3 NovBerg 20:14+1 min+4 min
Mon 2 NovBerg 20:130 min—
Sat 31 OctBerg 20:15+2 min+2 min
Fri 30 OctBerg 20:14+1 min—
Thu 29 OctBerg 20:14+1 min+1 min
Wed 28 OctBerg 20:130 min—
Tue 27 OctBerg 20:14+1 min—
Mon 26 OctBerg 20:14+1 min—
Sat 24 OctBerg 20:14+1 min+1 min
Fri 23 OctBerg 20:14+1 min+2 min
Thu 22 OctBerg 20:14+1 min—
Wed 21 OctBerg 20:14+1 min+1 min
Tue 20 OctBerg 20:140 min—
Mon 19 OctBerg 20:13+1 min—
Sun 18 OctKreuzlingen 19:58+1 min—
Sat 17 OctWeinfelden 20:24−1 min—
Fri 16 OctWeinfelden 20:27+1 min+2 min
Thu 15 OctWeinfelden 20:250 min—
Wed 14 OctWeinfelden 20:250 min—
Tue 13 OctWeinfelden 20:24−2 min—
Mon 12 OctWeinfelden 20:240 min—
Sun 11 OctKreuzlingen 19:58+1 min—
Sat 10 OctWeinfelden 20:250 min—
Fri 9 OctWeinfelden 20:25−1 min—
Thu 8 OctWeinfelden 20:24−1 min—
Wed 7 OctWeinfelden 20:25−1 min—
Tue 6 OctWeinfelden 20:26+1 min+1 min
Mon 5 OctWeinfelden 20:25−1 min—