🟡 This community is now protected by Collab.Land Token-gate your community and verify members automatically. Click below to verify your wallet and gain access.
Channel
rusich_army
@rusich_army
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
12,040subscribers
+635 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1004325174316 |
|---|---|
| Type | Channel |
| Username | @rusich_army |
| Created | 5 July 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/rusich_army |
Topic
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 22:41 | 12,040 | +57 |
| 6 Sept 2026, 18:15 | 11,983 | +61 |
| 4 Sept 2026, 09:20 | 11,922 | +26 |
| 2 Sept 2026, 22:36 | 11,896 | +16 |
| 1 Sept 2026, 21:54 | 11,880 | +9 |
| 31 Aug 2026, 20:36 | 11,871 | +10 |
| 30 Aug 2026, 23:07 | 11,861 | +9 |
| 29 Aug 2026, 21:55 | 11,852 | +15 |
| 28 Aug 2026, 19:55 | 11,837 | +30 |
| 27 Aug 2026, 20:27 | 11,807 | +26 |
| 26 Aug 2026, 17:45 | 11,781 | +25 |
| 25 Aug 2026, 16:48 | 11,756 | +17 |
| 24 Aug 2026, 15:54 | 11,739 | +11 |
| 22 Aug 2026, 21:33 | 11,728 | +25 |
| 21 Aug 2026, 14:05 | 11,703 | -5 |
| 20 Aug 2026, 14:15 | 11,708 | +82 |
| 19 Aug 2026, 13:53 | 11,626 | +18 |
| 18 Aug 2026, 14:36 | 11,608 | +21 |
| 17 Aug 2026, 12:56 | 11,587 | +8 |
| 16 Aug 2026, 06:04 | 11,579 | first reading |
Engagement
2 posts held, back to 5 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 47 pages 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 2 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel created
Showing the 2 most recent of 2 posts we hold for @rusich_army. 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.
Mentions
Named by 118 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.
@arx_spn · 1,027,561642 postsZERGULIO
@SergeyKolyasnikov · 444,12471 postsМир сегодня с "Юрий Подоляка"
@yurasumy · 2,665,43363 postsРыбарь
@rybar · 1,548,15446 postsReadovka
@readovkanews · 2,014,45839 postsДва майора
@dva_majors · 1,160,33416 posts106 гвардейская дивизия ВДВ Тула
@vdv_106 · 12,0979 postsЮжный ветер
@south0wind · 12,9427 postsТот самый Олень🦌
@trueolen · 144,3637 postsНЕ*АТЛЕТ
@athlete_axc · 12,7805 postsПортсигар Z
@port_z · 515 postsАгрегатор Z | Сводки специальной военной операции
@AgregatorZOV · 34 postsБои от первого лица 🇷🇺 | Combat GoPro
@RuCombatFootage · 13,5474 postsАдминистрация терминатора Z
@trogonklon · 4474 postsЮжный тревожный чемодан 🧳
@chemodan_trevog · 673 postsПЕРЕХВАТ (Z)
@dvesti22 · 7,2503 posts🇷🇺 ГОВОРИТ ФРОНТ!
@govoritfront · 23 postsКОНТРАКТ И ТОЧКА. ЯРОСЛАВСКАЯ ОБЛАСТЬ
@mobilizaciaitocka · 193 postsАрмия России
@russian_army · 4693 postsCODE | studio
@code_arthouse · 1972 postsДьявол ходит в Дикси
@dixi_devil · 5,4602 postsVремя выбрало Нас 🇷🇺
@nache_vremja · 4,5022 postsПатриот 54
@patriot54nsk · 612 posts🇷🇺ШТОРМ ВДВ🇷🇺
@shtorm345 · 2682 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“rusich_army” (@rusich_army), 12,040 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/rusich_army.
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.