S14 23802 Weinfelden → Konstanz

View line S14

Weinfelden 00:06 → Konstanz 00:34 Daily 0 h 28 min · 9 stops Thurbo

✓ Today’s run finished

Today it reached Konstanz at 00:34 0 min

  1. Weinfelden00:06
  2. Kehlhof00:11
  3. Siegershausen00:17
  4. Lengwil00:21
  5. Kreuzlingen Bernrain00:24
  6. Kreuzlingen00:30
  7. Konstanz00:34

Next service: tomorrow 00:06 from Weinfelden · Sun 22 Nov

Next departure 00:06 tomorrow · Weinfelden
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
58/59 runs under 3 min
RT coverage: 59 full · 0 partial · 1 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: +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

  • Wed 4 Nov Max en route +8 min · last fix heading to Konstanz +7 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=8
  • 100% T n=9
  • 88% W n=8
  • 100% T n=9
  • 100% F n=11
  • 100% S n=8
  • 100% S n=6

Stops and timetable

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

Last 90 days, 59 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
00:06on time +1 min
00:11≈ on time ≈ +1 min
00:14≈ on time ≈ +1 min
00:17≈ on time ≈ +1 min
00:21≈ on time ≈ +1 min
00:24≈ on time ≈ +1 min
00:26≈ on time ≈ +1 min
00:30 / 00:31≈ on time ≈ +1 min
00:34on 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
Sat 21 NovKonstanz 00:340 min—
Fri 20 NovKonstanz 00:37+2 min+2 min
Thu 19 NovKonstanz 00:340 min—
Wed 18 NovKonstanz 00:37+1 min+1 min
Tue 17 NovKonstanz 00:37+2 min+2 min
Mon 16 NovKonstanz 00:34+1 min—
Sun 15 NovKonstanz 00:34+1 min—
Sat 14 NovKonstanz 00:340 min—
Fri 13 NovKonstanz 00:35+1 min—
Thu 12 NovKonstanz 00:340 min—
Wed 11 NovKonstanz 00:34+1 min+1 min
Tue 10 NovKonstanz 00:35+1 min—
Mon 9 NovKonstanz 00:34−1 min—
Sun 8 NovKonstanz 00:34+1 min—
Sat 7 NovKonstanz 00:34+1 min—
Fri 6 NovKonstanz 00:34+1 min—
Thu 5 NovKonstanz 00:34+1 min—
Wed 4 NovKonstanz 00:42+7 min+8 min
Tue 3 NovKonstanz 00:34+1 min—
Mon 2 NovKonstanz 00:34+1 min—
Sun 1 NovKonstanz 00:36+1 min+1 min
Sat 31 OctKonstanz 00:36+1 min—
Fri 30 OctKonstanz 00:36+1 min—
Thu 29 OctKonstanz 00:38+3 min+3 min
Wed 28 OctKonstanz 00:36+1 min—
Tue 27 OctKonstanz 00:36+1 min+3 min
Mon 26 OctKonstanz 00:35+1 min—
Sun 25 OctKonstanz 01:35No data—
Sat 24 OctKonstanz 00:36+1 min+2 min
Fri 23 OctKonstanz 00:36+1 min—