REG 10258 Sokółka – Białystok

View line REG

Sokółka 09:25 → Białystok 10:02 Wed, Sat, Sun 0 h 37 min · 9 stops PKP

It does not run today

Last recorded run: Sunday 1 November +7 min

Next service: tomorrow 09:25 from Sokółka · Sat 7 Nov

Next departure 09:25 tomorrow · Sokółka
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 3 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 14 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Białystok, 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 Białystok +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 4
  • 3–10 min 20% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 5 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
09:25on time +5 min
09:29 / 09:30≈ on time ≈ +5 min
09:34≈ on time ≈ +5 min
09:38≈ +1 min ≈ +5 min
09:42≈ +1 min ≈ +5 min
09:45 / 09:46≈ +1 min ≈ +5 min
09:49 / 09:50≈ +1 min ≈ +5 min
09:55≈ +2 min ≈ +5 min
10:02+2 min +5 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
Sun 1 NovBiałystok 10:10+7 min+7 min
Sat 31 OctBiałystok 10:030 min—
Sun 25 OctBiałystok 10:03No data—
Sat 24 OctBiałystok 10:03No data—
Sun 18 OctBiałystok 10:05+2 min+2 min
Sat 17 OctBiałystok 10:05+2 min+2 min
Sun 11 OctBiałystok 10:04+1 min+1 min
Sat 10 OctBiałystok 10:03No data—
Sun 4 OctBiałystok 10:03No data—
Sat 3 OctBiałystok 10:02No data—
Sun 27 SeptBiałystok 10:01No data—
Sat 26 SeptBiałystok 10:01No data—
Sun 20 SeptBiałystok 10:01No data—
Sat 19 SeptBiałystok 10:01No data—
Sun 13 SeptBiałystok 10:02No data—
Sat 12 SeptBiałystok 10:01No data—
Sun 6 SeptBiałystok 10:01No data—
Sat 5 SeptBiałystok 10:01No data—
Sun 30 AugBiałystok 10:01No data—