R2 11682 Łuków – Siedlce

View line R2

Łuków 16:35 → Siedlce 17:02 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 9 stops Koleje Mazowieckie

It has not run yet today

Last recorded run: Tuesday 10 November +1 min

Next service: today 16:35 from Łuków · Thu 12 Nov

Next departure 16:35 today · Łuków
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 5 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 18 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 Siedlce, in minutes. One bar per run.

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

Worst days

  • Fri 18 Sept Max en route +3 min · last fix heading to Siedlce +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
16:35on time +1 min
16:40≈ on time ≈ +1 min
16:43≈ on time ≈ +1 min
16:46≈ on time ≈ +1 min
16:49 / 16:50≈ on time ≈ +1 min
16:52≈ on time ≈ +1 min
16:55≈ on time ≈ +1 min
16:58≈ on time ≈ +1 min
17:02on 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
Tue 10 NovSiedlce 17:04+1 min+1 min
Mon 9 NovSiedlce 17:04+1 min+1 min
Fri 6 NovSiedlce 17:030 min—
Thu 5 NovSiedlce 17:030 min—
Wed 4 NovSiedlce 17:030 min—
Tue 3 NovSiedlce 17:05+1 min+1 min
Mon 2 NovSiedlce 17:04+1 min+1 min
Fri 30 OctSiedlce 17:030 min—
Thu 29 OctSiedlce 17:030 min—
Wed 28 OctSiedlce 17:030 min—
Tue 27 OctSiedlce 17:04+1 min+1 min
Mon 26 OctSiedlce 17:040 min—
Fri 23 OctSiedlce 17:04No data—
Thu 22 OctSiedlce 17:03No data—
Wed 21 OctSiedlce 17:04No data—
Tue 20 OctSiedlce 17:03No data—
Mon 19 OctSiedlce 17:03No data—
Fri 16 OctSiedlce 17:030 min—
Thu 15 OctSiedlce 17:02−1 min—
Wed 14 OctSiedlce 17:02−1 min—
Tue 13 OctSiedlce 17:03−1 min—
Mon 12 OctSiedlce 17:030 min—
Fri 9 OctSiedlce 17:030 min—
Thu 8 OctSiedlce 17:030 min—
Wed 7 OctSiedlce 17:030 min—
Tue 6 OctSiedlce 17:030 min—
Mon 5 OctSiedlce 17:030 min—
Fri 2 OctSiedlce 17:02No data—
Thu 1 OctSiedlce 17:01No data—
Wed 30 SeptSiedlce 17:02+1 min+1 min