S1 99220 Pruszków – Otwock

View line S1

Pruszków 09:29 → Otwock 10:41 Mon, Tue, Thu, Fri 1 h 12 min · 24 stops SKM Warszawa

Running now · updated 09:35

Between Warszawa Ursus Niedźwiadek and Warszawa Ursus 0 min

Estimated arrival at Otwock 10:41 · 16 km/h

  1. Pruszków09:29
  2. Warszawa Ursus Niedźwiadek09:34
  3. Warszawa Ursus09:36
  4. Warszawa Włochy09:39
  5. Warszawa Powiśle09:55
  6. Warszawa Olszynka Grochowska10:07
  7. Otwock10:41

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

On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 40 full · 1 partial · 28 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: 0 min

Last 30 days

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

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

Worst days

  • Mon 14 Sept Max en route +3 min · last fix heading to Otwock Świder +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=6
  • 100% S n=4
  • 100% S n=6

Stops and timetable

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

Last 90 days, 41 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
09:29on time +2 minPassed
09:32≈ on time ≈ +2 minPassed
09:34 / 09:35≈ on time ≈ +2 minPassed
09:36 / 09:37≈ on time ≈ +2 minNext
09:39 / 09:40≈ on time ≈ +2 min
09:44 / 09:45≈ on time ≈ +2 min
09:48 / 09:49≈ on time ≈ +2 min
09:51 / 09:53≈ on time ≈ +2 min
09:55≈ on time ≈ +2 min
09:57 / 09:58≈ on time ≈ +2 min
10:00 / 10:01≈ on time ≈ +2 min
10:04 / 10:05≈ on time ≈ +2 min
10:07 / 10:08≈ on time ≈ +2 min
10:10 / 10:11≈ on time ≈ +2 min
10:14≈ on time ≈ +2 min
10:16≈ on time ≈ +2 min
10:18 / 10:19≈ on time ≈ +2 min
10:22≈ on time ≈ +2 min
10:24 / 10:25≈ on time ≈ +2 min
10:28 / 10:31≈ on time ≈ +2 min
10:33≈ on time ≈ +2 min
10:35 / 10:36≈ on time ≈ +2 min
10:38≈ on time ≈ +2 min
10:41on 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
Fri 6 NovWarszawa Ursus Niedźwiadek 09:34Partial coverage0 min—
Thu 5 NovOtwock 10:420 min—
Wed 4 NovOtwock 10:44+2 min+2 min
Tue 3 NovOtwock 10:420 min—
Mon 2 NovOtwock 10:420 min—
Sun 1 NovOtwock 10:45+3 min+3 min
Sat 31 OctOtwock 10:420 min—
Fri 30 OctOtwock 10:420 min—
Thu 29 OctOtwock 10:420 min—
Wed 28 OctOtwock 10:420 min—
Tue 27 OctOtwock 10:420 min—
Mon 26 OctOtwock 10:420 min—
Sun 25 OctOtwock 10:42No data—
Sat 24 OctOtwock 10:42No data—
Fri 23 OctOtwock 10:42No data—
Thu 22 OctOtwock 10:42No data—
Wed 21 OctOtwock 10:42No data—
Tue 20 OctOtwock 10:42No data—
Mon 19 OctOtwock 10:420 min—
Sun 18 OctOtwock 10:420 min—
Sat 17 OctOtwock 10:42No data—
Fri 16 OctOtwock 10:420 min—
Thu 15 OctOtwock 10:420 min—
Wed 14 OctOtwock 10:430 min—
Tue 13 OctOtwock 10:420 min—
Mon 12 OctOtwock 10:420 min—
Sun 11 OctOtwock 10:420 min—
Sat 10 OctOtwock 10:420 min—
Fri 9 OctOtwock 10:430 min—
Thu 8 OctOtwock 10:420 min—