R62 11783 Ostrołęka – Chorzele

View line R62

Ostrołęka 07:06 → Chorzele 07:57 Daily 0 h 51 min · 9 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Chorzele at 07:57 0 min

  1. Ostrołęka07:06
  2. Grabowo07:12
  3. Zabiele Wielkie07:24
  4. Jastrząbka07:31
  5. Parciaki07:39
  6. Raszujka07:51
  7. Chorzele07:57

Next service: tomorrow 07:06 from Ostrołęka · Sat 7 Nov

Next departure 07:06 tomorrow · Ostrołęka
On-time · 30 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 12 no data
On-time · 90 days
82%
18/22 runs under 3 min
RT coverage: 22 full · 0 partial · 45 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: +4 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

Worst days

  • Thu 15 Oct Max en route +8 min · last fix heading to Chorzele +8 min
  • Tue 13 Oct Max en route +7 min · last fix heading to Chorzele +7 min
  • Sun 18 Oct Max en route +3 min · last fix heading to Chorzele +3 min
  • Sat 17 Oct Max en route +3 min · last fix heading to Chorzele +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 18
  • 3–10 min 18% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 100% W n=3
  • 75% T n=4
  • 100% F n=3
  • 50% S n=2
  • 50% S n=2

Stops and timetable

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

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