REG 10411 Czeremcha – Białystok

View line REG

Czeremcha 04:43 → Białystok 06:07 Daily 1 h 24 min · 20 stops PolRegio

Running now · updated 05:22

Between Orzechowicze and Rajsk No data

Estimated arrival at Białystok 06:07 · 39 km/h

  1. Czeremcha04:43
  2. Suchowolce04:56
  3. Podbiele05:07
  4. Orzechowicze05:21
  5. Rajsk05:25
  6. Hołówki Duże05:40
  7. Białystok06:07
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 16 full · 0 partial · 14 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 25 full · 0 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
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

  • Mon 28 Sept Max en route +87 min · last fix heading to Czeremcha +87 min
  • Sun 27 Sept Max en route +87 min · last fix heading to Czeremcha +87 min
  • Sat 26 Sept Max en route +15 min · last fix heading to Hryniewicze +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 8% · 2

On-time by weekday

  • 86% M n=7
  • 100% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 67% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 25 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 10Today
04:43on time +9 minPassed
04:47≈ on time ≈ +9 minPassed
04:50 / 04:51≈ on time ≈ +9 minPassed
04:56≈ on time ≈ +9 minPassed
05:00≈ on time ≈ +9 minPassed
05:03≈ on time ≈ +9 minPassed
05:07≈ on time ≈ +9 minPassed
05:12≈ on time ≈ +9 minPassed
05:16≈ on time ≈ +9 minPassed
05:21 / 05:22≈ on time ≈ +9 minPassed
05:25 / 05:26≈ on time ≈ +9 minNext
05:31 / 05:32≈ on time ≈ +9 min
05:37≈ on time ≈ +9 min
05:40≈ on time ≈ +9 min
05:46 / 05:50≈ on time ≈ +9 min
05:54 / 05:55≈ on time ≈ +9 min
05:58≈ on time ≈ +9 min
06:00 / 06:01≈ on time ≈ +9 min
06:03≈ on time ≈ +9 min
06:07on time +9 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
Tue 10 NovOrzechowicze 05:19Partial coverageNo data—
Mon 9 NovBiałystok 06:080 min—
Sun 8 NovBiałystok 06:080 min—
Sat 7 NovBiałystok 06:090 min—
Fri 6 NovBiałystok 06:080 min—
Thu 5 NovBiałystok 06:080 min—
Wed 4 NovBiałystok 06:080 min—
Tue 3 NovBiałystok 06:080 min—
Mon 2 NovBiałystok 06:080 min—
Sun 1 NovBiałystok 06:09No data—
Sat 31 OctBiałystok 06:08No data—
Fri 30 OctBiałystok 06:08No data—
Thu 29 OctBiałystok 06:08No data—
Wed 28 OctBiałystok 06:08No data—
Tue 27 OctBiałystok 06:080 min—
Mon 26 OctBiałystok 06:080 min—
Sun 25 OctBiałystok 06:08No data—
Sat 24 OctBiałystok 06:08No data—
Fri 23 OctBiałystok 06:08No data—
Thu 22 OctBiałystok 06:08No data—
Wed 21 OctBiałystok 06:08No data—
Tue 20 OctBiałystok 06:08No data—
Mon 19 OctBiałystok 06:080 min—
Sun 18 OctBiałystok 06:090 min—
Sat 17 OctBiałystok 06:08No data—
Fri 16 OctBiałystok 06:09No data—
Thu 15 OctBiałystok 06:080 min—
Wed 14 OctBiałystok 06:080 min—
Tue 13 OctBiałystok 06:080 min—
Mon 12 OctBiałystok 06:090 min—