S14 23910 Berg – Konstanz

View line S14

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 21:16 from Berg · Sat 7 Nov

Next departure 21:16 today · Berg
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 41 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

Worst days

  • Fri 25 Sept Max en route +3 min · last fix heading to Kreuzlingen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=6
  • 100% T n=6
  • 86% 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, 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
21:16on time on time
21:19≈ on time ≈ on time
21:22≈ on time ≈ on time
21:25≈ on time ≈ on time
21:28≈ on time ≈ on time
21:32≈ on time ≈ +1 min
21: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 21:340 min—
Thu 5 NovKonstanz 21:340 min—
Wed 4 NovKonstanz 21:340 min—
Tue 3 NovKonstanz 21:340 min—
Mon 2 NovKonstanz 21:340 min—
Sun 1 NovKonstanz 21:340 min—
Sat 31 OctKonstanz 21:35−1 min—
Fri 30 OctKonstanz 21:360 min—
Thu 29 OctKonstanz 21:360 min—
Wed 28 OctKonstanz 21:37+1 min—
Tue 27 OctKonstanz 21:360 min—
Mon 26 OctKonstanz 21:36−1 min—
Sun 25 OctKonstanz 21:360 min—
Sat 24 OctKonstanz 21:36+1 min—
Fri 23 OctKonstanz 21:360 min—
Thu 22 OctKonstanz 21:35−1 min—
Wed 21 OctKonstanz 21:360 min—
Tue 20 OctKonstanz 21:36−1 min—
Mon 19 OctKonstanz 21:360 min—
Sun 18 OctKonstanz 21:360 min—
Sat 17 OctKonstanz 21:350 min—
Fri 16 OctKonstanz 21:350 min—
Thu 15 OctKonstanz 21:350 min—
Wed 14 OctKonstanz 21:360 min—
Tue 13 OctKonstanz 21:36+1 min—
Mon 12 OctKonstanz 21:350 min—
Sun 11 OctKonstanz 21:350 min—
Sat 10 OctKonstanz 21:36+1 min—
Fri 9 OctKonstanz 21:35−1 min—
Thu 8 OctKonstanz 21:36+1 min+1 min