Local community — 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 100% 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 3 other registered channels. This entry also sits inside a group of 4 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.
Matching posts — open both and compare (6 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. 24 of the 24 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 178 comparable posts for this entry, running 5 August 2026 to 16 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 4 channels, the one whose matching posts we hold earliest is @raion_mitino — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 17 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 4 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.
61 measurements spanning 101 days, net +1,773. 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 9,719–12,070 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)
Subscribers
Change
16 Nov 2026, 13:57
11,799
+691
13 Nov 2026, 01:09
11,108
+227
10 Nov 2026, 21:55
10,881
-14
9 Nov 2026, 11:00
10,895
+54
8 Nov 2026, 01:00
10,841
+47
7 Nov 2026, 00:19
10,794
+60
5 Nov 2026, 22:04
10,734
+50
4 Nov 2026, 21:20
10,684
-2
3 Nov 2026, 21:27
10,686
-2
2 Nov 2026, 17:35
10,688
-3
1 Nov 2026, 18:21
10,691
-4
31 Oct 2026, 21:28
10,695
-13
30 Oct 2026, 18:20
10,708
-10
29 Oct 2026, 18:41
10,718
-2
28 Oct 2026, 19:21
10,720
-25
27 Oct 2026, 22:06
10,745
-5
26 Oct 2026, 21:17
10,750
-3
24 Oct 2026, 22:15
10,753
-4
23 Oct 2026, 22:05
10,757
-3
23 Oct 2026, 01:00
10,760
first reading
Engagement
206 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 66 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
13.3%
avg views ÷ 11,799 subscribers
Avg views / post
1,570
81 posts measured
Reaction rate
0.391%
reactions ÷ views · ER floor
Posts in window
81
of 206 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. It is computed over the 75 of 81 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 17 November 2026
Posts held
206 (5 August 2026 – 17 November 2026)
Views total
127,248
Reactions total
477
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 10:49 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
≈9,100
Videos
≈2,840
Links
≈1,390
Lifetime counters from Telegram’s own channel header, read 17 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
46m 00s
Average length
38s
Measured directly from 73 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.
Reaction mix
823 reactions across 161 posts, in 29 distinct kinds. The most used accounts for 29.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
246
29.9%
❤
164
19.9%
👎
148
18.0%
😱
60
7.29%
🤬
47
5.71%
🔥
38
4.62%
😢
32
3.89%
😁
24
2.92%
🙏
10
1.22%
🤗
8
0.972%
😡
6
0.729%
🥴
6
0.729%
🤔
5
0.608%
🤡
4
0.486%
🤯
4
0.486%
👀
3
0.365%
😨
3
0.365%
🙈
3
0.365%
😍
2
0.243%
🎄
1
0.122%
9 further kinds
9
1.09%
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 166 of the 206 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 823 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 206 most recent posts we hold, published 5 August 2026 to 17 November 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.
Advertising
Ad load
0.485%
1 of 206 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
893
over 1 measured post
Median views · rest
1,120
over 204 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
CQH36pWzJqEWANRPw2FLgQvLvNQfey1mJEiuzJGZyQATUj
1
23 August 2026
23 August 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 206 most recent posts we hold, published 5 August 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 18 of 81 posts held from the last 30 days (22.2%) 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).
Последний день без осадков!
Завтра утром начнется снег ❄️
В Москве ожидается преобладание облачной погоды, преимущественно без осадков. Ветер подвернет на юго-восточный и усилится до 4-9 м/с. Максимальная температура воздуха 0…+3.
Показания барометров, предвещая скорое ухудшением погоды, будут падать и составят 741 мм рт. ст.
К утру среды начнется снегопад и формирование снежного покрова до 1-3 см, который, впроче…
🚇 КУДА ПРОПАЛА СТАНЦИЯ «ПОКРОВСКАЯ” на нашей линии метро?
Загадка московского метро
Наверняка многие замечали: есть Арбатско-Покровская линия метро, станция «Арбатская» тоже есть. А вот станции «Покровская» нет. Почему?
Оказывается, она действительно должна была появиться!
Ещё при проектировании метро в 1930-х годах между станциями «Площадь Революции» и «Курская» планировали построить две промежуточные станции:
🔹 …
🎄 Главную ёлку страны срубят совсем рядом с Митино! Вы только посмотрите на эти цифры 👇
Новогоднюю красавицу для Соборной площади Кремля выбрали в подмосковном Клину — по нашему любимому дачному направлению.
Эксперты объехали 3000 километров, но идеальное дерево нашли в Воронинском лесничестве:
— Высота: 27 метров (как девятиэтажный дом!)
— Возраст: 95 лет
— Обхват ствола: 72 сантиметра
Спилят её уже 7 декабря и с…
✨ У нас новогодние ёлочки переливаются огоньками около магазинов, а на Никитском бульваре уже засиял новогодний тоннель.
Не рано? 👍/👎
До Нового года 46 дней!
МИТИНО @raion_mitino
❗️🅰️“Последний герой»
Всех лебедей увезли на этой неделе на зимние квартиры, и только один лебедь не дал себя поймать и остался на пруду!
МИТИНО💙МОСКВА
@PRO_MITINO_TG
Солнце ☀️ в Митино!
Не упустите возможность совершить чудесную прогулку!
Москва: на периферии антициклона
Сегодня синоптическую ситуацию в столице сформирует гребень антициклона, вытягивающийся с юго-запада. На фоне растущего атмосферного давления в регионе ожидается переменная облачность 🌤️ , без осадков.
Температура воздуха +3…+5°, по области +1…+6°. Ветер юго-западный 3-8 м/с. Атмосферное давление будет расти и…
2️⃣Изменится движение поездов на D2
С 16 по 22 ноября, а также 30 ноября на Курском направлении изменится движение поездов.
По будням после 23:00 и по выходным дням после 21:00:
•Поезда в строну на Нахабино не будут останавливаться на станции Покровская.
— для проезда с Покровской в сторону Нахабино проезжайте до станции Красный Строитель и пересаживайтесь на поезд в обратном направлении.
•На станции Царицыно буд…
Письмо из Хогвартса доставили прямо в московское метро.
На станции «Киевская» пассажир разгуливал по переходам с живой совой, которая невозмутимо восседала у него на рюкзаке, а потом укатил в сторону Митино.
Следующая остановка — Косой переулок 🦉
📹 cosmonaut.jim
🚌 Наш митинский экспресс е30 — в топе самых популярных маршрутов Москвы!
Маршрут е30 «4-й микрорайон Митина — Метро „Китай-город“» официально вошёл в тройку самых востребованных экспрессов столицы. Для жителей нашего района это один из главных способов быстро и без пересадок доехать прямо до самого центра города.
Почему митинцы выбирают е30:
• Прямая связь с центром. Можно сесть в 4-м микрорайоне Митина и доехать …
🧑🏻⚖️ Суд взыскал с пассажира в пользу метро 360 тыс. руб. за падение на пути на станции «Пятницкое шоссе» после приема сильнодействующих веществ - ТАСС
Инцидент произошел летом этого года. Мужчина принял без назначения врача прегабалин, трамадол и тропикамид — потенциально опасные психоактивные вещества. После он упал на пути - из-за этого более 10 минут не было движения поездов.
МИТИНО💙МОСКВА
@RAION_MITINO
Обход завершён.
🟢Все обращения жителей взяты на контроль и внесены в протокол обхода в том числе:
✅ Провести опрос жителей. «О замене покрытия на собачьей площадке» по адресу: ул. Генерала Белобородова, д. 12.
✅ Установить искусственную дорожную неровность (ИДН) за домом по адресу: Волоцкой пер., д. 7, к. 1.
✅ Организовать работу по удалению стикеров и граффити на дорожных знаках по адресу : ул. Генерала Белоборо…
❤5👍3
Showing the 12 most recent of 206 posts we hold for @raion_mitino. 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.
Posts edited after publishing
@raion_mitino edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
24 August 2026
Most recent edit
14 November 2026
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 3 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.
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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“РАЙОН МИТИНО 🔴 МОСКВА” (@raion_mitino), 11,799 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/raion_mitino.
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.