REG 10365 Czyżew – Białystok

View line REG

Czyżew 17:28 → Białystok 18:30 Mon, Tue, Wed, Thu, Fri 1 h 02 min · 18 stops PolRegio

✓ Today’s run finished

Today it reached Białystok at 18:30 0 min

  1. Czyżew17:28
  2. Szepietowo17:41
  3. Racibory17:52
  4. Łapy18:04
  5. Bojary18:10
  6. Niewodnica18:19
  7. Białystok18:30

Next service: Monday 17:28 from Czyżew · Mon 23 Nov

Next departure 17:28 Monday · Czyżew
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 2 no data
On-time · 90 days
87%
33/38 runs under 3 min
RT coverage: 38 full · 0 partial · 21 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: +1 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

  • Fri 25 Sept Max en route +9 min · last fix heading to Klepacze +9 min
  • Tue 8 Sept Max en route +10 min · last fix heading to Klepacze +9 min
  • Fri 18 Sept Max en route +4 min · last fix heading to Białystok Zielone Wzgórza +4 min
  • Fri 6 Nov Max en route +3 min · last fix heading to Białystok +3 min
  • Tue 1 Sept Max en route +3 min · last fix heading to Białystok +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 33
  • 3–10 min 13% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 78% T n=9
  • 100% W n=7
  • 100% T n=7
  • 63% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 38 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
17:28on time +3 min
17:33≈ on time ≈ +3 min
17:36≈ on time ≈ +3 min
17:41≈ on time ≈ +3 min
17:45 / 17:46≈ on time ≈ +3 min
17:48 / 17:49≈ on time ≈ +3 min
17:52 / 17:53≈ on time ≈ +3 min
17:57≈ on time ≈ +3 min
18:01≈ on time ≈ +3 min
18:04 / 18:05≈ on time ≈ +3 min
18:07≈ on time ≈ +3 min
18:10 / 18:11≈ on time ≈ +3 min
18:13 / 18:14≈ on time ≈ +3 min
18:17≈ on time ≈ +3 min
18:19 / 18:20≈ on time ≈ +3 min
18:23≈ on time ≈ +3 min
18:26≈ on time ≈ +3 min
18:30on 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 20 NovBiałystok 18:300 min—
Thu 19 NovBiałystok 18:290 min—
Wed 18 NovBiałystok 18:290 min—
Tue 17 NovBiałystok 18:290 min—
Mon 16 NovBiałystok 18:320 min—
Fri 13 NovBiałystok 18:300 min—
Thu 12 NovBiałystok 18:290 min—
Tue 10 NovBiałystok 18:290 min—
Mon 9 NovBiałystok 18:290 min—
Fri 6 NovBiałystok 18:34+3 min+3 min
Thu 5 NovBiałystok 18:290 min—
Wed 4 NovBiałystok 18:290 min—
Tue 3 NovBiałystok 18:33+1 min+1 min
Mon 2 NovBiałystok 18:32+1 min+1 min
Fri 30 OctBiałystok 18:33+2 min+2 min
Thu 29 OctBiałystok 18:310 min—
Wed 28 OctBiałystok 18:32+1 min+1 min
Tue 27 OctBiałystok 18:310 min—
Mon 26 OctBiałystok 18:320 min—
Fri 23 OctBiałystok 18:32No data—
Thu 22 OctBiałystok 18:32No data—
Wed 21 OctBiałystok 18:31No data—
Tue 20 OctBiałystok 18:31No data—
Mon 19 OctBiałystok 18:31No data—
Fri 16 OctBiałystok 18:320 min—
Thu 15 OctBiałystok 18:310 min—
Wed 14 OctBiałystok 18:32+1 min+1 min
Tue 13 OctBiałystok 18:310 min—
Mon 12 OctBiałystok 18:310 min—
Fri 9 OctBiałystok 18:310 min—