Channel
@anuchinomchs
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
131subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001887883502 |
|---|---|
| Type | Channel |
| Username | @anuchinomchs |
| Created | 5 December 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 12 November 2026 |
| On Telegram | t.me/anuchinomchs |
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 15 October 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
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 in near-verbatim form on 5 other registered channels. This entry also sits inside a group of 6 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 |
|---|---|---|---|
| @anuchinomchs/1262 · this entry18 May 2026, 04:18 UTC | @ondyakovlevsky/99818 May 2026, 05:50 UTC | 1.00 | 1.5 hours |
| @anuchinomchs/1264 · this entry20 May 2026, 04:00 UTC | @ondyakovlevsky/100020 May 2026, 04:21 UTC | 1.00 | 20 minutes |
| @anuchinomchs/1266 · this entry22 May 2026, 04:03 UTC | @ondyakovlevsky/100222 May 2026, 04:46 UTC | 1.00 | 43 minutes |
| @anuchinomchs/1270 · this entry29 May 2026, 03:59 UTC | @ondyakovlevsky/100529 May 2026, 06:48 UTC | 1.00 | 2.8 hours |
| @anuchinomchs/1274 · this entry4 Jun 2026, 02:04 UTC | @ondyakovlevsky/10074 Jun 2026, 03:30 UTC | 1.00 | 86 minutes |
| @anuchinomchs/1262 · this entry18 May 2026, 04:18 UTC | @mchsKirovsky/123717 Jun 2026, 02:01 UTC | 1.00 | 30 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ondyakovlevsky | 13 (8/8 hand-verifiable sample passed) | 1.00 | 1.7 hours | this entry (13–0) |
| @mchsKirovsky | 5 (5/5 hand-verifiable sample passed) | 1.00 | 5 days | this entry (5–0) |
| @ond_kavalerovo | 5 (5/5 hand-verifiable sample passed) | 1.00 | 24 hours | this entry (3–2) |
| @oktyabrskynadzor | 5 (5/5 hand-verifiable sample passed) | 1.00 | 4 days | this entry (5–0) |
| @ondkhorolsky | 5 (5/5 hand-verifiable sample passed) | 1.00 | 3 days | 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. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 15 May 2026 to 16 June 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.
Of the group of 6 channels, the one whose matching posts we hold earliest is @ondyakovlevsky. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, 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.
This channel is in a group of 6 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 23:56 | 131 | -1 |
| 9 Aug 2026, 00:46 | 132 | no change |
| 7 Aug 2026, 19:46 | 132 | first reading |
20 posts held, back to 15 May 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 20 posts for this entry, the most recent from 16 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 8 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.
Для предупреждения детской шалости с огнём рекомендуется: 🔸С малых лет разговаривать с ребёнком на противопожарные темы. Разъяснять возможные последствия и опасность игр с огнём и другими пожароопасными предметами. 🔹Не разрешать детям пользоваться спичками и свечами в отсутствие взрослых. Не оставлять маленьких детей одних рядом с открытыми работающими электроприборами, каминами или печами. 🔸Если есть газовая плита,…
Безопасное лето: пожарная безопасность в период каникул, детского отдыха и выпускных мероприятий С наступлением летних каникул у школьников появляется больше свободного времени, а вместе с этим возрастает ответственность взрослых за обеспечение их безопасности. В этот период особое внимание необходимо уделять соблюдению требований пожарной безопасности как в быту, так и во время проведения массовых мероприятий, отды…
ОНДиПР по Кавалеровскому муниципальному району напоминает правила пользования огнетушителем: -Держать огнетушитель следует вертикально. Ни в коем случае не переворачивать его. -Перед использованием необходимо сорвать пломбу и выдернуть защитную чеку. -Шланг или раструб огнетушителя направляется в сторону огня. ... -Нажатие на рычаг приводит огнетушитель в действие. Указанные правила пользования огнетушителем могут по…
День России: праздник должен быть безопасным 12 июня наша страна отмечает один из главных государственных праздников — День России. В этот день во многих населенных пунктах проходят торжественные мероприятия, концерты, народные гулянья, спортивные соревнования и акции с массовым пребыванием людей. Чтобы праздничные мероприятия прошли без происшествий, необходимо строго соблюдать требования пожарной безопасности. Во…
Пожары от электротехнических причин возникают в случае перегрузки сети мощными потребителями, при неверном монтаже или ветхости электросетей, при пользовании неисправными электроприборами и оставлении их без присмотра. Чтобы избежать такого рода пожаров, необходимо соблюдать несложные правила: - монтаж электропроводки должен выполнять только специалист; - замер сопротивления изоляции электропроводки необходимо про…
Пагубная привычка - причина каждого третьего пожара в Приморье С начала года в Приморье зарегистрировано более 7,5 тысяч пожаров, 2,5 тысячи из которых — по причине неосторожного обращения с огнем при курении. Последствия такой беспечности трагичны: в результате таких пожаров погибли 15 человек, ещё 4 получили травмы. МЧС России предупреждает: · не кури в постели, кресле или других местах, где можно заснуть — тлею…
🔥 Сжигание тополиного пуха — плохая идея Одна искра в тополином пухе — и огонь может перекинуться на дома, машины, лес. Не рискуй! 🔸 Не бросай непотушенные окурки, спички на улице. 🔸 Тщательно проводи подготовку к сварочным и огневым работам. 🔸 Пресекай игры детей, связанные с поджиганием пуха. 🔸 Установи на придомовой территории бочки с водой и средства первичного пожаротушения. 🔸 Эффективный способ избавления от …
На сегодняшний день автономный дымовой пожарный извещатель (сокращённо его называют АДПИ) является одним из наиболее эффективных средств по предупреждению гибели людей на пожарах. АДПИ выделяются среди средств активной защиты от огня, поскольку они могут реагировать на дым на ранней стадии возгорания и способны звуковым сигналом своевременно предупредить жителей об угрозе пожара. Громкость и частота звука извещателя …
Чтобы не допустить возникновения пожара следует выполнить следующие правила пожарной безопасности: ❗️тщательно проверять исправность электропроводки; ❗️постоянно следить за исправностью и целостностью розеток, вилок и электрошнуров; ❗️доверять монтаж и ремонт электропроводки только профессионалам; ❗️не оставляйте без присмотра бытовые электронагревательные приборы. Установите пожарный извещатель, он вовремя оповест…
Photo, posted without a caption
Чтобы не допустить возникновения пожара следует выполнить следующие правила пожарной безопасности: ❗️тщательно проверять исправность электропроводки; ❗️постоянно следить за исправностью и целостностью розеток, вилок и электрошнуров; ❗️доверять монтаж и ремонт электропроводки только профессионалам; ❗️не оставляйте без присмотра бытовые электронагревательные приборы. Установите пожарный извещатель, он вовремя оповест…
Друзья, давайте обойдёмся без экспериментов: не стоит подключать кучу приборов в одну розетку или удлинитель. Да, так удобнее, но это опасно - может случиться перегрузка, короткое замыкание и даже пожар. Лучше включите по очереди или используйте разные розетки. Простое правило - спасённый дом! Поделитесь этим видео с близкими - пусть все будут в безопасности!
Showing the 12 most recent of 20 posts we hold for @anuchinomchs. 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.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“ОНДиПР по Анучинскому МР” (@anuchinomchs), 131 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/anuchinomchs.
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.