S1 99256 Pruszków – Otwock

View line S1

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 18:29 from Pruszków · Tue 10 Nov

Next departure 18:29 today · Pruszków
On-time · 30 days
77%
17/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
74%
35/47 runs under 3 min
RT coverage: 47 full · 0 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Wed 30 Sept Max en route +41 min · last fix heading to Otwock +41 min
  • Sat 19 Sept Max en route +26 min · last fix heading to Warszawa Międzylesie +26 min
  • Wed 9 Sept Max en route +10 min · last fix heading to Warszawa Falenica +10 min
  • Thu 10 Sept Max en route +9 min · last fix heading to Michalin +9 min
  • Wed 4 Nov Max en route +8 min · last fix heading to Otwock +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 35
  • 3–10 min 19% · 9
  • 10–30 min 4% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 83% M n=6
  • 57% T n=7
  • 57% W n=7
  • 86% T n=7
  • 100% F n=9
  • 60% S n=5
  • 67% S n=6

Stops and timetable

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

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