R62 11785 Ostrołęka – Chorzele

View line R62

Ostrołęka 13:26 → Chorzele 14:17 Daily 0 h 51 min · 9 stops Koleje Mazowieckie

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 13:26 from Ostrołęka · Tue 17 Nov

Next departure 13:26 today · Ostrołęka
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 10 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 48 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 Chorzele, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
13:26on time on time
13:32≈ on time ≈ on time
13:39≈ on time ≈ on time
13:44≈ on time ≈ on time
13:51 / 13:52≈ on time ≈ on time
13:59≈ on time ≈ on time
14:06≈ on time ≈ on time
14:11≈ on time ≈ on time
14:17on 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
Mon 16 NovChorzele 14:190 min—
Sun 15 NovChorzele 14:190 min—
Sat 14 NovChorzele 14:190 min—
Fri 13 NovChorzele 14:180 min—
Thu 12 NovChorzele 14:180 min—
Wed 11 NovChorzele 14:180 min—
Tue 10 NovChorzele 14:180 min—
Mon 9 NovChorzele 14:190 min—
Sun 8 NovChorzele 14:180 min—
Sat 7 NovChorzele 14:190 min—
Fri 6 NovChorzele 14:180 min—
Thu 5 NovChorzele 14:180 min—
Wed 4 NovChorzele 14:180 min—
Tue 3 NovChorzele 14:18No data—
Mon 2 NovChorzele 14:180 min—
Sun 1 NovChorzele 14:18No data—
Sat 31 OctChorzele 14:190 min—
Fri 30 OctChorzele 14:18No data—
Thu 29 OctChorzele 14:180 min—
Wed 28 OctChorzele 14:180 min—
Tue 27 OctChorzele 14:180 min—
Mon 26 OctChorzele 14:180 min—
Sun 25 OctChorzele 14:18No data—
Sat 24 OctChorzele 14:18No data—
Fri 23 OctChorzele 14:18No data—
Thu 22 OctChorzele 14:18No data—
Wed 21 OctChorzele 14:18No data—
Tue 20 OctChorzele 14:18No data—
Mon 19 OctChorzele 14:18No data—
Sun 18 OctChorzele 14:180 min—