R21 11774 Czeremcha – Siedlce

View line R21

Czeremcha 08:43 → Siedlce 10:06 Daily 1 h 23 min · 17 stops Koleje Mazowieckie

✓ Today’s run finished

Today, last fix heading to Siedlce at 10:07 No data

  1. Czeremcha08:43
  2. Nurzec08:59
  3. Siemiatycze09:11
  4. Platerów09:24
  5. Cierpigórz09:41
  6. Mordy09:48
  7. Siedlce10:06

Next service: tomorrow 08:43 from Czeremcha · Wed 18 Nov

Next departure 08:43 tomorrow · Czeremcha
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 15 full · 0 partial · 15 no data
On-time · 90 days
82%
31/38 runs under 3 min
RT coverage: 38 full · 0 partial · 41 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +5 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 4 Oct Max en route +31 min · last fix heading to Siedlce +26 min
  • Sun 27 Sept Max en route +15 min · last fix heading to Krzymosze +15 min
  • Sun 11 Oct Max en route +9 min · last fix heading to Siedlce +9 min
  • Wed 4 Nov Max en route +8 min · last fix heading to Siedlce +8 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Siedlce +5 min

Distribution · 90 days

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

  • Early 11% · 4
  • On time 71% · 27
  • 3–10 min 13% · 5
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 100% T n=5
  • 86% W n=7
  • 100% T n=5
  • 100% F n=6
  • 67% S n=3
  • 40% S n=5

Stops and timetable

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

Last 90 days, 38 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
08:43on time on time
08:50≈ on time ≈ +1 min
08:54≈ on time ≈ +1 min
08:59 / 09:00≈ on time ≈ +1 min
09:06≈ on time ≈ +2 min
09:11≈ on time ≈ +2 min
09:15≈ on time ≈ +2 min
09:20≈ on time ≈ +3 min
09:24 / 09:25≈ on time ≈ +3 min
09:30 / 09:31≈ on time ≈ +3 min
09:34 / 09:35≈ on time ≈ +4 min
09:41≈ on time ≈ +4 min
09:45 / 09:46≈ on time ≈ +4 min
09:48≈ on time ≈ +5 min
09:52≈ on time ≈ +5 min
09:56≈ on time ≈ +5 min
10:06on time +6 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 17 NovSiedlce 10:07No data—
Mon 16 NovSiedlce 10:09+2 min+2 min
Sun 15 NovSiedlce 19:140 min—
Sat 14 NovSiedlce 19:140 min—
Fri 13 NovSiedlce 10:070 min—
Thu 12 NovSiedlce 10:08No data—
Wed 11 NovSiedlce 19:14No data—
Tue 10 NovSiedlce 10:08No data—
Mon 9 NovSiedlce 10:070 min—
Sun 8 NovSiedlce 19:14No data—
Sat 7 NovSiedlce 19:14No data—
Fri 6 NovSiedlce 10:07No data—
Thu 5 NovSiedlce 10:070 min—
Wed 4 NovSiedlce 10:14+8 min+8 min
Tue 3 NovSiedlce 10:07No data—
Mon 2 NovSiedlce 10:09+4 min+4 min
Sun 1 NovSiedlce 19:14No data—
Sat 31 OctSiedlce 19:140 min—
Fri 30 OctSiedlce 10:05−2 min—
Thu 29 OctSiedlce 10:070 min—
Wed 28 OctSiedlce 10:070 min—
Tue 27 OctSiedlce 10:070 min—
Mon 26 OctSiedlce 10:12+5 min+5 min
Sun 25 OctSiedlce 19:14No data—
Sat 24 OctSiedlce 19:14No data—
Fri 23 OctSiedlce 10:07No data—
Thu 22 OctSiedlce 10:07No data—
Wed 21 OctSiedlce 10:07No data—
Tue 20 OctSiedlce 10:07No data—
Mon 19 OctSiedlce 10:070 min—