Train 512

RorschachLausanne

Passages not confirmedTimes reported by the data source. Passages are not confirmed.

Historical average delay — home ranking

+0.1 min

Average of available delays per run over the 30 days before calculation, with equal weight for each eligible run. This is not the current delay.

Runs used: 10. Calculated on: 9/11/2026, 1:00:25 AM (Europe/Paris).

This average can be available without a complete route. The route statistics below use only recorded routes with their stops.

Calculation window: 8/12/2026, 1:00:25 AM – 9/11/2026, 1:00:25 AM (Europe/Paris).

Runs in the window: 12
Events confirmed by the source: 0
Events predicted by the source: 1
Unknown event type: 9
Cancelled runs, excluded: 1
No usable delay, excluded: 1

Latest source timestamp: 9/10/2026, 10:20:28 AM (Europe/Paris).

Runs are identified within each source. Identities across sources are kept separate without a proven match. Exclusions can overlap.

Latest available run: these times are historical.

Stops on the latest run

Rorschach
Departure
Scheduled time06:39
Predicted by the source06:39(0′)
St. Gallen
Arrival
Scheduled time06:55
Predicted by the source06:55(0′)
Departure
Scheduled time06:58
Predicted by the source06:58(0′)
Winterthur
Arrival
Scheduled time07:31
Predicted by the source07:31(0′)
Departure
Scheduled time07:33
Predicted by the source07:33(0′)
Zürich Flughafen
Arrival
Scheduled time07:47
Predicted by the source07:47(0′)
Departure
Scheduled time07:49
Predicted by the source07:49(0′)
Zürich HB
Arrival
Scheduled time07:58
Predicted by the source07:59(+1′)
Departure
Scheduled time08:04
Predicted by the source08:07(+3′)
Aarau
Arrival
Scheduled time08:28
Predicted by the source08:31(+3′)
Departure
Scheduled time08:30
Predicted by the source08:33(+3′)
Olten
Arrival
Scheduled time08:39
Predicted by the source08:43(+4′)
Departure
Scheduled time08:41
Predicted by the source08:45(+4′)
Solothurn
Arrival
Scheduled time08:58
Predicted by the source09:00(+2′)
Departure
Scheduled time08:59
Predicted by the source09:01(+2′)
Biel/Bienne
Arrival
Scheduled time09:14
Predicted by the source09:15(+1′)
Departure
Scheduled time09:18
Predicted by the source09:18(0′)
Neuchâtel
Arrival
Scheduled time09:37
Predicted by the source09:37(0′)
Departure
Scheduled time09:39
Predicted by the source09:40(+1′)
Yverdon-les-Bains
Arrival
Scheduled time09:58
Predicted by the source09:58(0′)
Departure
Scheduled time09:59
Predicted by the source10:01(+2′)
Renens VD
Arrival
Scheduled time10:18
Predicted by the source10:19(+1′)
Departure
Scheduled time10:20
Predicted by the source10:20(0′)
Lausanne
Arrival
Scheduled time10:26
Predicted by the source10:26(0′)

Punctuality of recorded routes

Reported delays per run with a complete route; separate from the ranking sample. A predicted delay does not confirm a passage.

Cancelled runs are excluded from the punctuality calculation.

runs reported on time—

average delay+0.2 min

max delay+4 min

runs reported11

cancelled runs1

stops13

Delay values

DateDelay (min)

2026-08-270.15384615384615385

2026-08-280.07692307692307693

2026-08-290.3076923076923077

2026-08-310.07692307692307693

2026-09-030.15384615384615385

2026-09-050

2026-09-060

2026-09-070.07692307692307693

2026-09-080

2026-09-090.5384615384615384

2026-09-101.1538461538461537

Typical schedule

Stops and times of Train 512 from Rorschach to Lausanne on a typical weekday. Actual times may vary.

StopArrivalDeparture

Rorschach—06:39

St. Gallen06:5506:58

Winterthur07:3107:33

Zürich Flughafen07:4707:49

Zürich HB07:5808:04

Aarau08:2808:30

Olten08:3908:41

Solothurn08:5808:59

Biel/Bienne09:1409:18

Neuchâtel09:3709:39

Yverdon-les-Bains09:5809:59

Renens VD10:1810:20

Lausanne10:26—

Frequently asked questions

What time does Train 512 depart?

Train 512 departs from Rorschach at 06:39 (typical schedule from reported times). Actual times may vary.

How many stops does Train 512 make?

Train 512 connects Rorschach to Lausanne with 13 stops.

Is Train 512 on time?

Over the reported runs, every run of Train 512 was cancelled (1 run): punctuality cannot be established.

Back to the list