Politics & activism — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (5 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 152 comparable posts for this entry, running 5 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @sovrep — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
24 measurements spanning 92 days, net +351. 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 8,940–9,397 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)
Subscribers
Change
6 Nov 2026, 00:39
9,344
+141
3 Nov 2026, 09:37
9,203
+18
31 Oct 2026, 00:16
9,185
-2
27 Oct 2026, 19:21
9,187
+9
24 Oct 2026, 23:36
9,178
-6
21 Oct 2026, 15:41
9,184
+6
18 Oct 2026, 22:30
9,178
-1
15 Oct 2026, 14:08
9,179
+35
12 Oct 2026, 14:21
9,144
+13
5 Oct 2026, 18:56
9,131
+14
27 Sept 2026, 21:42
9,117
+55
18 Sept 2026, 06:00
9,062
+19
10 Sept 2026, 07:38
9,043
+9
4 Sept 2026, 23:19
9,034
+12
1 Sept 2026, 00:47
9,022
-6
29 Aug 2026, 05:15
9,028
+8
26 Aug 2026, 01:32
9,020
-4
22 Aug 2026, 19:27
9,024
+7
19 Aug 2026, 13:14
9,017
+11
16 Aug 2026, 18:27
9,006
first reading
Engagement
232 posts held, back to 5 August 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 47 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
13.9%
avg views ÷ 9,344 subscribers
Avg views / post
1,300
95 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
95
of 232 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 10 November 2026
Posts held
232 (5 August 2026 – 10 November 2026)
Views total
123,219
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Nov 2026, 22:58 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈56,300
Videos
≈8,720
Links
≈7,020
Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
1h 05m
Average length
2m 10s
Measured directly from 30 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
Telegram’s own ‘edited’ marker: 30 of 95 posts held from the last 30 days (31.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
⚡️⚡️⚡️«САМОЕ ГЛАВНОЕ — ЭТО ЛЮДИ И СЛУЖЕНИЕ ОТЕЧЕСТВУ»: СКОРО НА ТЕЛЕКАНАЛЕ «БЕЛАРУСЬ 1» — БОЛЬШОЕ И ИСКРЕННЕЕ ИНТЕРВЬЮ НАТАЛЬИ КОЧАНОВОЙ
Совсем скоро в эфире телеканала «Беларусь 1» выйдет большой и доверительный разговор с Председателем Совета Республики Национального собрания Республики Беларусь Натальей Кочановой.
🟥О ключевых ориентирах государственного развития и повседневной работе с людьми на местах.
🟥О всес…
⚡️Члены Совета Республики проведут личные приемы граждан и прямые телефонные линии
🟥 11 ноября. Наталья Маркович проведет личный прием граждан и прямую телефонную линию в Ушачах
🟥 11 ноября. Екатерина Зенкевич проведет личный прием граждан в Буда-Кошелево
🟥 13 ноября. Глеб Лапицкий проведет личный прием граждан в Шумилино
🟥 17 ноября. Роман Бродов проведет личный прием граждан в Минске
🟥 18 ноября. Наталья Глинс…
Showing the 12 most recent of 232 posts we hold for @sovrep. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 21 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Министерство труда и социальной защиты Республики Беларусь @MintrudSocBelarus · 25,363 Telegram ranks this channel #1 of 97 here — alongside 96 others — read 14 September 2026
Официальный Минздрав - новости здравоохранения и фармацевтики Республики Беларусь @minzdravbelarus · 32,501 Telegram ranks this channel #1 of 97 here — alongside 96 others — read 5 September 2026
Гайдукевич Олег @gajdukevichh · 43,156 Telegram ranks this channel #2 of 92 here — alongside 91 others — read 15 September 2026
Министерство образования Беларуси @MinobrofBelarus · 33,452 Telegram ranks this channel #3 of 99 here — alongside 98 others — read 4 September 2026
МЧС Беларуси @mchs112by · 45,637 Telegram ranks this channel #3 of 95 here — alongside 94 others — read 27 August 2026
NEWS.BY @newsby_btrc · 24,058 Telegram ranks this channel #6 of 92 here — alongside 91 others — read 29 September 2026
МАРТ @mart_gov_by · 23,412 Telegram ranks this channel #6 of 92 here — alongside 91 others — read 18 September 2026
ONT NEWS @ontnews · 30,460 Telegram ranks this channel #6 of 92 here — alongside 91 others — read 7 September 2026
Главный. Тур @glav_tur · 18,816 Telegram ranks this channel #7 of 94 here — alongside 93 others — read 25 September 2026
Министерство обороны Республики Беларусь @modmilby · 37,281 Telegram ranks this channel #8 of 92 here — alongside 91 others — read 2 September 2026
Belorusneft_official @Belorusneft_official · 22,063 Telegram ranks this channel #9 of 92 here — alongside 91 others — read 21 September 2026
BELTA @belta_telegramm · 82,154 Telegram ranks this channel #9 of 91 here — alongside 90 others — read 18 August 2026
Невольфович @nevolf · 28,379 Telegram ranks this channel #11 of 91 here — alongside 90 others — read 16 September 2026
МВД Беларуси @pressmvd · 72,643 Telegram ranks this channel #14 of 97 here — alongside 96 others — read 20 August 2026
Пограничный комитет Беларуси @gpkgovby · 19,466 Telegram ranks this channel #16 of 93 here — alongside 92 others — read 3 October 2026
Внутренние войска МВД 🇧🇾 @vvmvdrb · 19,603 Telegram ranks this channel #23 of 91 here — alongside 90 others — read 2 October 2026
Могилёв - мой город! @moymogilev · 23,196 Telegram ranks this channel #26 of 89 here — alongside 88 others — read 19 September 2026
Беларусь 4 Витебск l НОВОСТИ ВИТЕБСКА 🎥 @b4_vitebsk · 5,394 Telegram ranks this channel #33 of 97 here — alongside 96 others — read 27 September 2026
Moladz.by @moladz_by_official · 20,987 Telegram ranks this channel #35 of 98 here — alongside 97 others — read 23 September 2026
BELAVIA - Belarusian Airlines @belavia_official · 58,528 Telegram ranks this channel #39 of 80 here — alongside 79 others — read 26 September 2026
Гомельщина официально @gomel_region_gov · 34,789 Telegram ranks this channel #39 of 97 here — alongside 96 others — read 5 September 2026
Пул Первого @pul_1 · 272,086 Telegram ranks this channel #39 of 89 here — alongside 88 others — read 10 August 2026
БелНовости @belnewsby1 · 50,753 Telegram ranks this channel #44 of 84 here — alongside 83 others — read 25 August 2026
Гомель. Официально @Gomel_official · 28,254 Telegram ranks this channel #46 of 93 here — alongside 92 others — read 9 September 2026
This channel appears in 43 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cross-platform identity — Wikidata
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
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 November 2026 — this
entry's latest reading, not the date you are reading this.
“Совет Республики Национального собрания Республики Беларусь” (@sovrep), 9,344 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/sovrep.
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.
