REG 51804 Ełk – Białystok

View line REG

Ełk 14:35 → Białystok 16:10 Daily 1 h 35 min · 20 stops PolRegio

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 14:35 from Ełk · Fri 6 Nov

Next departure 14:35 today · Ełk
On-time · 30 days
62%
8/13 runs under 3 min
RT coverage: 13 full · 0 partial · 16 no data
On-time · 90 days
70%
16/23 runs under 3 min
RT coverage: 23 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Wed 14 Oct Max en route +6 min · last fix heading to Białystok +6 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Białystok +5 min
  • Sat 17 Oct Max en route +5 min · last fix heading to Białystok +5 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Białystok +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Białystok +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 70% · 16
  • 3–10 min 30% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=4
  • 75% W n=4
  • 75% T n=4
  • 0% F n=2
  • 0% S n=1
  • 50% S n=2

Stops and timetable

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

Last 90 days, 23 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
14:35on time +5 min
14:38≈ on time ≈ +5 min
14:43 / 14:44≈ on time ≈ +5 min
14:47 / 14:48≈ on time ≈ +5 min
14:52 / 14:53≈ on time ≈ +5 min
14:59 / 15:00≈ on time ≈ +5 min
15:03 / 15:04≈ on time ≈ +5 min
15:13 / 15:14≈ on time ≈ +5 min
15:18≈ on time ≈ +5 min
15:25 / 15:30≈ on time ≈ +5 min
15:34 / 15:35≈ on time ≈ +5 min
15:39≈ on time ≈ +5 min
15:42 / 15:43≈ on time ≈ +5 min
15:48 / 15:49≈ on time ≈ +5 min
15:53 / 15:54≈ on time ≈ +5 min
15:56 / 15:57≈ on time ≈ +5 min
16:00 / 16:01≈ on time ≈ +5 min
16:04≈ on time ≈ +5 min
16:06 / 16:07≈ on time ≈ +5 min
16:10on time +5 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 16:090 min—
Wed 4 NovBiałystok 16:090 min—
Tue 3 NovBiałystok 16:100 min—
Mon 2 NovBiałystok 16:090 min—
Sun 1 NovBiałystok 16:11No data—
Sat 31 OctBiałystok 16:12No data—
Fri 30 OctBiałystok 16:11No data—
Thu 29 OctBiałystok 16:11No data—
Wed 28 OctBiałystok 16:11No data—
Tue 27 OctBiałystok 16:11No data—
Mon 26 OctBiałystok 16:120 min—
Sun 25 OctBiałystok 16:11No data—
Sat 24 OctBiałystok 16:11No data—
Fri 23 OctBiałystok 16:11No data—
Thu 22 OctBiałystok 16:12No data—
Wed 21 OctBiałystok 16:12No data—
Tue 20 OctBiałystok 16:11No data—
Mon 19 OctBiałystok 16:12No data—
Sun 18 OctBiałystok 16:16+5 min+5 min
Sat 17 OctBiałystok 16:17+5 min+5 min
Fri 16 OctBiałystok 16:16+5 min+5 min
Thu 15 OctBiałystok 16:110 min—
Wed 14 OctBiałystok 16:17+6 min+6 min
Tue 13 OctBiałystok 16:120 min—
Mon 12 OctBiałystok 16:110 min—
Sun 11 OctBiałystok 16:11No data—
Sat 10 OctBiałystok 16:12No data—
Fri 9 OctBiałystok 16:11No data—
Thu 8 OctBiałystok 16:16+5 min+5 min
Wed 7 OctBiałystok 16:110 min—