肉搏战中活下来的俄军士兵
❤13👍6👎4😁1

Channel
@arms08
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
1,012subscribers
-36 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001851863656 |
|---|---|
| Type | Channel |
| Username | @arms08 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/arms08 |
International news — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 6 Oct 2026, 12:00 | 1,012 | -10 |
| 29 Sept 2026, 20:37 | 1,022 | -6 |
| 16 Sept 2026, 08:02 | 1,028 | -2 |
| 12 Sept 2026, 07:58 | 1,030 | -2 |
| 8 Sept 2026, 09:57 | 1,032 | -1 |
| 3 Sept 2026, 13:00 | 1,033 | -3 |
| 30 Aug 2026, 23:46 | 1,036 | -1 |
| 28 Aug 2026, 01:14 | 1,037 | -2 |
| 25 Aug 2026, 02:38 | 1,039 | -4 |
| 21 Aug 2026, 09:23 | 1,043 | -1 |
| 18 Aug 2026, 04:53 | 1,044 | -2 |
| 14 Aug 2026, 21:55 | 1,046 | -1 |
| 11 Aug 2026, 10:53 | 1,047 | -1 |
| 8 Aug 2026, 00:19 | 1,048 | no change |
| 7 Aug 2026, 14:28 | 1,048 | first reading |
11 posts held, back to 7 January 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 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 11 posts for this entry, the most recent from 9 January 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 8 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.
37 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 48.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 18 | 48.6% | |
| 👍 | 14 | 37.8% | |
| 👎 | 4 | 10.8% | |
| 😁 | 1 | 2.70% |
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 7 of the 11 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 37 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 7 January 2025 to 9 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
肉搏战中活下来的俄军士兵
❤13👍6👎4😁1
俄乌肉搏战中乌军士兵随身摄像机的记录
👍4
空拍机画面
❤1
俄军士兵和乌军士兵相遇,双方扭打在一起,俄军士兵掏出匕首重伤了乌军士兵,乌军士兵用手榴弹自杀
❤2
俄军的强大火力覆盖
SSO 宣布在库尔什奇纳 (Kurshchyna) 击毙数名朝鲜士兵 乌克兰武装部队特种作战部队第 8 团的作战人员摧毁了 13 名朝鲜军人。 在执行特别行动期间,SSO士兵在一场枪战中“杀死”了五名朝鲜士兵,并在无人机的帮助下“杀死”了八名朝鲜士兵。 战斗结束后,SSO 操作员检查了朝鲜士兵的尸体及其个人文件。其中一人持有带有准直瞄准镜的突击步枪、中俄广播电台“阿扎尔特”和无人机探测器,还有一张与普通军人身份证不同的身份证件。发现的东西可能表明他是一名军官。 除其他外,这名朝鲜军人还随身携带了一份入党申请书
👍4❤2
库尔斯克地区,乌军开着弹药耗尽的史崔克装甲车碾压俄军士兵
三名投降的乌军士兵遭到俄军行刑式处决,从后脑开枪打死
俄军在库尔斯克推进,士兵拔掉乌军之前安插的国旗
扎波罗热地区,无人机空战
哈尔科夫州北部,乌军第三突击旅的士兵攻占俄军战壕
Showing the 11 most recent of 11 posts we hold for @arms08. 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“俄乌战争军武盘点” (@arms08), 1,012 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/arms08.
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.