S19 19950 Effretikon – Dietikon

View line S19

Effretikon 13:21 → Dietikon 13:53 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 7 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Dietikon at 13:53 0 min

  1. Effretikon13:21
  2. Dietlikon13:25
  3. Wallisellen13:28
  4. Zürich Oerlikon13:33
  5. Zürich HB13:39
  6. Zürich Altstetten13:46
  7. Dietikon13:53

Next service: tomorrow 13:21 from Effretikon · Wed 18 Nov

Next departure 13:21 tomorrow · Effretikon
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 16 full · 0 partial · 6 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 24 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 Dietikon, 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 +4 min · last fix heading to Dietikon +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=7
  • 100% W n=6
  • 67% T n=3
  • 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, 24 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:21on time on time
13:25≈ on time ≈ on time
13:28 / 13:29≈ on time ≈ on time
13:33 / 13:34≈ on time ≈ +1 min
13:39 / 13:41≈ on time ≈ +1 min
13:46 / 13:47≈ on time ≈ +1 min
13:53on 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 NovDietikon 13:540 min—
Mon 16 NovDietikon 13:54No data—
Fri 13 NovDietikon 13:54+1 min+1 min
Thu 12 NovDietikon 13:54No data—
Wed 11 NovDietikon 13:540 min—
Tue 10 NovDietikon 13:540 min—
Mon 9 NovDietikon 13:54No data—
Fri 6 NovDietikon 13:53−1 min—
Thu 5 NovDietikon 13:54No data—
Wed 4 NovDietikon 13:540 min—
Tue 3 NovDietikon 13:540 min—
Mon 2 NovDietikon 13:54No data—
Fri 30 OctDietikon 13:53−1 min—
Thu 29 OctDietikon 13:540 min—
Wed 28 OctDietikon 13:55+1 min—
Tue 27 OctDietikon 13:54−1 min—
Mon 26 OctDietikon 13:54No data—
Fri 23 OctDietikon 13:540 min—
Thu 22 OctDietikon 13:550 min—
Wed 21 OctDietikon 13:55+1 min+1 min
Tue 20 OctDietikon 13:57+2 min+2 min
Mon 19 OctDietikon 13:54+1 min+1 min
Fri 16 OctDietikon 13:540 min—
Thu 15 OctDietikon 13:54No data—
Wed 14 OctDietikon 13:540 min—
Tue 13 OctDietikon 13:54−1 min—
Mon 12 OctDietikon 13:54No data—
Fri 9 OctDietikon 13:54+1 min—
Thu 8 OctDietikon 13:58+4 min+4 min
Wed 7 OctDietikon 13:55+1 min—