Channel
@multi_XAM
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
16,027subscribers
-30 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001780981596 |
|---|---|
| Type | Channel |
| Username | @multi_XAM |
| Description | Аналитика и новости от «военного андерграунда». Разбираем обстановку на линии боевого соприкосновения. Связь с админом: @Z_MultiXam Разместить контент: @MultiXAM_content Реклама: вакант Поддержка канала: 5228 6005 9512 2708 (Сбер) |
| Created | 20 June 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/multi_XAM |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:13 | 16,027 | -6 |
| 11 Aug 2026, 23:52 | 16,033 | -7 |
| 10 Aug 2026, 20:51 | 16,040 | -1 |
| 9 Aug 2026, 19:41 | 16,041 | -6 |
| 8 Aug 2026, 18:10 | 16,047 | -1 |
| 7 Aug 2026, 20:32 | 16,048 | -4 |
| 6 Aug 2026, 23:51 | 16,052 | -5 |
| 6 Aug 2026, 04:15 | 16,057 | no change |
| 6 Aug 2026, 04:07 | 16,057 | first reading |
17 posts held, back to 14 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof 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 5 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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 4 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.
3,589 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 49.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,768 | 49.3% | |
| 🔥 | 1,446 | 40.3% | |
| 🤔 | 121 | 3.37% | |
| 😁 | 105 | 2.93% | |
| 👏 | 80 | 2.23% | |
| 👌 | 57 | 1.59% | |
| 👎 | 12 | 0.334% |
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 17 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 3,589reactions 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 14 May 2025 to 5 July 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.
✍ Всем салют, дорогие наши читатели! Просим прощения за долгое отсутствие в сети! Админ и партнеры в строю! Канал и наше дело живо! По возможности будем вас знакомить со своими наблюдениями за обстановкой. Спасибо, что не забываете 🤝🫡 🏴☠
🔥358👍160👌23👏14🤔3😁1
С новым 2026! Победы и больше сил!
👍218🔥114😁93👌6👎5
С годовщиной крылатых пехотинцев!
👍198🔥67👏17😁5
#Аэротакси - если надо быстро
🔥116👌21👍12👏4
✍️🗺️📐 Общая конфигурация линии боевого соприкосновения на Покровско-Мирноградском направлении по данным #ISW - Института изучения войны (Institute for the Study of War) и Военкора Марата Хайруллина. #КартыСВО ✈️ @Multi_XAM
🔥82👍53🤔3
✍️⁉️ Ответы на вопросы: За несколько дней накопились вопросы читателей в обратной связи: ❓«Почему вы не освещаете конкретные успехи наших войск? Вот, например, наши взяли то-то...» 📄 Построю ответ так: 🔻Во-первых, о взятии того или иного населенника официально заявляют уполномоченные на то лица. Мы же не преследуем информационной цели быстрее опубликовать экстренные новости, у нас иной формат и задачи - мы описываем …
👍230🔥51👏11👌3😁2
✍️📽️ Трасса Краматорск - Доброполье: ВС РФ наносят удары дальнобойными FPV 🛸 по логистике ВСУ. ✈️ @Multi_XAM
🔥138👍54👏6
✍️‼️ Общая конфигурация логистических путей в Покровске после авиа-ударов ВКС РФ 2024 года. Въезд в южную часть города по трассе Т0405 со стороны Удачного не возможен - Котлино под нашим контролем, а объездная дорога Западнее Удачного на Сергеевку и трассу М-30 (со стороны Павлограда) как и сама эта трасса на сегодня под огневым контролем наших ударных FPV-групп. ✈️ @Multi_XAM
👍100🔥33🤔9😁1
✍️‼️ Положение противника на Покровском направлении (на 18 мая) - дополнение к части 1 разбора По нашим данным, противник достаточно организованно готовится к отходу из Покровска (Красноармейска). При этом, в сети постоянно публикуются материалы, где UA-медиа показывают, что город почти брошен, очагово остаются гражданские, а сами ВСУ измотаны и испытывают жесткие проблемы с логистикой (о причинах читайте выше). Про…
👍108🤔21
✍️📰 Известный в Twitter 🕊| 👥OSINT-ресурс AMK_Mapping сообщает, со ссылкой на украинские источники, что российские ударные группы начали наносить огневое поражение FPV-дронами по логистике противника на трассе Краматорск - Доброполье (удаление от ЛБС - ❗️29км). ✈️ @Multi_XAM
🔥157👍63👏14😁1
✍️‼️Также противником продолжаются работы по возведению инженерных и установке минных заграждений в резервной полосе обороны за Покровском (Красноармейском), о чем сообщают наши коллеги. ✈️ @Multi_XAM
🤔62👍22🔥12👎5
✍️📈 Та самая дорога из Покровска (Красноармейска) на Доброполье - главная логистическая артерия снабжения, ротации и эвакуации ВСУ в этом районе. На протяжении практически всей дороги противник установил противодронные сети, о чем мы ранее писали. Эта дорога уже находится под плотным огневым контролем ударных подразделений беспилотных систем ВС РФ, тем не менее, противник пытается постоянно укреплять защиту. Также до…
🔥97👍36👌4
Showing the 12 most recent of 17 posts we hold for @multi_XAM. 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.
Citation-graph rank — 530,619 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 3 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“MultiXAM” (@multi_XAM), 16,027 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/multi_XAM.
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.