REG 10359 Czyżew – Białystok

View line REG

Czyżew 10:03 → Białystok 11:05 Mon, Tue, Wed, Thu, Fri, Sun 1 h 02 min · 18 stops PolRegio

✓ Today’s run finished

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

  1. Czyżew10:03
  2. Szepietowo10:16
  3. Racibory10:27
  4. Łapy10:39
  5. Bojary10:45
  6. Niewodnica10:54
  7. Białystok11:05

Next service: tomorrow 10:03 from Czyżew · Fri 6 Nov

Next departure 10:03 tomorrow · Czyżew
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 6 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 31 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

  • Thu 1 Oct Max en route +7 min · last fix heading to Białystok +7 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Białystok +4 min
  • Fri 25 Sept Max en route +4 min · last fix heading to Białystok Zielone Wzgórza +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 80% T n=5
  • 83% F n=6
  • — S n=0
  • 67% S n=3

Stops and timetable

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

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