REG 10355 Czyżew – Białystok

View line REG

Czyżew 07:16 → Białystok 08:17 Daily 1 h 01 min · 18 stops PolRegio

✓ Today’s run finished

Today it reached Białystok at 08:17 0 min

  1. Czyżew07:16
  2. Szepietowo07:28
  3. Racibory07:40
  4. Łapy07:52
  5. Bojary07:58
  6. Niewodnica08:07
  7. Białystok08:17

Next service: tomorrow 07:16 from Czyżew · Thu 12 Nov

Next departure 07:16 tomorrow · Czyżew
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
93%
40/43 runs under 3 min
RT coverage: 43 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 3 Nov Max en route +5 min · last fix heading to Białystok +5 min
  • Thu 24 Sept Max en route +4 min · last fix heading to Białystok +4 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Białystok +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 40
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 43 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:16on time +2 min
07:20 / 07:21≈ on time ≈ +2 min
07:23 / 07:24≈ on time ≈ +2 min
07:28 / 07:29≈ on time ≈ +2 min
07:33≈ on time ≈ +2 min
07:36≈ on time ≈ +2 min
07:40≈ on time ≈ +2 min
07:44 / 07:45≈ on time ≈ +2 min
07:48 / 07:49≈ on time ≈ +2 min
07:52≈ on time ≈ +2 min
07:54 / 07:55≈ on time ≈ +2 min
07:58≈ on time ≈ +2 min
08:01≈ on time ≈ +2 min
08:04 / 08:05≈ on time ≈ +2 min
08:07≈ on time ≈ +2 min
08:10 / 08:11≈ on time ≈ +2 min
08:13 / 08:14≈ on time ≈ +2 min
08:17on time +2 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
Wed 11 NovBiałystok 08:180 min—
Tue 10 NovBiałystok 08:180 min—
Mon 9 NovBiałystok 08:180 min—
Sun 8 NovBiałystok 08:180 min—
Sat 7 NovBiałystok 08:180 min—
Fri 6 NovBiałystok 08:180 min—
Thu 5 NovBiałystok 08:180 min—
Wed 4 NovBiałystok 08:180 min—
Tue 3 NovBiałystok 08:23+5 min+5 min
Mon 2 NovBiałystok 08:180 min—
Sun 1 NovBiałystok 08:22+4 min+4 min
Sat 31 OctBiałystok 08:180 min—
Fri 30 OctBiałystok 08:180 min—
Thu 29 OctBiałystok 08:180 min—
Wed 28 OctBiałystok 08:180 min—
Tue 27 OctBiałystok 08:180 min—
Mon 26 OctBiałystok 08:180 min—
Sun 25 OctBiałystok 08:18No data—
Sat 24 OctBiałystok 08:18No data—
Fri 23 OctBiałystok 08:18No data—
Thu 22 OctBiałystok 08:18No data—
Wed 21 OctBiałystok 08:18No data—
Tue 20 OctBiałystok 08:18No data—
Mon 19 OctBiałystok 08:180 min—
Sun 18 OctBiałystok 08:20+2 min+2 min
Sat 17 OctBiałystok 08:20+2 min+2 min
Fri 16 OctBiałystok 08:180 min—
Thu 15 OctBiałystok 08:180 min—
Wed 14 OctBiałystok 08:180 min—
Tue 13 OctBiałystok 08:180 min—