S14 23858 Weinfelden – Konstanz

View line S14

Weinfelden 12:36 → Konstanz 13:03 Daily 0 h 27 min · 9 stops Thurbo

✓ Today’s run finished

Today it reached Konstanz at 13:03 0 min

  1. Weinfelden12:36
  2. Kehlhof12:41
  3. Siegershausen12:47
  4. Lengwil12:50
  5. Kreuzlingen Bernrain12:53
  6. Kreuzlingen13:00
  7. Konstanz13:03

Next service: tomorrow 12:36 from Weinfelden · Sat 14 Nov

Next departure 12:36 tomorrow · Weinfelden
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 9 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 10 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: +2 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 23 Oct Max en route +3 min · last fix heading to Konstanz +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=7
  • 100% W n=6
  • 100% T n=1
  • 88% F n=8
  • 100% S n=6
  • 100% S n=2

Stops and timetable

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

Last 90 days, 34 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
12:36on time on time
12:41≈ on time ≈ on time
12:44≈ on time ≈ on time
12:47≈ on time ≈ on time
12:50≈ on time ≈ on time
12:53≈ on time ≈ on time
12:56≈ on time ≈ on time
13:00≈ on time ≈ +1 min
13:03on 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 13 NovKonstanz 13:040 min—
Thu 12 NovKonstanz 13:04No data—
Wed 11 NovKonstanz 13:040 min—
Tue 10 NovKonstanz 13:040 min—
Mon 9 NovKonstanz 13:04No data—
Sat 7 NovKonstanz 13:040 min—
Fri 6 NovKonstanz 13:040 min—
Thu 5 NovKonstanz 13:04No data—
Wed 4 NovKonstanz 13:040 min—
Tue 3 NovKonstanz 13:040 min—
Mon 2 NovKonstanz 13:04No data—
Sat 31 OctKonstanz 13:07+1 min—
Fri 30 OctKonstanz 13:060 min—
Thu 29 OctKonstanz 13:06No data—
Wed 28 OctKonstanz 13:060 min—
Tue 27 OctKonstanz 13:060 min—
Mon 26 OctKonstanz 13:06No data—
Sat 24 OctKonstanz 13:07+1 min+1 min
Fri 23 OctKonstanz 13:09+3 min+3 min
Thu 22 OctKonstanz 13:06No data—
Wed 21 OctKonstanz 13:060 min—
Tue 20 OctKonstanz 13:06−1 min—
Mon 19 OctKonstanz 13:06No data—
Sun 18 OctKonstanz 13:050 min—
Sat 17 OctKonstanz 13:040 min—
Fri 16 OctKonstanz 13:07+3 min+3 min
Thu 15 OctKonstanz 13:04No data—
Wed 14 OctKonstanz 13:040 min—
Tue 13 OctKonstanz 13:050 min—
Mon 12 OctKonstanz 13:04No data—