R91 95854 Sierpc – Nasielsk

View line R91

Sierpc 10:10 → Nasielsk 11:25 Daily 1 h 15 min · 14 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Nasielsk at 11:25 0 min

  1. Sierpc10:10
  2. Zawidz10:20
  3. Koziebrody10:29
  4. Baboszewo10:47
  5. Płońsk10:58
  6. Wkra11:11
  7. Nasielsk11:25

Next service: tomorrow 10:10 from Sierpc · Wed 18 Nov

Next departure 10:10 tomorrow · Sierpc
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 41 full · 0 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Nasielsk, 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 1 Nov Max en route +7 min · last fix heading to Nasielsk +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=6
  • 100% S n=5
  • 83% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 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
10:10on time +1 min
10:15≈ on time ≈ +1 min
10:20 / 10:21≈ on time ≈ +1 min
10:23≈ on time ≈ +1 min
10:29≈ on time ≈ +1 min
10:36≈ on time ≈ +1 min
10:42≈ on time ≈ +1 min
10:47 / 10:48≈ on time ≈ +1 min
10:51 / 10:52≈ on time ≈ +1 min
10:58≈ on time ≈ +1 min
11:05≈ on time ≈ +1 min
11:11≈ on time ≈ +1 min
11:17 / 11:18≈ on time ≈ +1 min
11:25on time +1 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 NovNasielsk 11:240 min—
Mon 16 NovNasielsk 11:240 min—
Sun 15 NovNasielsk 11:240 min—
Sat 14 NovNasielsk 11:240 min—
Fri 13 NovNasielsk 11:240 min—
Thu 12 NovNasielsk 11:240 min—
Wed 11 NovNasielsk 11:240 min—
Tue 10 NovNasielsk 11:240 min—
Mon 9 NovNasielsk 11:250 min—
Sun 8 NovNasielsk 11:250 min—
Sat 7 NovNasielsk 11:240 min—
Fri 6 NovNasielsk 11:240 min—
Thu 5 NovNasielsk 11:240 min—
Wed 4 NovNasielsk 11:240 min—
Tue 3 NovNasielsk 11:24−1 min—
Mon 2 NovNasielsk 11:240 min—
Sun 1 NovNasielsk 11:34+7 min+7 min
Sat 31 OctNasielsk 11:260 min—
Fri 30 OctNasielsk 11:260 min—
Thu 29 OctNasielsk 11:260 min—
Wed 28 OctNasielsk 11:27+1 min+1 min
Tue 27 OctNasielsk 11:260 min—
Mon 26 OctNasielsk 11:260 min—
Sun 25 OctNasielsk 11:26No data—
Sat 24 OctNasielsk 11:26No data—
Fri 23 OctNasielsk 11:26No data—
Thu 22 OctNasielsk 11:26No data—
Wed 21 OctNasielsk 11:26No data—
Tue 20 OctNasielsk 11:26No data—
Mon 19 OctNasielsk 11:260 min—