S4 99448 Piaseczno → Wieliszew

View line S4

Piaseczno 11:11 → Wieliszew 12:21 Sun 1 h 10 min · 25 stops SKM Warszawa

S4 99448/9 Piaseczno–Wieliszew: final delay under 3 min on 5 of its 5 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 12:40 (GMT+1).

✓ Today’s run finished

Today it reached Wieliszew at 12:21 0 min

  1. Piaseczno11:11
  2. Warszawa Okęcie11:22
  3. Warszawa Aleje Jerozolimskie11:32
  4. Warszawa Koło11:42
  5. Warszawa Praga11:54
  6. Warszawa Choszczówka12:06
  7. Wieliszew12:21

Next service: Sunday 11:11 from Piaseczno · Sun 29 Nov

Next departure 11:11 Sunday · Piaseczno
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 1 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 1 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 Wieliszew, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 8
  • 3–10 min 0% · 0
  • 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
  • — S n=0
  • 100% S n=7

Stops and timetable

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

Last 90 days, 8 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
11:11on time +1 min
11:14≈ on time ≈ +1 min
11:16 / 11:17≈ on time ≈ +1 min
11:19≈ on time ≈ +1 min
11:22 / 11:23≈ on time ≈ +1 min
11:25≈ on time ≈ +1 min
11:27 / 11:28≈ on time ≈ +1 min
11:29 / 11:30≈ on time ≈ +1 min
11:32≈ on time ≈ +1 min
11:36 / 11:37≈ on time ≈ +1 min
11:39≈ on time ≈ +1 min
11:41≈ on time ≈ +1 min
11:42 / 11:43≈ on time ≈ +1 min
11:45≈ on time ≈ +1 min
11:48 / 11:49≈ on time ≈ +1 min
11:51≈ on time ≈ +1 min
11:54 / 11:55≈ on time ≈ +1 min
11:57≈ on time ≈ +1 min
12:00≈ on time ≈ +1 min
12:03≈ on time ≈ +1 min
12:06≈ on time ≈ +1 min
12:11 / 12:14≈ on time ≈ +1 min
12:16≈ on time ≈ +1 min
12:18 / 12:19≈ on time ≈ +1 min
12:21on 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 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 NovWieliszew 12:220 min—
Sun 15 NovWieliszew 12:230 min—
Wed 11 NovWieliszew 12:220 min—
Sun 8 NovWieliszew 12:230 min—
Sun 1 NovWieliszew 12:25+2 min+2 min
Sun 25 OctWieliszew 12:22No data—
Sun 18 OctWieliszew 12:220 min—
Sun 11 OctWieliszew 12:220 min—
Sun 4 OctWieliszew 12:23+1 min+1 min