S14 23838 Berg – Konstanz

View line S14

Berg 09:16 → Konstanz 09:35 Daily 0 h 19 min · 7 stops Thurbo

✓ Today’s run finished

Today it reached Konstanz at 09:35 0 min

  1. Berg09:16
  2. Siegershausen09:19
  3. Lengwil09:22
  4. Kreuzlingen Bernrain09:25
  5. Tägerwilen Dorf09:28
  6. Kreuzlingen09:32
  7. Konstanz09:35

Next service: tomorrow 09:16 from Berg · Sat 7 Nov

Next departure 09:16 tomorrow · Berg
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 36 full · 0 partial · 1 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 Konstanz, 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

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

  • Early 0% · 0
  • On time 100% · 36
  • 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=7
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 100% S n=4
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
09:16on time on time
09:19≈ on time ≈ on time
09:22≈ on time ≈ on time
09:25≈ on time ≈ +1 min
09:28≈ on time ≈ +1 min
09:32≈ on time ≈ +1 min
09:35on 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 NovKonstanz 09:340 min—
Thu 5 NovKonstanz 09:34−1 min—
Wed 4 NovKonstanz 09:340 min—
Tue 3 NovKonstanz 09:340 min—
Mon 2 NovKonstanz 09:370 min—
Sun 1 NovKonstanz 09:360 min—
Sat 31 OctKonstanz 09:36+1 min—
Fri 30 OctKonstanz 09:37+1 min+1 min
Thu 29 OctKonstanz 09:36No data—
Wed 28 OctKonstanz 09:37+1 min—
Tue 27 OctKonstanz 09:36−1 min—
Mon 26 OctKonstanz 09:37+1 min—
Sun 25 OctKonstanz 09:360 min—
Sat 24 OctKonstanz 09:37+1 min+1 min
Fri 23 OctKonstanz 09:360 min—
Thu 22 OctKonstanz 09:360 min—
Wed 21 OctKonstanz 09:36−1 min—
Tue 20 OctKonstanz 09:370 min—
Mon 19 OctKonstanz 09:35−1 min—
Sun 18 OctKonstanz 09:360 min—
Sat 17 OctKonstanz 09:350 min—
Fri 16 OctKonstanz 09:350 min—
Thu 15 OctKonstanz 09:36+1 min—
Wed 14 OctKonstanz 09:36+1 min+1 min
Tue 13 OctKonstanz 09:360 min—
Mon 12 OctKonstanz 09:36+1 min+2 min
Sun 11 OctKonstanz 09:350 min—
Sat 10 OctKonstanz 09:38+3 min+3 min
Fri 9 OctKonstanz 09:37+3 min+3 min
Thu 8 OctKonstanz 09:350 min—