S4 11266 Wieliszew → Piaseczno

View line S4

Wieliszew 22:34 → Piaseczno 23:47 Sat, Sun 1 h 13 min · 25 stops SKM Warszawa

S4 11266/7 Wieliszew–Piaseczno: final delay under 3 min on 8 of its 9 runs with data in the last 30 days (89%). Median final delay: 0 min. Running now, on time. Expected at Piaseczno: 23:47. TrainsRadar data as of 22 Nov 2026, 23:10 (GMT+1).

Running now · updated 23:10

Position estimated from the timetable

Between Warszawa Gdańska and Warszawa Powązki 0 min

Estimated arrival at Piaseczno 23:47 · 37 km/h

  1. Wieliszew22:34
  2. Warszawa Choszczówka22:49
  3. Warszawa Praga23:01
  4. Warszawa Gdańska23:07
  5. Warszawa Powązki23:10
  6. Warszawa Koło23:12
  7. Piaseczno23:47

Today it is running no worse than usual: typical arrival delay is 0 min; 89% of the last 9 runs arrived on time.

On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 8 full · 1 partial · 2 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 14 full · 1 partial · 2 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: +1 min

Last 30 days

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

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

Worst days

  • Sun 1 Nov Max en route +4 min · last fix heading to Piaseczno +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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 10Today
22:34on time on timePassed
22:36 / 22:37≈ on time ≈ on timePassed
22:39≈ on time ≈ on timePassed
22:42 / 22:45≈ on time ≈ on timePassed
22:49 / 22:50≈ on time ≈ on timePassed
22:52 / 22:53≈ on time ≈ on timePassed
22:55 / 22:56≈ on time ≈ on timePassed
22:58 / 22:59≈ on time ≈ on timePassed
23:01≈ on time ≈ on timePassed
23:04 / 23:05≈ on time ≈ on timePassed
23:07 / 23:08≈ on time ≈ on timePassed
23:10≈ on time ≈ on timeNext
23:12 / 23:13≈ on time ≈ on time
23:14 / 23:15≈ on time ≈ on time
23:16 / 23:17≈ on time ≈ on time
23:19 / 23:21≈ on time ≈ on time
23:25≈ on time ≈ on time
23:28≈ on time ≈ on time
23:30≈ on time ≈ on time
23:32 / 23:33≈ on time ≈ on time
23:35≈ on time ≈ on time
23:38 / 23:39≈ on time ≈ on time
23:41≈ on time ≈ on time
23:43 / 23:44≈ on time ≈ on time
23:47on 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 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 22 NovWarszawa ZOO 23:04Partial coverage0 min—
Sat 21 NovPiaseczno 23:480 min—
Sun 15 NovPiaseczno 23:480 min—
Sat 14 NovPiaseczno 23:480 min—
Wed 11 NovPiaseczno 23:480 min—
Sun 8 NovPiaseczno 23:480 min—
Sat 7 NovPiaseczno 23:480 min—
Sun 1 NovPiaseczno 23:49+4 min+4 min
Sat 31 OctPiaseczno 23:490 min—
Sun 25 OctPiaseczno 23:48No data—
Sat 24 OctPiaseczno 23:48No data—
Sun 18 OctPiaseczno 23:490 min—
Sat 17 OctPiaseczno 23:480 min—
Sun 11 OctPiaseczno 23:480 min—
Sat 10 OctPiaseczno 23:480 min—
Sun 4 OctPiaseczno 23:490 min—
Sat 3 OctPiaseczno 23:480 min—