S4 11240 Wieliszew → Piaseczno

View line S4

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

S4 11240/1 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 06:47 0 min

  1. Wieliszew05:34
  2. Warszawa Choszczówka05:49
  3. Warszawa Praga06:01
  4. Warszawa Koło06:12
  5. Warszawa Aleje Jerozolimskie06:25
  6. Warszawa Okęcie06:35
  7. Piaseczno06:47

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

Next departure 05: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%
11/12 runs under 3 min
RT coverage: 12 full · 0 partial · 4 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: +2 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

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

  • Early 0% · 0
  • On time 92% · 11
  • 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
  • 80% S n=5

Stops and timetable

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

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