R21 10771 Siedlce – Czeremcha

View line R21

Siedlce 06:19 → Czeremcha 07:41 Daily 1 h 22 min · 17 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Czeremcha at 07:41 0 min

  1. Siedlce06:19
  2. Mordy06:35
  3. Cierpigórz06:42
  4. Platerów06:57
  5. Siemiatycze07:11
  6. Nurzec07:23
  7. Czeremcha07:41

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

Next departure 06:19 tomorrow · Siedlce
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 15 full · 0 partial · 15 no data
On-time · 90 days
85%
33/39 runs under 3 min
RT coverage: 39 full · 0 partial · 42 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: +5 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

  • Mon 2 Nov Max en route +50 min · last fix heading to Czeremcha +50 min
  • Tue 29 Sept Max en route +29 min · last fix heading to Sycze +29 min
  • Mon 26 Oct Max en route +7 min · last fix heading to Czeremcha +7 min
  • Mon 12 Oct Max en route +4 min · last fix heading to Czeremcha +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Czeremcha +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 50% M n=8
  • 80% T n=5
  • 100% W n=5
  • 100% T n=6
  • 80% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

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