REG 10353 Czyżew – Białystok

View line REG

Czyżew 06:03 → Białystok 07:05 Daily 1 h 02 min · 18 stops PolRegio

✓ Today’s run finished

Today it reached Białystok at 07:05 0 min

  1. Czyżew06:03
  2. Szepietowo06:16
  3. Racibory06:27
  4. Łapy06:39
  5. Bojary06:45
  6. Niewodnica06:54
  7. Białystok07:05

Next service: tomorrow 06:03 from Czyżew · Thu 12 Nov

Next departure 06:03 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
92%
34/37 runs under 3 min
RT coverage: 37 full · 0 partial · 37 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: +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

  • Sun 1 Nov Max en route +4 min · last fix heading to Białystok +4 min
  • Tue 13 Oct Max en route +3 min · last fix heading to Białystok +3 min
  • Mon 12 Oct Max en route +3 min · last fix heading to Białystok +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 34
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=6
  • 80% S n=5

Stops and timetable

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

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