S19 19949 Dietikon – Effretikon

View line S19

Dietikon 13:04 → Effretikon 13:38 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 7 stops SBB CFF FFS

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: tomorrow 13:04 from Dietikon · Mon 9 Nov

Next departure 13:04 tomorrow · Dietikon
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 12 full · 0 partial · 8 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 8 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 Effretikon, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 8 Oct Max en route +5 min · last fix heading to Effretikon +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=5
  • 0% T n=1
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 17 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
13:04on time on time
13:09 / 13:10≈ on time ≈ on time
13:15 / 13:19≈ on time ≈ on time
13:24 / 13:25≈ on time ≈ +1 min
13:28 / 13:29≈ on time ≈ +1 min
13:31 / 13:32≈ on time ≈ +1 min
13:38on 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 NovEffretikon 13:39+1 min—
Thu 5 NovEffretikon 13:39No data—
Wed 4 NovEffretikon 13:390 min—
Tue 3 NovEffretikon 13:390 min—
Mon 2 NovEffretikon 13:39No data—
Fri 30 OctEffretikon 13:390 min—
Thu 29 OctEffretikon 13:39No data—
Wed 28 OctEffretikon 13:40+1 min—
Tue 27 OctEffretikon 13:390 min—
Mon 26 OctEffretikon 13:39No data—
Fri 23 OctEffretikon 13:390 min—
Thu 22 OctEffretikon 13:39No data—
Wed 21 OctEffretikon 13:390 min—
Tue 20 OctEffretikon 13:390 min—
Mon 19 OctEffretikon 13:39No data—
Fri 16 OctEffretikon 13:390 min—
Thu 15 OctEffretikon 13:39No data—
Wed 14 OctEffretikon 13:390 min—
Tue 13 OctEffretikon 13:400 min—
Mon 12 OctEffretikon 13:39No data—
Fri 9 OctEffretikon 13:390 min—
Thu 8 OctEffretikon 13:44+5 min+5 min
Wed 7 OctEffretikon 13:390 min—
Tue 6 OctEffretikon 13:41+1 min+1 min
Mon 5 OctEffretikon 13:360 min—