REG 15801 Białystok – Ełk

View line REG

Białystok 05:40 → Ełk 07:13 Mon, Tue, Wed, Thu, Fri 1 h 33 min · 20 stops PolRegio

✓ Today’s run finished

Today it reached Ełk at 07:13 0 min

  1. Białystok05:40
  2. Białystok Bacieczki05:50
  3. Borsukówka06:02
  4. Mońki06:22
  5. Podlasek06:43
  6. Prostki06:58
  7. Ełk07:13

Next service: tomorrow 05:40 from Białystok · Thu 12 Nov

Next departure 05:40 tomorrow · Białystok
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 7 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Ełk, 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 2 Nov Max en route +3 min · last fix heading to Ełk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
05:40on time on time
05:43 / 05:44≈ on time ≈ on time
05:46 / 05:47≈ on time ≈ on time
05:50≈ on time ≈ on time
05:54≈ on time ≈ on time
05:57≈ on time ≈ on time
06:02≈ on time ≈ on time
06:08≈ on time ≈ on time
06:12≈ on time ≈ on time
06:16 / 06:17≈ on time ≈ on time
06:22 / 06:23≈ on time ≈ on time
06:29≈ on time ≈ on time
06:33 / 06:34≈ on time ≈ on time
06:43≈ on time ≈ on time
06:46 / 06:47≈ on time ≈ on time
06:53 / 06:54≈ on time ≈ on time
06:58≈ on time ≈ on time
07:02≈ on time ≈ on time
07:07 / 07:08≈ on time ≈ on time
07:13on time on time

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 NovEłk 07:140 min—
Tue 10 NovEłk 07:140 min—
Mon 9 NovEłk 07:140 min—
Fri 6 NovEłk 07:14No data—
Thu 5 NovEłk 07:140 min—
Wed 4 NovEłk 07:140 min—
Tue 3 NovEłk 07:140 min—
Mon 2 NovEłk 07:17+3 min+3 min
Fri 30 OctEłk 07:140 min—
Thu 29 OctEłk 07:140 min—
Wed 28 OctEłk 07:140 min—
Tue 27 OctEłk 07:140 min—
Mon 26 OctEłk 07:140 min—
Fri 23 OctEłk 07:18No data—
Thu 22 OctEłk 07:18No data—
Wed 21 OctEłk 07:18No data—
Tue 20 OctEłk 07:18No data—
Mon 19 OctEłk 07:180 min—
Fri 16 OctEłk 07:180 min—
Thu 15 OctEłk 07:18No data—
Wed 14 OctEłk 07:18No data—
Tue 13 OctEłk 07:180 min—
Mon 12 OctEłk 07:190 min—
Fri 9 OctEłk 07:190 min—
Thu 8 OctEłk 07:180 min—
Wed 7 OctEłk 07:190 min—
Tue 6 OctEłk 07:190 min—
Mon 5 OctEłk 07:190 min—
Fri 2 OctEłk 07:16No data—
Thu 1 OctEłk 07:16No data—