R60 10743 Warszawa Wileńska – Tłuszcz

View line R60

Warszawa Wileńska 17:20 → Tłuszcz 18:00 Wed, Sat, Sun 0 h 40 min · 13 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Tłuszcz at 18:00 −3 min

  1. Warszawa Wileńska17:20
  2. Ząbki17:27
  3. Kobyłka-Ossów17:34
  4. Wołomin17:39
  5. Zagościniec17:45
  6. Klembów17:51
  7. Tłuszcz18:00

Next service: Saturday 17:20 from Warszawa Wileńska · Sat 21 Nov

Next departure 17:20 Saturday · Warszawa Wileńska
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 2 no data
On-time · 90 days
81%
13/16 runs under 3 min
RT coverage: 16 full · 0 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Tłuszcz, in minutes. One bar per run.

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

Worst days

  • Sat 19 Sept Max en route +5 min · last fix heading to Jasienica Mazowiecka +5 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Tłuszcz +3 min
  • Sun 20 Sept Max en route +3 min · last fix heading to Tłuszcz +3 min

Distribution · 90 days

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

  • Early 25% · 4
  • On time 56% · 9
  • 3–10 min 19% · 3
  • 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
  • 83% S n=6
  • 78% S n=9

Stops and timetable

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

Last 90 days, 16 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
17:20on time +3 min
17:24 / 17:25≈ on time ≈ +3 min
17:27 / 17:28≈ on time ≈ +3 min
17:31 / 17:32≈ on time ≈ +3 min
17:34 / 17:35≈ on time ≈ +3 min
17:37≈ on time ≈ +3 min
17:39 / 17:40≈ on time ≈ +3 min
17:42 / 17:43≈ on time ≈ +3 min
17:45 / 17:46≈ on time ≈ +3 min
17:48 / 17:49≈ on time ≈ +3 min
17:51 / 17:52≈ on time ≈ +3 min
17:55≈ on time ≈ +3 min
18:00on time +3 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 15 NovTłuszcz 17:58−3 min—
Sat 14 NovTłuszcz 17:590 min—
Wed 11 NovTłuszcz 17:590 min—
Sun 8 NovTłuszcz 17:59−2 min—
Sat 7 NovTłuszcz 17:590 min—
Sun 1 NovTłuszcz 18:04+3 min+3 min
Sat 31 OctTłuszcz 18:020 min—
Sun 25 OctTłuszcz 18:01No data—
Sat 24 OctTłuszcz 18:01No data—
Sun 18 OctTłuszcz 17:58−4 min—
Sat 17 OctTłuszcz 18:010 min—
Sun 11 OctTłuszcz 18:00−1 min—
Sat 10 OctTłuszcz 18:020 min—
Sun 4 OctTłuszcz 18:010 min—
Sat 3 OctTłuszcz 17:59No data—
Sun 27 SeptTłuszcz 18:00No data—
Sat 26 SeptTłuszcz 17:59No data—
Sun 20 SeptTłuszcz 17:59+3 min+3 min
Sat 19 SeptJasienica Mazowiecka 18:00+5 min+5 min
Sun 13 SeptTłuszcz 17:59−2 min—
Sat 12 SeptTłuszcz 17:59No data—
Sun 6 SeptTłuszcz 17:59−1 min—
Sat 5 SeptTłuszcz 17:59No data—
Sun 30 AugTłuszcz 17:59No data—