Channel
@Slyudyanski_rayon
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
971subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001689294387 |
|---|---|
| Type | Channel |
| Username | @Slyudyanski_rayon |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/Slyudyanski_rayon |
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 95% 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 why it has no browse page of its own yet.
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.
Posts published here appear word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @n_udinsk/167435 Aug 2026, 08:15 UTC | @Slyudyanski_rayon/14577 · this entry5 Aug 2026, 09:04 UTC | 1.00 | 49 minutes |
| @Slyudyanski_rayon/14579 · this entry6 Aug 2026, 06:43 UTC | @n_udinsk/167456 Aug 2026, 08:35 UTC | 1.00 | 1.9 hours |
| @n_udinsk/167557 Aug 2026, 01:17 UTC | @Slyudyanski_rayon/14593 · this entry7 Aug 2026, 02:01 UTC | 1.00 | 44 minutes |
| @n_udinsk/167567 Aug 2026, 01:25 UTC | @Slyudyanski_rayon/14594 · this entry7 Aug 2026, 03:01 UTC | 1.00 | 1.6 hours |
| @Slyudyanski_rayon/14595 · this entry7 Aug 2026, 04:03 UTC | @n_udinsk/167577 Aug 2026, 04:24 UTC | 0.98 | 21 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @n_udinsk | 5 (5/5 hand-verifiable sample passed) | 1.00 | 49 minutes | @n_udinsk (3–2) |
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. 2 of the 3 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 11 comparable posts for this entry, running 5 August 2026 to 7 August 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.
Across the whole group of 2, the earliest publisher we hold is @n_udinsk. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 16:06 | 971 | -1 |
| 7 Aug 2026, 06:47 | 972 | first reading |
13 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 1 pageof Telegram’s post history, 20 posts per page.
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. It is computed over the 2 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 13 (5 August 2026 – 7 August 2026) |
| Views total | 865 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 06:47 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.
4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 3 | 75.0% | |
| ❤ | 1 | 25.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 2 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 5 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🏆 Победа школы №1 на федеральном уровне! 🇷🇺 Ученик Николай Владимиров и его наставник, советник директора по воспитанию Анна Викторовна Гуменн, а также юнаты школы стали абсолютными победителями Всероссийского этапа проекта «Юннатские экспедиции»! 🌿 О проекте: Масштабная инициатива от «Движения Первых» в рамках трека «Юннаты Первых». Главная цель — возродить традиции юных натуралистов, научить молодежь изучать прир…
👍3
Photo, posted without a caption
В Иркутской области в ближайшее время завершится этап регистрации кандидатов на выборы в Госдуму. На данный момент в списке – 38 претендентов. До 15 августа региональный избирком озвучит финальный список. Руководитель Общественного штаба по наблюдению за выборами в Иркутской области Владислав Шиндяев уже дал экспертную оценку этому этапу. Подробности – в видео. #АдминистрацияСлюдянскогомуниципальногорайона
🕯В Нижнеудинске создают место, которое станет символом памяти о подвигах бойцов СВО. Оно появится благодаря неравнодушным жителям города и района и участию в проекте «Есть Решение». История создания мемориала началась прошлой весной по инициативе действующего участника СВО Семена Семенова с позывным «Бродяга». Он обратился к землякам с просьбой почтить память своих товарищей и перечислил от себя первые 100 тысяч руб…
❤1
🤳🏻 Могут ли блогеры менять города и сёла? Однозначно да, ведь взгляд людей на место, где они живут, способен преобразить каждый уголок малой родины, и сегодня у нас есть шанс заявить о своих идеях на всю страну. 🏙 В Иркутской области продолжается регистрация заявок на конкурс «Блогеры благоустройства 2.0». К участию приглашают подростков от 12 лет и взрослых любого возраста – в конкурсе предусмотрено 4 возрастных …
🎉 День физкультурника в эту субботу! 🏃 Дорогие друзья! Приглашаем вас отметить День физкультурника вместе с нами! В эту субботу вас ждут увлекательные спортивные мероприятия, которые подарят заряд энергии и хорошее настроение! Не упустите возможность погрузиться в мир спорта и здоровья! Ознакомьтесь с нашей афишей, чтобы не пропустить самые интересные события и выбрать то, что вам по душе. 💪❤️ #АдминистрацияСлюдян…
Историко-патриотический конкурс «Связующая нить народов России» приглашает к участию С 15 июля 2026 года при поддержке Общественной палаты РФ, Министерства культуры РФ, а также с использованием Гранта Президента РФ, предоставленного Фондом президентских грантов, стартовал Всероссийский историко-патриотический конкурс «Связующая нить народов России». Он приурочен к Году единства народов России. Организатор конкурса …
Photo, posted without a caption
В Иркутской области заработал «СВОйНАВИГАТОР38» — цифровая платформа поддержки участников спецоперации и их семей. Онлайн-портал, объединяющий все актуальные меры помощи, был представлен Губернатором Игорем Кобзевым на заседании Правительства региона. Проект создан в соавторстве с участником программы «Герои Приангарья» Максимом Маньковым при активном участии самих ветеранов СВО. Что внутри портала? ⤵️ 🗂 109 мер по…
Хочешь управлять будущим целой страны? Минобороны России набирает операторов дронов в подразделения беспилотных войск. Условия: 📌один год контракта (с возможностью продления) 📌бесплатное обучение 📌служба только в войсках БПС под усиленной защитой 📌достойная зарплата и бонусы 📌крупные единовременные выплаты 📞 117 🌐 служба-по-контракту38.рф | бпла38.рф #АдминистрацияСлюдянскогомуниципальногорайона
🌿 Почему где-то траву уже скосили, а рядом она по пояс? И кто вообще отвечает за покос? В сезон активного роста травы такие вопросы возникают особенно часто. Но далеко не каждый участок находится в ведении одной службы. Рассказываем, от чего зависит покос, что делать, если работы задерживаются, и куда обращаться, если проблему не решают.
🎸 5 сентября пройдёт фестиваль-конкурс «Воинское братство на Байкале»! Приглашаем к участию 📢: ✍️ Авторов-исполнителей; 🎤 Вокалистов; 📖 Чтецов. 📍 Место: стадион школы №7, п. Култук. Участвуйте сами и зовите друзей! Душевные песни под гитару, поэзия и живое общение в кругу единомышленников у священных вод Байкала ⛰️ ❓ Подробная информация по телефону 📱 8-902-762-18-39. ✉️ Заявки принимаются на эл. почту 📩 dkpe…
Showing the 12 most recent of 13 posts we hold for @Slyudyanski_rayon. 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.
Citation-graph rank — 684,242 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Администрация Слюдянского района” (@Slyudyanski_rayon), 971 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Slyudyanski_rayon.
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.