R91 55849 Raciąż – Sierpc

View line R91

Raciąż 14:09 → Sierpc 14:37 Mon, Tue, Thu, Fri 0 h 28 min · 6 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Sierpc at 14:37 0 min

  1. Raciąż14:09
  2. Koziebrody14:15
  3. Zawidz Kościelny14:21
  4. Zawidz14:24
  5. Mieszaki14:30
  6. Sierpc14:37

Next service: Thursday 14:09 from Raciąż · Thu 12 Nov

Next departure 14:09 Thursday · Raciąż
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 5 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 21 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:09on time on time
14:15≈ on time ≈ on time
14:21≈ on time ≈ on time
14:24≈ on time ≈ on time
14:30≈ on time ≈ on time
14:37on time on time

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 NovSierpc 14:380 min—
Mon 9 NovSierpc 14:380 min—
Fri 6 NovSierpc 14:380 min—
Thu 5 NovSierpc 14:380 min—
Wed 4 NovSierpc 14:380 min—
Tue 3 NovSierpc 14:380 min—
Mon 2 NovSierpc 14:380 min—
Fri 30 OctSierpc 14:380 min—
Thu 29 OctSierpc 14:380 min—
Wed 28 OctSierpc 14:380 min—
Tue 27 OctSierpc 14:380 min—
Mon 26 OctSierpc 14:380 min—
Fri 23 OctSierpc 14:38No data—
Thu 22 OctSierpc 14:38No data—
Wed 21 OctSierpc 14:39No data—
Tue 20 OctSierpc 14:38No data—
Mon 19 OctSierpc 14:39No data—
Fri 16 OctSierpc 14:380 min—
Thu 15 OctSierpc 14:380 min—
Wed 14 OctSierpc 14:380 min—
Tue 13 OctSierpc 14:380 min—
Mon 12 OctSierpc 14:380 min—
Fri 9 OctSierpc 14:380 min—
Thu 8 OctSierpc 14:380 min—
Wed 7 OctSierpc 14:380 min—
Tue 6 OctSierpc 14:380 min—
Mon 5 OctSierpc 14:38No data—
Fri 2 OctSierpc 14:36No data—
Thu 1 OctSierpc 14:37No data—
Wed 30 SeptSierpc 14:36No data—