R21 11772 Czeremcha – Siedlce

View line R21

Czeremcha 14:14 → Siedlce 15:37 Daily 1 h 23 min · 17 stops Koleje Mazowieckie

✓ Today’s run finished

Today, last fix heading to Siedlce at 15:39 No data

  1. Czeremcha14:14
  2. Nurzec14:30
  3. Siemiatycze14:42
  4. Platerów14:55
  5. Cierpigórz15:12
  6. Mordy15:19
  7. Siedlce15:37

Next service: tomorrow 14:14 from Czeremcha · Wed 11 Nov

Next departure 14:14 tomorrow · Czeremcha
On-time · 30 days
81%
13/16 runs under 3 min
RT coverage: 16 full · 0 partial · 14 no data
On-time · 90 days
73%
30/41 runs under 3 min
RT coverage: 41 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Sun 11 Oct Max en route +22 min · last fix heading to Siedlce +22 min
  • Thu 8 Oct Max en route +14 min · last fix heading to Siedlce +14 min
  • Fri 11 Sept Max en route +9 min · last fix heading to Stok Lacki +9 min
  • Fri 16 Oct Max en route +8 min · last fix heading to Siedlce +8 min
  • Thu 15 Oct Max en route +7 min · last fix heading to Siedlce +7 min

Distribution · 90 days

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

  • Early 24% · 10
  • On time 49% · 20
  • 3–10 min 22% · 9
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (17 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 10
14:14on time +5 min
14:21≈ on time ≈ +5 min
14:25≈ on time ≈ +6 min
14:30 / 14:31≈ on time ≈ +6 min
14:37≈ on time ≈ +6 min
14:42≈ on time ≈ +6 min
14:46≈ on time ≈ +7 min
14:51≈ on time ≈ +7 min
14:55 / 14:56≈ on time ≈ +7 min
15:01 / 15:02≈ on time ≈ +7 min
15:05 / 15:06≈ on time ≈ +7 min
15:12≈ on time ≈ +7 min
15:16 / 15:17≈ on time ≈ +7 min
15:19≈ on time ≈ +7 min
15:23≈ on time ≈ +7 min
15:27≈ on time ≈ +7 min
15:37on time +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
Tue 10 NovSiedlce 15:39No data—
Mon 9 NovSiedlce 15:380 min—
Sun 8 NovSiedlce 15:38No data—
Sat 7 NovSiedlce 15:38No data—
Fri 6 NovSiedlce 15:38No data—
Thu 5 NovSiedlce 15:380 min—
Wed 4 NovSiedlce 15:380 min—
Tue 3 NovSiedlce 15:39No data—
Mon 2 NovSiedlce 15:42+4 min+4 min
Sun 1 NovSiedlce 15:38No data—
Sat 31 OctSiedlce 15:37−2 min—
Fri 30 OctSiedlce 15:36−2 min—
Thu 29 OctSiedlce 15:380 min—
Wed 28 OctSiedlce 15:37−1 min—
Tue 27 OctSiedlce 15:380 min—
Mon 26 OctSiedlce 15:390 min—
Sun 25 OctSiedlce 15:38No data—
Sat 24 OctSiedlce 15:38No data—
Fri 23 OctSiedlce 15:38No data—
Thu 22 OctSiedlce 15:38No data—
Wed 21 OctSiedlce 15:39No data—
Tue 20 OctSiedlce 15:38No data—
Mon 19 OctSiedlce 15:39No data—
Sun 18 OctSiedlce 15:380 min—
Sat 17 OctSiedlce 15:39No data—
Fri 16 OctSiedlce 15:46+8 min+8 min
Thu 15 OctSiedlce 15:45+7 min+7 min
Wed 14 OctSiedlce 15:37−1 min—
Tue 13 OctSiedlce 15:390 min—
Mon 12 OctSiedlce 15:380 min—