S4 99450 Piaseczno → Wieliszew
Alerts for train 99450
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S4.
S4 99450/1 Piaseczno–Wieliszew: final delay under 3 min on 8 of its 8 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 14:48 (GMT+1).
An alert on this phone or computer when the 99450 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today it reached Wieliszew at 13:21 0 min
- Piaseczno12:11
- Warszawa Okęcie12:22
- Warszawa Aleje Jerozolimskie12:32
- Warszawa Koło12:42
- Warszawa Praga12:54
- Warszawa Choszczówka13:06
- Wieliszew13:21
Next service: tomorrow 12:11 from Piaseczno · Sun 22 Nov
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
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 13
- 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
- 100% S n=6
- 100% 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 12:11 | on time | on time | |
| 12:14 | ≈ on time | ≈ on time | |
| 12:16 / 12:17 | ≈ on time | ≈ on time | |
| 12:19 | ≈ on time | ≈ on time | |
| 12:22 / 12:23 | ≈ on time | ≈ on time | |
| 12:25 | ≈ on time | ≈ on time | |
| 12:27 / 12:28 | ≈ on time | ≈ on time | |
| 12:29 / 12:30 | ≈ on time | ≈ on time | |
| 12:32 | ≈ on time | ≈ on time | |
| 12:36 / 12:37 | ≈ on time | ≈ on time | |
| 12:39 | ≈ on time | ≈ on time | |
| 12:41 | ≈ on time | ≈ on time | |
| 12:42 / 12:43 | ≈ on time | ≈ on time | |
| 12:45 | ≈ on time | ≈ on time | |
| 12:48 / 12:49 | ≈ on time | ≈ on time | |
| 12:51 | ≈ on time | ≈ on time | |
| 12:54 / 12:55 | ≈ on time | ≈ on time | |
| 12:57 | ≈ on time | ≈ on time | |
| 13:00 | ≈ on time | ≈ on time | |
| 13:03 | ≈ on time | ≈ on time | |
| 13:06 | ≈ on time | ≈ on time | |
| 13:11 / 13:14 | ≈ on time | ≈ on time | |
| 13:16 | ≈ on time | ≈ on time | |
| 13:18 / 13:19 | ≈ on time | ≈ on time | |
| 13:21 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Wieliszew 13:23 | 0 min | — |
| Sun 15 Nov | Wieliszew 13:23 | 0 min | — |
| Sat 14 Nov | Wieliszew 13:23 | 0 min | — |
| Wed 11 Nov | Wieliszew 13:23 | 0 min | — |
| Sun 8 Nov | Wieliszew 13:23 | 0 min | — |
| Sat 7 Nov | Wieliszew 13:23 | 0 min | — |
| Sun 1 Nov | Wieliszew 13:26 | +3 min | +3 min |
| Sat 31 Oct | Wieliszew 13:23 | 0 min | — |
| Sun 25 Oct | Wieliszew 13:23 | No data | — |
| Sat 24 Oct | Wieliszew 13:23 | No data | — |
| Sun 18 Oct | Wieliszew 13:23 | 0 min | — |
| Sat 17 Oct | Wieliszew 13:23 | 0 min | +1 min |
| Sun 11 Oct | Wieliszew 13:23 | 0 min | — |
| Sat 10 Oct | Wieliszew 13:23 | 0 min | — |
| Sun 4 Oct | Wieliszew 13:23 | 0 min | — |
| Sat 3 Oct | Wieliszew 13:21 | No data | — |