S19 19959 Dietikon – Effretikon

View line S19

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

It has not run yet today

Last recorded run: Thursday 19 November −1 min

Next service: today 15:34 from Dietikon · Fri 20 Nov

Next departure 15:34 today · Dietikon
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 12 Nov Max en route +4 min · last fix heading to Effretikon +4 min

Distribution · 90 days

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

  • Early 21% · 7
  • On time 76% · 26
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 86% T n=7
  • 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, 34 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
15:34on time on time
15:39 / 15:40≈ on time ≈ on time
15:45 / 15:49≈ on time ≈ on time
15:54 / 15:55≈ on time ≈ on time
15:58 / 15:59≈ on time ≈ on time
16:01 / 16:02≈ on time ≈ on time
16:08on time on time

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
Thu 19 NovEffretikon 16:08−1 min—
Wed 18 NovEffretikon 16:090 min—
Tue 17 NovEffretikon 16:090 min—
Mon 16 NovEffretikon 16:08−1 min—
Fri 13 NovEffretikon 16:090 min—
Thu 12 NovEffretikon 16:13+4 min+4 min
Wed 11 NovEffretikon 16:090 min—
Tue 10 NovEffretikon 16:09+1 min—
Mon 9 NovEffretikon 16:090 min—
Fri 6 NovEffretikon 16:08−1 min—
Thu 5 NovEffretikon 16:09−1 min—
Wed 4 NovEffretikon 16:080 min—
Tue 3 NovEffretikon 16:090 min—
Mon 2 NovEffretikon 16:08−1 min—
Fri 30 OctEffretikon 16:08−1 min—
Thu 29 OctEffretikon 16:08−1 min—
Wed 28 OctEffretikon 16:090 min—
Tue 27 OctEffretikon 16:08−1 min—
Mon 26 OctEffretikon 16:08−1 min—
Fri 23 OctEffretikon 16:080 min—
Thu 22 OctEffretikon 16:080 min—
Wed 21 OctEffretikon 16:090 min—
Tue 20 OctEffretikon 16:09−1 min+3 min
Mon 19 OctEffretikon 16:090 min—
Fri 16 OctEffretikon 16:100 min—
Thu 15 OctEffretikon 16:08−1 min—
Wed 14 OctEffretikon 16:07−1 min—
Tue 13 OctEffretikon 16:09−1 min—
Mon 12 OctEffretikon 16:090 min—
Fri 9 OctEffretikon 16:07−1 min—