Channel
@MoscowAfish
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
29,311subscribers
-165 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001173435423 |
|---|---|
| Type | Channel |
| Username | @MoscowAfish |
| Description | Новости города в удобном для вас формате! Актуальные и интересные события, скидки, акции, мероприятия и концерты! По вопросам рекламы пишите @kira_polit Зарегистрирован в РКН: https://www.gosuslugi.ru/snet/679a38b1063b2d237426ffd2 |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 57 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/MoscowAfish |
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 80% 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 3 other registered channels. This entry also sits inside a group of 3 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 |
|---|---|---|---|
| @Mos_culture/273129 Jun 2026, 08:49 UTC | @MoscowAfish/2475 · this entry29 Jun 2026, 08:50 UTC | 1.00 | under a minute |
| @Mos_culture/27333 Jul 2026, 11:30 UTC | @MoscowAfish/2477 · this entry3 Jul 2026, 11:30 UTC | 1.00 | under a minute |
| @Mos_culture/273813 Jul 2026, 09:18 UTC | @MoscowAfish/2482 · this entry13 Jul 2026, 09:19 UTC | 1.00 | under a minute |
| @Mos_culture/27655 Sept 2026, 01:32 UTC | @MoscowAfish/2509 · this entry5 Sept 2026, 01:32 UTC | 1.00 | under a minute |
| @Mos_culture/277014 Sept 2026, 22:32 UTC | @MoscowAfish/2514 · this entry14 Sept 2026, 22:32 UTC | 1.00 | under a minute |
| @Mos_culture/277522 Sept 2026, 21:18 UTC | @MoscowAfish/2518 · this entry22 Sept 2026, 21:18 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Mos_culture | 28 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Mos_culture (28–0) |
| @MoscowEdim | 27 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (27–0) |
| @Moscow_interesnoe | 8 (8/8 hand-verifiable sample passed) | 1.00 | 1.9 hours | this entry (8–0) |
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. 15 of the 28 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 68 comparable posts for this entry, running 29 June 2026 to 10 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.
Of the group of 3 channels, the one whose matching posts we hold earliest is @Mos_culture. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · 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 3 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 |
|---|---|---|
| 9 Nov 2026, 14:31 | 29,311 | -3 |
| 8 Nov 2026, 09:38 | 29,314 | -1 |
| 7 Nov 2026, 03:19 | 29,315 | -4 |
| 6 Nov 2026, 05:36 | 29,319 | -1 |
| 5 Nov 2026, 05:18 | 29,320 | -2 |
| 4 Nov 2026, 02:09 | 29,322 | -2 |
| 2 Nov 2026, 23:49 | 29,324 | -1 |
| 1 Nov 2026, 20:28 | 29,325 | -1 |
| 31 Oct 2026, 16:40 | 29,326 | -1 |
| 30 Oct 2026, 19:30 | 29,327 | +2 |
| 28 Oct 2026, 22:51 | 29,325 | -1 |
| 26 Oct 2026, 18:50 | 29,326 | -1 |
| 25 Oct 2026, 19:20 | 29,327 | -1 |
| 24 Oct 2026, 21:27 | 29,328 | -1 |
| 23 Oct 2026, 21:27 | 29,329 | -5 |
| 22 Oct 2026, 18:47 | 29,334 | -4 |
| 21 Oct 2026, 17:41 | 29,338 | -1 |
| 20 Oct 2026, 15:39 | 29,339 | -3 |
| 19 Oct 2026, 14:31 | 29,342 | -2 |
| 18 Oct 2026, 16:36 | 29,344 | first reading |
68 posts held, back to 29 June 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 160 pages of 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.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 68 (29 June 2026 – 10 November 2026) |
| Views total | 191,500 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 00:43 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.
Lifetime counters from Telegram’s own channel header, read 11 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.
Telegram’s own ‘edited’ marker: 0 of 15 posts held from the last 30 days (0%) 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).
Массовые задержания прошли на Китай-городе в Москве. К парку «Горка» приехали более десяти автозаков. По словам очевидцев, полиция задерживала молодых людей в парке, возле баров и на соседних улицах. Среди задержанных есть несовершеннолетние. Людей доставляли в ОВД «Басманный» и «Таганский». По оценкам самих задержанных, суммарно в отделы могли привезти около 300 человек. В МВД заявили, что в центре Москвы проводи…
Эммануэлю Макрону разработали план эвакуации из Елисейского дворца на случай его штурма протестующими, сообщает The Telegraph. По данным издания, у Макрона есть секретный бункер за пределами Парижа, куда его могут перевезти в случае массовых беспорядков. Планы эвакуации начали разрабатывать после нападения сторонников движения "желтых жилетов" на кортеж президента в 2018 году. Также французские спецслужбы опасаютс…
Минстрой предлагает включить в тарифы ЖКХ дополнительные расходы на ремонт изношенных котельных и коммунальных сетей. Если инициативу примут, прибавка затронет отопление, водоснабжение и водоотведение. Полученные деньги планируют направлять на капитальный ремонт и модернизацию инфраструктуры.
ФНС использует открытые данные из соцсетей, чтобы выявлять тех, кто регулярно оказывает услуги и получает доход, но не декларирует его. В поле внимания могут попасть домашние кондитеры, электрики, мастера красоты, репетиторы и другие специалисты, которые рекламируют свои услуги через соцсети. Публикации, цены и объявления могут стать поводом для дополнительной проверки.
На подлёте к Москве сбили 20 беспилотников. В Подмосковье объявляли беспилотную опасность, а во Внуково и Домодедово вводили временные ограничения на полёты. Авиакомпании корректировали расписание рейсов.
С кошельков Binance вывели активы на сумму до $5,8 млрд — биржа расследует возможный взлом. Если кража подтвердится, она может стать крупнейшей в истории криптовалют. Уже заморожено более $2,5 млрд подозрительных активов. В Binance заявляют, что средства пользователей находятся в безопасности.
Три сотрудника МЧС пострадали во время тушения пожара в санатории «Узкое». Один пожарный с тяжёлой травмой позвоночника доставлен в реанимацию, второй получил перелом рёбер и ушибы. Третий спасатель, предварительно, остаётся под завалами живым. Сейчас его готовятся извлечь.
Мошенники начали рассылать москвичам фальшивые досудебные претензии на крупные суммы. В письмах предлагают открыть вложение с «документами», но внутри может находиться вирус. Если открыть такой файл, злоумышленники могут получить доступ к данным и устройству пользователя.
Банк России сохранил ключевую ставку на уровне 14% годовых. Решение означает, что условия по кредитам и вкладам пока резко не изменятся. Следующее решение ЦБ по ставке будут ждать уже с особым вниманием.
68-летний житель Подмосковья получил два года условно за незаконную майнинг-ферму. Оборудование для добычи криптовалюты он разместил в сарае и грузовом контейнере, а электричество, по данным суда, получал через незаконное подключение к ЛЭП. Ущерб оценили в 4,1 млн рублей. Эту сумму пенсионера обязали возместить, а оборудование конфисковали.
Пассажиры Air Cairo почти 60 часов не могут вылететь из Москвы в Хургаду, сообщает Baza. Рейс должен был отправиться ещё 16 октября в 01:45, но вылет переносили уже трижды. Сначала причиной стала угроза БПЛА, затем одной из стюардесс стало плохо, а позже заболел весь экипаж. Люди всё это время ждут возможности наконец улететь в Египет.
Москвич отсудил 35 тысяч рублей у таксиста, который отказался везти его в аэропорт. Водитель принял заказ, но позже сам отменил поездку, сославшись на неисправность машины. Пассажир из-за этого едва не опоздал на рейс и решил обратиться в суд. В августе Мосгорсуд постановил взыскать с водителя компенсацию морального вреда, штраф и расходы на юриста.
Showing the 12 most recent of 68 posts we hold for @MoscowAfish. 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.
We recorded 1 post on @MoscowAfish as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 8 September 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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Москва Афиша Театры Концерты” (@MoscowAfish), 29,311 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/MoscowAfish.
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.