Telegram RegisterThe public register of Telegram
Telegram profile photo for ПОЗИТИВНЫЙ БРАГИН

Channel

ПОЗИТИВНЫЙ БРАГИН

@bginka

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

248subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001468440572
TypeChannel
Username@bginka
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 15 September 2026
On Telegramt.me/bginka

Growth

2482502497 August 2026 — 250 subscribers8 August 2026 — 250 subscribers16 August 2026 — 249 subscribers6 September 2026 — 248 subscribers7 August 20266 September 2026
4 measurements spanning 30 days, net -2. 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 248–250 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 15:41248-1
16 Aug 2026, 05:43249-1
8 Aug 2026, 09:31250no change
7 Aug 2026, 20:24250first reading

Engagement

15 posts held, back to 30 March 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 May 2026, 04:23 UTC297 viewsread 8 August 2026
Forwarded from @BraginInfoPhoto

⚡️Брагинские экспонаты заинтересовали участников и гостей XX Гомельского экономического форума В экспозиции, посвящённой туристическому потенциалу Гомельской области, были представлены и брагинские экспонаты. Среди них – метеорит «Брагин», который вызвал интерес делегатов, участников форума, а также гостей города, коллекция реконструированных древних женских украшений Брагинского строя «кружка» и «плетёнка», а такж…

Showing the 12 most recent of 15 posts we hold for @bginka. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Брагін.info
@BraginInfo · 1,6291 post

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“ПОЗИТИВНЫЙ БРАГИН” (@bginka), 248 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/bginka.

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.