Channel
@n_udinsk
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
1,915subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001618788881 |
|---|---|
| Type | Channel |
| Username | @n_udinsk |
| Created | 14 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/n_udinsk |
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 82% 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/16743 · this entry5 Aug 2026, 08:15 UTC | @Slyudyanski_rayon/145775 Aug 2026, 09:04 UTC | 1.00 | 49 minutes |
| @Slyudyanski_rayon/145796 Aug 2026, 06:43 UTC | @n_udinsk/16745 · this entry6 Aug 2026, 08:35 UTC | 1.00 | 1.9 hours |
| @n_udinsk/16755 · this entry7 Aug 2026, 01:17 UTC | @Slyudyanski_rayon/145937 Aug 2026, 02:01 UTC | 1.00 | 44 minutes |
| @n_udinsk/16756 · this entry7 Aug 2026, 01:25 UTC | @Slyudyanski_rayon/145947 Aug 2026, 03:01 UTC | 1.00 | 1.6 hours |
| @Slyudyanski_rayon/145957 Aug 2026, 04:03 UTC | @n_udinsk/16757 · this entry7 Aug 2026, 04:24 UTC | 0.98 | 21 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Slyudyanski_rayon | 5 (5/5 hand-verifiable sample passed) | 1.00 | 49 minutes | this entry (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 2 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 9 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 — which is this entry. 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 |
|---|---|---|
| 11 Aug 2026, 13:53 | 1,915 | -1 |
| 7 Aug 2026, 20:46 | 1,916 | no change |
| 7 Aug 2026, 19:55 | 1,916 | first reading |
9 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 9 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 | 9 (5 August 2026 – 7 August 2026) |
| Views total | 596 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 20:46 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.
Measured directly from 2 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.
3 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 33.3% | |
| 🕊 | 1 | 33.3% | |
| 🤡 | 1 | 33.3% |
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 9 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 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.
Какие изменения ждут нас по пути на Ольхон? ⛴️ Каждый, кто хоть раз ездил на Ольхон, знает: дорога туда — отдельный квест. Однако изменения требуют времени и долгих согласований, ведь речь о территории, относящейся к центральной экологической зоне Байкала. Но со временем маршрут перестанет быть испытанием. План уже намечен. Что же поменяется? Рассказали в карточках ☝🏼
В Иркутской области в ближайшее время завершится этап регистрации кандидатов на выборы в Госдуму. На данный момент в списке – 38 претендентов. До 15 августа региональный избирком озвучит финальный список. Руководитель Общественного штаба по наблюдению за выборами в Иркутской области Владислав Шиндяев уже дал экспертную оценку этому этапу. Подробности – в видео.
🕯В Нижнеудинске создают место, которое станет символом памяти о подвигах бойцов СВО. Оно появится благодаря неравнодушным жителям города и района и участию в проекте «Есть Решение». История создания мемориала началась прошлой весной по инициативе действующего участника СВО Семена Семенова с позывным «Бродяга». Он обратился к землякам с просьбой почтить память своих товарищей и перечислил от себя первые 100 тысяч руб…
👍1🕊1
🤳🏻 Могут ли блогеры менять города и сёла? Однозначно да, ведь взгляд людей на место, где они живут, способен преобразить каждый уголок малой родины, и сегодня у нас есть шанс заявить о своих идеях на всю страну. 🏙 В Иркутской области продолжается регистрация заявок на конкурс «Блогеры благоустройства 2.0». К участию приглашают подростков от 12 лет и взрослых любого возраста – в конкурсе предусмотрено 4 возрастных …
⚡️Быть в курсе… … требует современная жизнь. Соответствуем! Все последние события и только факты — в нашем канале в мессенджере «МАКС». 👉Посмотреть: https://max.ru/id3813002056_gos
🤡1
В Иркутской области обсудили подготовку к уборочной кампании. Совещание прошло в правительстве региона. Как отметил губернатор Игорь Кобзев, в условиях санкционного давления продовольственная безопасность – задача государственного значения, и Приангарье вносит свой вклад в ее решение. Особое внимание уделили топливному обеспечению сельхозпредприятий. Специально созданный штаб продолжает мониторить ситуацию. – У се…
🌿 Почему где-то траву уже скосили, а рядом она по пояс? И кто вообще отвечает за покос? В сезон активного роста травы такие вопросы возникают особенно часто. Но далеко не каждый участок находится в ведении одной службы. Рассказываем, от чего зависит покос, что делать, если работы задерживаются, и куда обращаться, если проблему не решают.
Хочешь управлять будущим целой страны? Минобороны России набирает операторов дронов в подразделения беспилотных войск. Условия: 📌один год контракта (с возможностью продления) 📌бесплатное обучение 📌служба только в войсках БПС под усиленной защитой 📌достойная зарплата и бонусы 📌крупные единовременные выплаты 📞 117 🌐 служба-по-контракту38.рф | бпла38.рф
«Играющие с огнем». Кирилл из Красноярска, Виктория из Читы, Алексей из Оренбурга, Эдуард из Краснодара – кто они? Скорей всего, они мечтали о ярком, счастливом будущем, хотели счастья, планировали жить. Вместо этого – задержание, уголовное дело, суд. Просто они решили, что можно получить только легкие деньги за поджог релейного шкафа, попытку диверсии на железной дороге или военном объекте, теракт на АЗС. Им обещал…
Showing the 9 most recent of 9 posts we hold for @n_udinsk. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Администрация Нижнеудинского муниципального образования” (@n_udinsk), 1,915 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/n_udinsk.
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.