RE1 5231 Herisau – Konstanz

View line RE1

Herisau 09:05 → Konstanz 09:50 Daily 0 h 45 min · 5 stops Thurbo

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: tomorrow 09:05 from Herisau · Fri 20 Nov

Next departure 09:05 tomorrow · Herisau
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 46 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: +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 28 Oct Max en route +3 min · last fix heading to Konstanz +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 86% W n=7
  • 100% T n=5
  • 100% F n=6
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

Last 90 days, 46 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:05on time on time
09:14 / 09:15≈ on time ≈ +1 min
09:33≈ on time ≈ +1 min
09:47≈ on time ≈ +1 min
09:50on 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
Wed 18 NovKonstanz 16:52+1 min—
Tue 17 NovKonstanz 16:53+1 min+1 min
Mon 16 NovKonstanz 16:52+2 min+2 min
Sun 15 NovKonstanz 16:490 min—
Sat 14 NovKonstanz 16:490 min—
Fri 13 NovKonstanz 16:520 min—
Thu 12 NovKonstanz 16:49No data—
Wed 11 NovKonstanz 16:490 min—
Tue 10 NovKonstanz 16:490 min—
Mon 9 NovKonstanz 16:490 min—
Sun 8 NovKonstanz 16:53+1 min+4 min
Sat 7 NovKonstanz 16:490 min—
Fri 6 NovKonstanz 16:53+2 min+2 min
Thu 5 NovKonstanz 16:490 min—
Wed 4 NovKonstanz 16:490 min—
Tue 3 NovKonstanz 16:520 min—
Mon 2 NovKonstanz 16:520 min—
Sun 1 NovKonstanz 16:50−1 min—
Sat 31 OctKonstanz 16:52+1 min+1 min
Fri 30 OctKonstanz 16:53+2 min+2 min
Thu 29 OctKonstanz 16:52+1 min+1 min
Wed 28 OctKonstanz 16:54+3 min+3 min
Tue 27 OctKonstanz 16:510 min—
Mon 26 OctKonstanz 16:51−1 min—
Sun 25 OctKonstanz 16:50−1 min—
Sat 24 OctKonstanz 16:510 min—
Fri 23 OctKonstanz 16:53+1 min+1 min
Thu 22 OctKonstanz 16:52+1 min—
Wed 21 OctKonstanz 16:510 min—
Tue 20 OctKonstanz 16:53+1 min+1 min