S19 19951 Dietikon – Effretikon

View line S19

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 13:34 from Dietikon · Wed 18 Nov

Next departure 13:34 today · Dietikon
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 7 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 22 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: +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

Distribution · 90 days

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

  • Early 9% · 2
  • On time 91% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=6
  • 100% T n=2
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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:34on time on time
13:39 / 13:40≈ on time ≈ on time
13:45 / 13:49≈ on time ≈ on time
13:54 / 13:55≈ on time ≈ on time
13:58 / 13:59≈ on time ≈ on time
14:01 / 14:02≈ on time ≈ on time
14:08on 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
Tue 17 NovEffretikon 14:090 min—
Mon 16 NovEffretikon 14:09No data—
Fri 13 NovEffretikon 14:09−1 min—
Thu 12 NovEffretikon 14:09No data—
Wed 11 NovEffretikon 14:09+1 min—
Tue 10 NovEffretikon 14:08−1 min—
Mon 9 NovEffretikon 14:09No data—
Fri 6 NovEffretikon 14:090 min—
Thu 5 NovEffretikon 14:08−1 min—
Wed 4 NovEffretikon 14:090 min—
Tue 3 NovEffretikon 14:090 min—
Mon 2 NovEffretikon 14:09No data—
Fri 30 OctEffretikon 14:090 min—
Thu 29 OctEffretikon 14:09No data—
Wed 28 OctEffretikon 14:12+3 min+3 min
Tue 27 OctEffretikon 14:08−1 min—
Mon 26 OctEffretikon 14:09No data—
Fri 23 OctEffretikon 14:09+1 min—
Thu 22 OctEffretikon 14:09No data—
Wed 21 OctEffretikon 14:08−1 min—
Tue 20 OctEffretikon 14:09−1 min—
Mon 19 OctEffretikon 14:09No data—
Fri 16 OctEffretikon 14:090 min—
Thu 15 OctEffretikon 14:09No data—
Wed 14 OctEffretikon 14:08−1 min—
Tue 13 OctEffretikon 14:09−1 min—
Mon 12 OctEffretikon 14:09No data—
Fri 9 OctEffretikon 14:090 min—
Thu 8 OctEffretikon 14:090 min—
Wed 7 OctEffretikon 14:090 min—