Channel
@Black_Mytishchi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
61subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002244110320 |
|---|---|
| Type | Channel |
| Username | @Black_Mytishchi |
| Description | Министерство не твоих собачих дел. Здесь мы будем просто общаться на разные темы |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Black_Mytishchi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 04:31 | 61 | no change |
| 7 Aug 2026, 16:28 | 61 | first reading |
17 posts held, back to 10 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 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 17 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
35 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 34.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 12 | 34.3% | |
| 🔥 | 8 | 22.9% | |
| 👍 | 6 | 17.1% | |
| 🤣 | 4 | 11.4% | |
| 🤡 | 2 | 5.71% | |
| 👏 | 1 | 2.86% | |
| 💯 | 1 | 2.86% | |
| 🤮 | 1 | 2.86% |
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 12 of the 17 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 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 10 June 2026 to 3 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.
ТЕПЕРЬ МОЖНО УДАЛИТЬ ОЦЕНКУ САМОСТОЯТЕЛЬНО Но только 2 раза, и только за сегодня :) Тестируют, видимо. Если вы думаете, что пассажир вам снизит рейтинг, можете удалить его оценку. Новое казино от Яндекса 😂 Ну, хоть, так. Спасибо, хули 👍 @biztaxi
Злостный нарушитель ч.4
😁3
Злостный нарушитель ч.3
😁3
Злостный нарушитель ч.2
😁3
⚡️Стало известно, кто виноват в топливном кризисе 📢 Пездуза
🤣4👍1💯1
Полнолуние.... Ждём вурдалаков
🔥1
Посмотрите на него.... Злостный нарушитель
https://youtu.be/gPCzxf6iIvI?is=Kfpby5Kt1QxdyqCI
😁2
https://youtube.com/shorts/Vi-VLBga774?is=rxSldKaIXxidczZ4
🔥2👍1👏1🤮1
Когда принимаешь заказ изначально с неверно рассчитанной подачей из-за не стабильной гео, и во время подачи так же гео ебётся и у пасса показывает то 10 минут.... То 20 минут.... Естественно он отменит заказ и я окажусь в нежелательной жопе)))
🤡1
Новая игрушка
🔥3🤡1
Ой.. что это у меня?))))
😁1
Showing the 12 most recent of 17 posts we hold for @Black_Mytishchi. 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Черные Мытищи” (@Black_Mytishchi), 61 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Black_Mytishchi.
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.