S74 44652 Orzesze Jaśkowice – Tychy

View line S74

Orzesze Jaśkowice 06:05 → Tychy 06:22 Daily 0 h 17 min · 5 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Tychy at 06:25 +3 min

  1. Orzesze Jaśkowice06:05
  2. Orzesze Miasto06:07
  3. Łaziska Średnie06:13
  4. Wyry06:17
  5. Tychy06:22

Next service: tomorrow 06:05 from Orzesze Jaśkowice · Mon 9 Nov

Next departure 06:05 tomorrow · Orzesze Jaśkowice
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
89%
33/37 runs under 3 min
RT coverage: 37 full · 0 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Tychy, in minutes. One bar per run.

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

Worst days

  • Wed 28 Oct Max en route +34 min · last fix heading to Tychy +34 min
  • Thu 17 Sept Max en route +11 min · last fix heading to Łaziska Średnie +11 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Tychy +5 min
  • Sun 8 Nov Max en route +3 min · last fix heading to Tychy +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 33
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 80% W n=5
  • 80% T n=5
  • 100% F n=5
  • 100% S n=5
  • 67% S n=6

Stops and timetable

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

Last 90 days, 37 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
06:05on time +1 min
06:07 / 06:08≈ on time ≈ +1 min
06:13≈ on time ≈ +1 min
06:17≈ on time ≈ +2 min
06:22on time +2 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 1 August 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
Sun 8 NovTychy 06:24+3 min+3 min
Sat 7 NovTychy 06:24+2 min+2 min
Fri 6 NovTychy 06:230 min—
Thu 5 NovTychy 06:230 min—
Wed 4 NovTychy 06:230 min—
Tue 3 NovTychy 06:24+1 min+1 min
Mon 2 NovTychy 06:24+2 min+2 min
Sun 1 NovTychy 06:29+5 min+5 min
Sat 31 OctTychy 06:230 min—
Fri 30 OctTychy 06:230 min—
Thu 29 OctTychy 06:23No data—
Wed 28 OctTychy 06:57+34 min+34 min
Tue 27 OctTychy 06:230 min—
Mon 26 OctTychy 06:230 min—
Sun 25 OctTychy 06:23No data—
Sat 24 OctTychy 06:22No data—
Fri 23 OctTychy 06:22No data—
Thu 22 OctTychy 06:22No data—
Wed 21 OctTychy 06:22No data—
Tue 20 OctTychy 06:22No data—
Mon 19 OctTychy 06:220 min—
Sun 18 OctTychy 06:24+1 min+1 min
Sat 17 OctTychy 06:23+1 min+1 min
Fri 16 OctTychy 06:220 min—
Thu 15 OctTychy 06:220 min—
Wed 14 OctTychy 06:220 min—
Tue 13 OctTychy 06:220 min—
Mon 12 OctTychy 06:230 min—
Sun 11 OctTychy 06:220 min—
Sat 10 OctTychy 06:220 min—