REG 10363 Czyżew – Białystok

View line REG

Czyżew 16:11 → Białystok 17:13 Daily 1 h 02 min · 18 stops PolRegio

✓ Today’s run finished

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

  1. Czyżew16:11
  2. Szepietowo16:24
  3. Racibory16:35
  4. Łapy16:47
  5. Bojary16:53
  6. Niewodnica17:02
  7. Białystok17:13

Next service: tomorrow 16:11 from Czyżew · Fri 6 Nov

Next departure 16:11 tomorrow · Czyżew
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
81%
26/32 runs under 3 min
RT coverage: 32 full · 0 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: 0 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 27 Oct Max en route +14 min · last fix heading to Białystok +14 min
  • Wed 30 Sept Max en route +31 min · last fix heading to Trypucie +14 min
  • Thu 1 Oct Max en route +13 min · last fix heading to Trypucie +13 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Białystok +4 min
  • Sun 4 Oct Max en route +3 min · last fix heading to Białystok +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 26
  • 3–10 min 9% · 3
  • 10–30 min 9% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 80% W n=5
  • 80% T n=5
  • 100% F n=4
  • 80% S n=5
  • 60% S n=5

Stops and timetable

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

Last 90 days, 32 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
16:11on time +4 min
16:16≈ on time ≈ +4 min
16:19≈ on time ≈ +4 min
16:24≈ on time ≈ +4 min
16:28 / 16:29≈ on time ≈ +4 min
16:31 / 16:32≈ on time ≈ +4 min
16:35 / 16:36≈ on time ≈ +4 min
16:40≈ on time ≈ +4 min
16:44≈ on time ≈ +4 min
16:47 / 16:48≈ on time ≈ +4 min
16:50≈ on time ≈ +4 min
16:53 / 16:54≈ on time ≈ +4 min
16:56 / 16:57≈ on time ≈ +4 min
17:00≈ on time ≈ +4 min
17:02 / 17:03≈ on time ≈ +4 min
17:06≈ on time ≈ +4 min
17:09≈ on time ≈ +4 min
17:13on time +4 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 17:140 min—
Wed 4 NovBiałystok 17:140 min—
Tue 3 NovBiałystok 17:150 min—
Mon 2 NovBiałystok 17:140 min—
Sun 1 NovBiałystok 17:18+4 min+4 min
Sat 31 OctBiałystok 17:150 min—
Fri 30 OctBiałystok 17:140 min—
Thu 29 OctBiałystok 17:140 min—
Wed 28 OctBiałystok 17:140 min—
Tue 27 OctBiałystok 17:28+14 min+14 min
Mon 26 OctBiałystok 17:150 min—
Sun 25 OctBiałystok 17:14No data—
Sat 24 OctBiałystok 17:14No data—
Fri 23 OctBiałystok 17:15No data—
Thu 22 OctBiałystok 17:15No data—
Wed 21 OctBiałystok 17:15No data—
Tue 20 OctBiałystok 17:14No data—
Mon 19 OctBiałystok 17:14No data—
Sun 18 OctBiałystok 17:150 min—
Sat 17 OctBiałystok 17:150 min—
Fri 16 OctBiałystok 17:140 min—
Thu 15 OctBiałystok 17:140 min—
Wed 14 OctBiałystok 17:140 min—
Tue 13 OctBiałystok 17:140 min—
Mon 12 OctBiałystok 17:140 min—
Sun 11 OctBiałystok 17:140 min—
Sat 10 OctBiałystok 17:150 min—
Fri 9 OctBiałystok 17:140 min—
Thu 8 OctBiałystok 17:140 min—
Wed 7 OctBiałystok 17:140 min—