REG 10400 Białystok – Czeremcha

View line REG

Białystok 06:45 → Czeremcha 08:09 Daily 1 h 24 min · 20 stops PolRegio

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 06:45 from Białystok · Thu 19 Nov

Next departure 06:45 today · Białystok
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 13 no data
On-time · 90 days
82%
28/34 runs under 3 min
RT coverage: 34 full · 0 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+40min
9 in 10 runs arrive with less than this
30 days: +20 min

Last 30 days

Arrival delay at Czeremcha, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 26 Sept Max en route +53 min · last fix heading to Strabla +53 min
  • Mon 28 Sept Max en route +51 min · last fix heading to Strabla +51 min
  • Sun 27 Sept Max en route +51 min · last fix heading to Strabla +51 min
  • Wed 4 Nov Max en route +41 min · last fix heading to Czeremcha +41 min
  • Thu 5 Nov Max en route +39 min · last fix heading to Czeremcha +39 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 15% · 5

On-time by weekday

  • 78% M n=9
  • 100% T n=6
  • 75% W n=4
  • 67% T n=3
  • 100% F n=3
  • 75% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 34 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:45on time +11 min
06:48 / 06:49≈ on time ≈ +12 min
06:51 / 06:52≈ on time ≈ +13 min
06:54≈ on time ≈ +14 min
06:57 / 06:58≈ on time ≈ +15 min
07:02 / 07:05≈ on time ≈ +18 min
07:11≈ on time ≈ +22 min
07:14≈ on time ≈ +23 min
07:20≈ on time ≈ +26 min
07:26≈ on time ≈ +29 min
07:30≈ on time ≈ +31 min
07:35 / 07:36≈ on time ≈ +33 min
07:39 / 07:40≈ on time ≈ +35 min
07:44 / 07:45≈ on time ≈ +36 min
07:48 / 07:49≈ on time ≈ +37 min
07:51≈ on time ≈ +37 min
07:55≈ on time ≈ +38 min
08:00 / 08:01≈ on time ≈ +38 min
08:04≈ on time ≈ +39 min
08:09on time +40 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 18 NovCzeremcha 08:100 min—
Tue 17 NovCzeremcha 08:090 min—
Mon 16 NovCzeremcha 08:090 min—
Sun 15 NovCzeremcha 08:090 min—
Sat 14 NovCzeremcha 08:090 min—
Fri 13 NovCzeremcha 08:090 min—
Thu 12 NovCzeremcha 08:09No data—
Wed 11 NovCzeremcha 08:09No data—
Tue 10 NovCzeremcha 08:09No data—
Mon 9 NovCzeremcha 08:090 min—
Sun 8 NovCzeremcha 08:090 min—
Sat 7 NovCzeremcha 08:090 min—
Fri 6 NovCzeremcha 08:090 min—
Thu 5 NovCzeremcha 08:49+39 min+39 min
Wed 4 NovCzeremcha 08:49+41 min+41 min
Tue 3 NovCzeremcha 08:090 min—
Mon 2 NovCzeremcha 08:090 min—
Sun 1 NovCzeremcha 08:11No data—
Sat 31 OctCzeremcha 08:10No data—
Fri 30 OctCzeremcha 08:10No data—
Thu 29 OctCzeremcha 08:10No data—
Wed 28 OctCzeremcha 08:10No data—
Tue 27 OctCzeremcha 08:100 min—
Mon 26 OctCzeremcha 08:100 min—
Sun 25 OctCzeremcha 08:10No data—
Sat 24 OctCzeremcha 08:10No data—
Fri 23 OctCzeremcha 08:10No data—
Thu 22 OctCzeremcha 08:10No data—
Wed 21 OctCzeremcha 08:10No data—
Tue 20 OctCzeremcha 08:10No data—