Telegram RegisterThe public register of Telegram
Telegram profile photo for Чат Беларусов в Польше

Supergroup

Чат Беларусов в Польше

@BelarusyPL

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

21,874members

-509 since we began measuring on 6 August 2026

4,647 online right now

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001327891757
TypeSupergroup
Username@BelarusyPL
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live30 October 2026
Measurements held52
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/BelarusyPL

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

21,87222,38322,127.56 August 2026 — 22,383 members7 August 2026 — 22,380 members8 August 2026 — 22,372 members10 August 2026 — 22,359 members10 August 2026 — 22,350 members12 August 2026 — 22,351 members13 August 2026 — 22,340 members14 August 2026 — 22,313 members15 August 2026 — 22,313 members16 August 2026 — 22,306 members17 August 2026 — 22,295 members18 August 2026 — 22,291 members19 August 2026 — 22,295 members21 August 2026 — 22,289 members23 August 2026 — 22,276 members25 August 2026 — 22,268 members26 August 2026 — 22,258 members26 August 2026 — 22,244 members27 August 2026 — 22,243 members28 August 2026 — 22,239 members29 August 2026 — 22,232 members30 August 2026 — 22,221 members31 August 2026 — 22,201 members1 September 2026 — 22,197 members2 September 2026 — 22,185 members4 September 2026 — 22,165 members6 September 2026 — 22,135 members9 September 2026 — 22,115 members12 September 2026 — 22,087 members13 September 2026 — 22,084 members15 September 2026 — 22,074 members17 September 2026 — 22,068 members26 September 2026 — 22,013 members4 October 2026 — 21,956 members9 October 2026 — 21,976 members13 October 2026 — 21,974 members14 October 2026 — 21,963 members15 October 2026 — 21,960 members16 October 2026 — 21,949 members18 October 2026 — 21,941 members18 October 2026 — 21,936 members19 October 2026 — 21,947 members20 October 2026 — 21,940 members22 October 2026 — 21,920 members23 October 2026 — 21,908 members24 October 2026 — 21,899 members25 October 2026 — 21,884 members26 October 2026 — 21,882 members27 October 2026 — 21,881 members28 October 2026 — 21,876 members29 October 2026 — 21,872 members30 October 2026 — 21,874 members21,8746 August 202630 October 2026
52 measurements spanning 85 days, net -509. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 21,795–22,460 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 52
Measured (UTC)MembersChange
30 Oct 2026, 08:1621,874+2
29 Oct 2026, 07:5621,872-4
28 Oct 2026, 02:2721,876-5
27 Oct 2026, 03:3421,881-1
26 Oct 2026, 03:3721,882-2
25 Oct 2026, 00:5421,884-15
24 Oct 2026, 02:4621,899-9
23 Oct 2026, 01:5621,908-12
22 Oct 2026, 01:0821,920-20
20 Oct 2026, 16:3421,940-7
19 Oct 2026, 19:5021,947+11
18 Oct 2026, 22:2821,936-5
18 Oct 2026, 00:3121,941-8
16 Oct 2026, 23:0621,949-11
15 Oct 2026, 21:4721,960-3
14 Oct 2026, 19:5821,963-11
13 Oct 2026, 08:5121,974-2
9 Oct 2026, 03:2121,976+20
4 Oct 2026, 14:1421,956-57
26 Sept 2026, 07:1922,013first reading

Engagement

No public post preview. We read this entry on 15 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 30 October 2026 — this entry's latest reading, not the date you are reading this.

“Чат Беларусов в Польше” (@BelarusyPL), 21,874 members as measured 30 October 2026. Telegram Register, tgregister.com/channel/BelarusyPL.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.