S14 23816 Berg – Konstanz

View line S14

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

✓ Today’s run finished

Today it reached Konstanz at 18:35 0 min

  1. Berg18:16
  2. Siegershausen18:19
  3. Lengwil18:22
  4. Kreuzlingen Bernrain18:25
  5. Tägerwilen Dorf18:28
  6. Kreuzlingen18:32
  7. Konstanz18:35

Next service: tomorrow 18:16 from Berg · Fri 6 Nov

Next departure 18:16 tomorrow · Berg
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%
40/40 runs under 3 min
RT coverage: 40 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 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

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

  • Early 0% · 0
  • On time 100% · 40
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 100% W n=7
  • 100% T n=9
  • 100% F n=5
  • 100% S n=4
  • 100% S n=1

Stops and timetable

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

Last 90 days, 40 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
18:16on time on time
18:19≈ on time ≈ on time
18:22≈ on time ≈ on time
18:25≈ on time ≈ +1 min
18:28≈ on time ≈ +1 min
18:32≈ on time ≈ +1 min
18: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
Thu 5 NovKonstanz 06:040 min—
Wed 4 NovKonstanz 06:040 min—
Tue 3 NovKonstanz 06:040 min—
Mon 2 NovKonstanz 06:040 min—
Sat 31 OctKonstanz 06:060 min—
Fri 30 OctKonstanz 06:060 min—
Thu 29 OctKonstanz 06:08+1 min+1 min
Wed 28 OctKonstanz 06:07+1 min+2 min
Tue 27 OctKonstanz 06:060 min—
Mon 26 OctKonstanz 06:060 min—
Sat 24 OctKonstanz 06:060 min—
Fri 23 OctKonstanz 06:060 min—
Thu 22 OctKonstanz 06:060 min—
Wed 21 OctKonstanz 06:060 min—
Tue 20 OctKonstanz 06:060 min—
Mon 19 OctKonstanz 06:060 min—
Sat 17 OctKonstanz 06:050 min—
Fri 16 OctKonstanz 06:05+1 min+1 min
Thu 15 OctKonstanz 06:050 min—
Wed 14 OctKonstanz 06:040 min—
Tue 13 OctKonstanz 06:040 min—
Mon 12 OctKonstanz 06:040 min—
Sun 11 OctKonstanz 06:050 min—
Sat 10 OctKonstanz 06:050 min—
Fri 9 OctKonstanz 06:040 min—
Thu 8 OctKonstanz 06:050 min—
Wed 7 OctKonstanz 06:040 min—
Tue 6 OctKonstanz 06:050 min—
Mon 5 OctKonstanz 06:050 min—
Thu 17 SeptKonstanz 00:020 min+3 min