R21 19205 Siedlce – Czeremcha

View line R21

Siedlce 14:19 → Czeremcha 15:41 Mon, Tue, Wed, Thu, Fri 1 h 22 min · 17 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Czeremcha at 15:41 0 min

  1. Siedlce14:19
  2. Mordy14:35
  3. Cierpigórz14:42
  4. Platerów14:57
  5. Siemiatycze15:11
  6. Nurzec15:23
  7. Czeremcha15:41

Next service: tomorrow 14:19 from Siedlce · Fri 20 Nov

Next departure 14:19 tomorrow · Siedlce
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 11 full · 0 partial · 10 no data
On-time · 90 days
64%
18/28 runs under 3 min
RT coverage: 28 full · 0 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Czeremcha, in minutes. One bar per run.

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

Worst days

  • Tue 22 Sept Max en route +16 min · last fix heading to Nowy Nurzec +16 min
  • Mon 21 Sept Max en route +16 min · last fix heading to Nowy Nurzec +16 min
  • Fri 18 Sept Max en route +16 min · last fix heading to Nowy Nurzec +14 min
  • Fri 25 Sept Max en route +9 min · last fix heading to Borowiki +9 min
  • Fri 13 Nov Max en route +8 min · last fix heading to Czeremcha +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 64% · 18
  • 3–10 min 25% · 7
  • 10–30 min 11% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 40% T n=5
  • 100% W n=4
  • 100% T n=5
  • 43% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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:19on time +8 min
14:27≈ on time ≈ +8 min
14:30 / 14:31≈ on time ≈ +8 min
14:35≈ on time ≈ +9 min
14:37≈ on time ≈ +9 min
14:42≈ +1 min ≈ +9 min
14:48 / 14:49≈ +1 min ≈ +9 min
14:52≈ +1 min ≈ +9 min
14:57 / 14:58≈ +1 min ≈ +10 min
15:02 / 15:03≈ +1 min ≈ +10 min
15:07≈ +1 min ≈ +10 min
15:11≈ +1 min ≈ +10 min
15:16 / 15:17≈ +1 min ≈ +10 min
15:23 / 15:24≈ +1 min ≈ +10 min
15:29≈ +1 min ≈ +10 min
15:32 / 15:33≈ +1 min ≈ +10 min
15:41+1 min +11 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
Thu 19 NovCzeremcha 15:420 min—
Wed 18 NovCzeremcha 15:42No data—
Tue 17 NovCzeremcha 15:42No data—
Mon 16 NovCzeremcha 15:430 min—
Fri 13 NovCzeremcha 15:49+8 min+8 min
Thu 12 NovCzeremcha 15:42No data—
Tue 10 NovCzeremcha 15:43No data—
Mon 9 NovCzeremcha 15:420 min—
Fri 6 NovCzeremcha 15:43No data—
Thu 5 NovCzeremcha 15:420 min—
Wed 4 NovCzeremcha 15:420 min—
Tue 3 NovCzeremcha 15:43No data—
Mon 2 NovCzeremcha 15:420 min—
Fri 30 OctCzeremcha 15:42No data—
Thu 29 OctCzeremcha 15:420 min—
Wed 28 OctCzeremcha 15:420 min—
Tue 27 OctCzeremcha 15:420 min—
Mon 26 OctCzeremcha 15:430 min—
Fri 23 OctCzeremcha 15:42No data—
Thu 22 OctCzeremcha 15:42No data—
Wed 21 OctCzeremcha 15:43No data—
Tue 20 OctCzeremcha 15:42No data—
Mon 19 OctCzeremcha 15:43No data—
Fri 16 OctCzeremcha 15:49+7 min+13 min
Thu 15 OctCzeremcha 15:420 min—
Wed 14 OctCzeremcha 15:420 min—
Tue 13 OctCzeremcha 15:46+3 min+3 min
Mon 12 OctCzeremcha 15:46+4 min+4 min
Fri 9 OctCzeremcha 15:43+1 min+1 min
Thu 8 OctCzeremcha 15:420 min—