S4 11244 Wieliszew → Piaseczno

View line S4

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

S4 11244/5 Wieliszew–Piaseczno: final delay under 3 min on 7 of its 8 runs with data in the last 30 days (88%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 13:02 (GMT+1).

✓ Today’s run finished

Today it reached Piaseczno at 09:47 0 min

  1. Wieliszew08:34
  2. Warszawa Choszczówka08:49
  3. Warszawa Praga09:01
  4. Warszawa Koło09:12
  5. Warszawa Aleje Jerozolimskie09:25
  6. Warszawa Okęcie09:35
  7. Piaseczno09:47

Next service: tomorrow 08:34 from Wieliszew · Sun 22 Nov

Next departure 08:34 tomorrow · Wieliszew
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 8 full · 0 partial · 2 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 13 full · 0 partial · 3 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

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 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=6
  • 83% S n=6

Stops and timetable

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

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