Channel
@ano_moscow_team
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
825subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002704076680 |
|---|---|
| Type | Channel |
| Username | @ano_moscow_team |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 4 times, most recently 14 September 2026 |
| On Telegram | t.me/ano_moscow_team |
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 02:18 | 825 | -5 |
| 14 Aug 2026, 19:07 | 830 | -1 |
| 8 Aug 2026, 01:30 | 831 | no change |
| 7 Aug 2026, 17:14 | 831 | first reading |
6 posts held, back to 17 July 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 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
226 reactions across 6 posts, in 14 distinct kinds. The most used accounts for 55.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 125 | 55.3% | |
| ❤ | 26 | 11.5% | |
| 👍 | 18 | 7.96% | |
| ⚡ | 11 | 4.87% | |
| 😱 | 10 | 4.42% | |
| ❤🔥 | 7 | 3.10% | |
| 🥰 | 7 | 3.10% | |
| 🏆 | 6 | 2.65% | |
| 🫡 | 5 | 2.21% | |
| 💯 | 3 | 1.33% | |
| 🤩 | 3 | 1.33% | |
| 👏 | 2 | 0.885% | |
| 😎 | 2 | 0.885% | |
| 🎉 | 1 | 0.442% |
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 6 of the 6 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 226 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 17 July 2026 to 6 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.
Есть тишина, в которой слышно, как бьётся сердце перед выстрелом 🔫 Здесь, в Екатеринбурге, мы четвёртый день подряд выходим на рубеж и оттачиваем все элементы до автоматизма. Именно из таких дней и складывается команда, на которую можно положиться в любой ситуации. Смотрите, как выглядит наша подготовка, в кадрах выше ⬆️
🔥17👍7❤5❤🔥3😱2
Снова в Екатеринбурге 🔫 Уральская земля вновь принимает нас — мы здесь не впервые, и задачи с каждым разом становятся сложнее. Продолжаем работать над точностью на огневом рубеже и выносливостью на полосе препятствий. Готовимся каждый день, где бы мы ни были 💪
🔥21👍7❤🔥4🤩2💯1😎1
Выход на рубеж — и мир сужается до мишеней и траекторий 🔫 В рамках сборов в Екатеринбурге наша команда приняла участие в международных соревнованиях по практической стрельбе «Eurasia Open 2026». 24 упражнения, 460 выстрелов и ни секунды на раздумья! На огневой решали детали: темп, реакция, точность и скорость смены магазина 🎯 Неделя интенсивной подготовки позади. Домой везём чёткий план, над чем работать до следую…
🔥20⚡7🥰5💯2❤1🎉1
Если на огневом рубеже оттачиваем точность, то на полосе препятствий — скорость и выносливость! На видео — один из этапов нашей подготовки к предстоящим соревнованиям ⚡️ Ставьте 🔥 — чтобы зарядить нашу команду на успех!
🔥30❤12😱8🤩1😎1
Из Сочи — в Екатеринбург 🤩 Локации меняются быстрее, чем успеваем распаковать сумки. Каждый новый сбор — это новый этап подготовки и новые задачи. Основное время проводим на огневом рубеже: отрабатываем элементы соревновательных упражнений, доводим технику до автоматизма 🔫 Но и про физическую подготовку не забываем — продолжаем заниматься на полосе препятствий! Меняем города, но не меняем цель. Работа продолжаетс…
🔥19❤8⚡4👍3🥰2
Море видели. Но чаще — стадион, зал и секундомер ⏰ Каждый из нас проживает сборы по-своему. Но есть то, что объединяет всю команду — ежедневная работа над собой! Чем запомнились сборы в Сочи? Ответы — в карточках ⬆️
🔥18🏆6🫡5👏2👍1
Showing the 6 most recent of 6 posts we hold for @ano_moscow_team. 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.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Moscow Team” (@ano_moscow_team), 825 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/ano_moscow_team.
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.