🌠 Лучший и самый большой канал о Москве
Прислать новость: @moscowachnewsbot
Реклама: t.me/pricemos/620
Москвач Daily: @mosdaily
Сайт: https://mskch.ru
РКН: clck.ru/3FTixA
Created
4 January 2021 — measured — dated from the channel’s first post
National news — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
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 word for word on 12 other registered channels. They sit inside a group of 377 channels that share the same post bodies 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)
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 327 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 18,384 comparable posts for this entry, running 5 July 2021 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.
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).
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
Views and reactions moved apart
On 10 of the 451 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0100 reactions per view.
Each interval, as we read it — views and reactions before and after
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_copy · clone_mutual · clone_source · view_reaction_decoupling, last confirmed 23 September 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, 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.
326 more channels are in this same group but not listed individually here.
Growth
34 measurements spanning 42 days, net -96,177. 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 4,078,230–4,362,280 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)
Subscribers
Change
17 Sept 2026, 09:18
4,111,005
-11,777
15 Sept 2026, 07:19
4,122,782
-4,944
13 Sept 2026, 14:38
4,127,726
-4,208
11 Sept 2026, 21:15
4,131,934
-14,535
9 Sept 2026, 11:20
4,146,469
-20,333
6 Sept 2026, 05:58
4,166,802
-13,847
4 Sept 2026, 03:17
4,180,649
-9,433
2 Sept 2026, 17:43
4,190,082
-8,846
1 Sept 2026, 15:23
4,198,928
-8,993
31 Aug 2026, 13:48
4,207,921
-9,197
30 Aug 2026, 11:45
4,217,118
-9,134
29 Aug 2026, 09:46
4,226,252
-10,224
28 Aug 2026, 07:07
4,236,476
-9,822
27 Aug 2026, 04:59
4,246,298
-10,891
26 Aug 2026, 03:11
4,257,189
-10,705
25 Aug 2026, 04:54
4,267,894
-12,274
24 Aug 2026, 01:37
4,280,168
-22,309
22 Aug 2026, 11:52
4,302,477
+8,541
21 Aug 2026, 02:54
4,293,936
-15,613
20 Aug 2026, 04:02
4,309,549
first reading
Engagement
29,855 posts held, back to 4 January 2021 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5,645 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
5.84%
avg views ÷ 4,111,005 subscribers
Avg views / post
240,000
498 posts measured
Reaction rate
1.19%
reactions ÷ views · ER floor
Posts in window
498
of 29,855 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 22 September 2026
Posts held
29,855 (4 January 2021 – 22 September 2026)
Views total
119,516,800
Reactions total
1,421,427
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Sept 2026, 21:02 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
≈12,700
Videos
≈8,160
Links
≈8,700
Lifetime counters from Telegram’s own channel header, read 22 September 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 42m
Average length
24s
Measured directly from 254 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 453 of this channel’s own posts over the last 30 days (1 of the 24-hour readings behind this are interpolated, not measured directly): across 442 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.4 hours of being posted; a typical post has already reached 32.1% of its 24-hour view count within the first hour, and 72.1% within the first six; the median 24-hour reach across those posts is 201,000 views — 4.89% of this channel’s own subscriber count (90th percentile 231,000).
8 most recently posted, with a view-velocity reading
2.8 hoursprovisional — final view count still climbing
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Reaction mix
2,429,860 reactions across 834 posts, in 14 distinct kinds. The most used accounts for 21.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
530,197
21.8%
🤡
421,320
17.3%
😱
298,701
12.3%
🤬
267,693
11.0%
😁
254,689
10.5%
👍
199,909
8.23%
😭
145,099
5.97%
👎
141,570
5.83%
custom 5251622264197107992
48,588
2.00%
😢
45,513
1.87%
custom 5289923786110420788
20,848
0.858%
🙏
20,723
0.853%
🥰
20,143
0.829%
🎉
14,867
0.612%
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 1,000 of the 1,000 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 2,915,895 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 28 July 2026 to 22 September 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
2.30%
23 of 1,000 posts carry an ad marker
Regulatory tokens
23
posts carrying an erid · 23 distinct tokens
Median views · ads
234,000
over 23 measured posts
Median views · rest
251,000
over 977 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2VSb5ywuYcz
1
29 August 2026
29 August 2026
2Vfnxxfucuq
1
20 August 2026
20 August 2026
2VtzquX58gK
1
15 August 2026
15 August 2026
2Vtzqv8foJL
1
7 September 2026
7 September 2026
2VtzqvLMmhu
1
3 September 2026
3 September 2026
2VtzqvLXRoR
1
19 August 2026
19 August 2026
2Vtzqw2X3me
1
14 September 2026
14 September 2026
2Vtzqw5BvuR
1
20 August 2026
20 August 2026
2Vtzqwb984T
1
17 August 2026
17 August 2026
2VtzqwowP4G
1
6 September 2026
6 September 2026
2VtzqwpTjFH
1
26 August 2026
26 August 2026
2VtzqwpXM8X
1
13 August 2026
13 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. 11 further tokens are held for this entry and not listed here.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 28 July 2026 to 22 September 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.
🍬 Фанатка знаменитых красных батончиков «Рот Фронта» устроила конфетам настоящий краш-тест — и нашла самые вкусные.
Девушка сравнила сладости с трех заводов компании — московского, воронежского и тамбовского. Победителями стали тамбовские батончики с буквой D на упаковке. А вот московские не прошли: показались слишком засахаренными и «пластмассовыми» на вкус.
Сладкоежкам на заметку.
⚽️ С 1 октября на всех матчах Кубка России будет нужен Fan ID — без паспорта болельщика на стадион не пустят.
Меру объясняют требованиями безопасности.
🫎 Лось-дебошир портит машины возле ЖК «Измайловский лес».
Как рассказал Москвачу один из жителей, с утра он заметил на своем автомобиле вмятины и повреждения капота, проверил камеры и понял, что машину испортил лось. На хулиганские действия сохатого жалуются и другие жильцы.
🐘🥹 В Москве открыли вакансию специалиста по уходу за слонами с зарплатой от 100 тысяч рублей.
Человеку предстоит проводить время с животными, кормить их, убирать в вольерах, а также готовить слонов к репетициям и спектаклям. Среди других необычных вакансий сентября — дегустатор-контролёр мясной продукции, флорист клубничных букетов и вязальщица.
Ничего себе.
💰 В Москве насчитали 154 тысячи безработных жителей, имеющих многочисленные объекты недвижимости и транспортные средства.
Часто речь идет о незадекларированных доходах от сдачи недвижимости и автомобилей. Если налоговая подтвердит нарушение, владельцам могут доначислить налоги.
👵 Пенсионерка в Путилково через прокуратуру добилась, чтобы грузовик с продуктами для супермаркета не разгружался под ее окном — жительница много лет терпела шум от автомобиля.
Квартира пенсионерки находится прямо на пожарным выходом, через который разгружался грузовик. Женщина обратилась в Красногорскую прокуратуру, которая 16 сентября установила сразу несколько нарушений и потребовала от руководства супермаркета и…
😥 В Подмосковье обнаружили новый очаг бешенства — карантин ввели в селе Слемские Борки в Луховицах.
Ветеринары будут обходить дома, прививать животных и отлавливать бездомных — их изолируют на 14 дней. Ранее бешенство обнаружили в деревне Чернево Можайского округа, где причиной стала енотовидная собака, которая зашла во двор частного дома.
🎨 Выпускники университета имени С. Г. Строганова используют планшет HUAWEI MatePad Air для восстановления стульев из музыкальных салонов XIX века.
Точная передача линий и чувствительность экрана к нажатию помогают воспроизводить детали исторической резьбы, а приложение GoPaint ускоряет работу с чертежами и скетчами благодаря большому выбору кистей и умной карте цветов. Так современные технологии помогают не только в…
🙃 Мрачные лавочки, похожие на гробы, на станции «Народное Ополчение» решили видоизменить — у них закруглили углы. Правда, сильно ситуацию это не изменило.
Видео: ogaltsoff
😨 У москвича изъяли права из-за «жирных» номеров.
Буквы и цифры на номерах оказались выше нормы, а линии толще. Инспектор и суд сочли знаки подложными и лишили водителя прав на полгода.
Мужчина утверждает, что номера заказывал не он, а родственник в специальной фирме. Теперь он пытается вернуть права через суд.
☔️ Сильный ливень накроет Москву в обед и продлится до ночи — в столице объявлен «жёлтый» уровень опасности.
❤716😱512🤬179👍68
Showing the 12 most recent of 29,855 posts we hold for @moscowach. 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
@moscowach edited 28 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
10 August 2026
Most recent edit
22 September 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 223 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 114 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Handles this channel named that no longer answer
Dead references
39
handles named in this channel’s posts, vacant today
Evidenced gone
2
we ourselves saw one of these resolve, at some point
Never seen alive
37
vacant every time we have ever looked
@moscowach named 39 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@rgrunews named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 13 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@nuum_ru named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 12 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@rian_ru named in 91 posts, 8 August 2026 – 8 August 2026
@moscowachneesbot named in 3 posts, 8 August 2026 – 8 August 2026
@moscowach_stories named in 3 posts, 8 August 2026 – 8 August 2026
@redakciya_channel named in 2 posts, 8 August 2026 – 8 August 2026
@yandexplusblog named in 2 posts, 8 August 2026 – 8 August 2026
@moscowachnewbot named in 2 posts, 8 August 2026 – 8 August 2026
@evgeny_alekss named in 1 post, 8 August 2026 – 8 August 2026
@exsava76 named in 1 post, 8 August 2026 – 8 August 2026
@gazprombank_official_channel named in 1 post, 8 August 2026 – 8 August 2026
@github_official named in 1 post, 8 August 2026 – 8 August 2026
@jokerokker named in 1 post, 8 August 2026 – 8 August 2026
@katy_yur named in 1 post, 8 August 2026 – 8 August 2026
@lelixl1 named in 1 post, 8 August 2026 – 8 August 2026
@ligiober named in 1 post, 8 August 2026 – 8 August 2026
@mam_lino_1991 named in 1 post, 8 August 2026 – 8 August 2026
@maximkhhan named in 1 post, 8 August 2026 – 8 August 2026
@moscowachbewsbot named in 1 post, 8 August 2026 – 8 August 2026
@moscowresto named in 1 post, 8 August 2026 – 8 August 2026
@phorbes named in 1 post, 8 August 2026 – 8 August 2026
@plehanyura named in 1 post, 8 August 2026 – 8 August 2026
@rt_russian named in 1 post, 8 August 2026 – 8 August 2026
@sigen_media named in 1 post, 8 August 2026 – 8 August 2026
@suchkovvvv named in 1 post, 8 August 2026 – 8 August 2026
@ta_nails_91 named in 1 post, 8 August 2026 – 8 August 2026
@tsiganova_yan named in 1 post, 8 August 2026 – 8 August 2026
@tsvetnoycentralmarket named in 1 post, 8 August 2026 – 8 August 2026
@vlad_good4you named in 1 post, 8 August 2026 – 8 August 2026
@xitker named in 1 post, 8 August 2026 – 8 August 2026
@anashachat named in 1 post, 8 August 2026 – 8 August 2026
@ziyodfwek named in 1 post, 8 August 2026 – 8 August 2026
@aphonya_art named in 1 post, 8 August 2026 – 8 August 2026
@artgolubyatnikov named in 1 post, 8 August 2026 – 8 August 2026
@clxudsaw named in 1 post, 8 August 2026 – 8 August 2026
@cycjl named in 1 post, 8 August 2026 – 8 August 2026
@daikja named in 1 post, 8 August 2026 – 8 August 2026
@elkamoscowach named in 1 post, 8 August 2026 – 8 August 2026
@erudit named in 1 post, 8 August 2026 – 8 August 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 7 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
Мужское Женское. Редакция @dorogoemj · 21,823 Telegram ranks this channel #1 of 67 here — alongside 66 others — read 22 September 2026
Хроники Москвы @mskhronika · 36,160 Telegram ranks this channel #1 of 89 here — alongside 88 others — read 1 September 2026
Чат Андреевича @andreevichat · 40,917 Telegram ranks this channel #1 of 76 here — alongside 75 others — read 31 August 2026
Больше @bolshenews · 67,836 Telegram ranks this channel #1 of 92 here — alongside 91 others — read 20 August 2026
Ингосстрах @ingosofficial · 76,912 Telegram ranks this channel #1 of 69 here — alongside 68 others — read 20 August 2026
Москва, Бизнес и Технологии @mosbiznes · 81,266 Telegram ranks this channel #1 of 95 here — alongside 94 others — read 18 August 2026
Московский ревизор @mosreview · 83,303 Telegram ranks this channel #1 of 92 here — alongside 91 others — read 18 August 2026
Москва 2033 @mosheadlines · 86,990 Telegram ranks this channel #1 of 89 here — alongside 88 others — read 17 August 2026
МОСКВА СЕГОДНЯ @moskvae · 153,059 Telegram ranks this channel #1 of 82 here — alongside 81 others — read 15 August 2026
Мои Люберцы ®️ @myluber · 107,483 Telegram ranks this channel #1 of 66 here — alongside 65 others — read 15 August 2026
Маркетинговый джем @marketologjam · 120,029 Telegram ranks this channel #1 of 65 here — alongside 64 others — read 14 August 2026
Москва онлайн @mskonline2024 · 173,509 Telegram ranks this channel #1 of 86 here — alongside 85 others — read 12 August 2026
Мой город — Москва @mskmycity · 205,150 Telegram ranks this channel #1 of 88 here — alongside 87 others — read 11 August 2026
Мосфид • Новости Москвы @moslenta · 213,387 Telegram ranks this channel #1 of 83 here — alongside 82 others — read 11 August 2026
КудаМосква @kudamsk24 · 230,378 Telegram ranks this channel #1 of 91 here — alongside 90 others — read 11 August 2026
Е-коммерс @kommerc · 238,022 Telegram ranks this channel #1 of 81 here — alongside 80 others — read 11 August 2026
Москва 24/7 @msk7days · 2,198,178 Telegram ranks this channel #1 of 67 here — alongside 66 others — read 10 August 2026
Москва радует • Афиша @Moscow_happy · 371,706 Telegram ranks this channel #1 of 88 here — alongside 87 others — read 10 August 2026
Моя Москва @moscowmi · 765,892 Telegram ranks this channel #1 of 93 here — alongside 92 others — read 10 August 2026
Москва на максималках @mosjournal · 386,973 Telegram ranks this channel #1 of 91 here — alongside 90 others — read 10 August 2026
Москва+ @moscowplus · 1,199,829 Telegram ranks this channel #1 of 85 here — alongside 84 others — read 8 August 2026
Новости Москвы @moscowmap · 2,674,200 Telegram ranks this channel #1 of 90 here — alongside 89 others — read 7 August 2026
Москва сегодня @moscow · 2,655,291 Telegram ranks this channel #1 of 92 here — alongside 91 others — read 7 August 2026
Первый Московский @mosguru · 3,180,311 Telegram ranks this channel #1 of 82 here — alongside 81 others — read 7 August 2026
This channel appears in 1,562 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.
Domains linked from posts
99 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
www.zr.ruregistrable domain: zr.ru1 post · 6 February 2026 – 6 February 2026 · example post
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Москвач • Новости Москвы” (@moscowach), 4,111,005 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/moscowach.
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.