A Ukrainian sabotage and reconnaissance group destroys three Russian soldiers during a raid on rear positions in the Donetsk region
❤63💩25👍11🔥8🥰6👻2

Channel
@ukrainosrusijoskaras
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
10,465subscribers
+43 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001626253944 |
|---|---|
| Type | Channel |
| Username | @ukrainosrusijoskaras |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/ukrainosrusijoskaras |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 17 Sept 2026, 13:56 | 10,465 | -3 |
| 14 Sept 2026, 00:41 | 10,468 | +12 |
| 12 Sept 2026, 09:19 | 10,456 | -1 |
| 10 Sept 2026, 07:18 | 10,457 | +15 |
| 7 Sept 2026, 01:40 | 10,442 | +12 |
| 2 Sept 2026, 21:38 | 10,430 | +2 |
| 1 Sept 2026, 22:55 | 10,428 | -1 |
| 31 Aug 2026, 22:06 | 10,429 | +9 |
| 31 Aug 2026, 00:15 | 10,420 | +2 |
| 29 Aug 2026, 23:13 | 10,418 | -8 |
| 29 Aug 2026, 00:25 | 10,426 | +4 |
| 28 Aug 2026, 09:30 | 10,422 | first reading |
20 posts held, back to 27 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 3 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 20 posts for this entry, the most recent from 1 November 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 18 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.
1,091 reactions across 20 posts, in 23 distinct kinds. The most used accounts for 33.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 365 | 33.5% | |
| 💩 | 134 | 12.3% | |
| 🔥 | 94 | 8.62% | |
| 👍 | 91 | 8.34% | |
| 😁 | 65 | 5.96% | |
| 😭 | 61 | 5.59% | |
| 🫡 | 55 | 5.04% | |
| 👎 | 51 | 4.67% | |
| 😢 | 42 | 3.85% | |
| 🙏 | 27 | 2.47% | |
| 🥰 | 26 | 2.38% | |
| 🥴 | 18 | 1.65% | |
| 👏 | 16 | 1.47% | |
| 😱 | 15 | 1.37% | |
| 🤬 | 9 | 0.825% | |
| 👻 | 7 | 0.642% | |
| 🤣 | 4 | 0.367% | |
| 🕊 | 3 | 0.275% | |
| 🤡 | 3 | 0.275% | |
| 🥱 | 2 | 0.183% | |
| 3 further kinds | 3 | 0.275% |
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 20 of the 20 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 1,091 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 27 January 2025 to 1 November 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.
A Ukrainian sabotage and reconnaissance group destroys three Russian soldiers during a raid on rear positions in the Donetsk region
❤63💩25👍11🔥8🥰6👻2
A Russian soldier's GoPro recorded the moment an FPV drone struck his buggy and the death of a comrade on the Donetsk front
❤31💩8👎7🫡7🥰5👍3
Ukrainian kamikaze drones destroy 90 Russian assault vehicles in the Pokrovsk area of Donetsk region
❤27👎15💩15🫡6👻3🥰3🔥2😁2
Ukrainian kamikaze drones destroy 90 ruSSians in the Pokrovsk area of Donetsk region
🔥16❤6💩6🥰4😭4⚡1
Video, posted without a caption
🔥11❤3💩3🥰3
Ukrainian sabotage and reconnaissance group destroys three Russian soldiers with small arms fire during a raid on rear positions in the Sumy region
❤9💩5
Footage of clearing the forest area in the Sumy direction from the first-person perspective of Ukrainian Special Operations Forces fighters from the "UA_REG TEAM"
❤17💩6👍4👻1
Ukrainian fiber-optic FPV drone flies to Russian soldiers hiding in a bunker in the Lyman direction
🔥16❤7💩6👏1👻1
Three Russian soldiers shoot themselves in the head with automatic rifles after failed assaults in various directions
❤22🫡19👏8😭6💩5😢1
Footage of an attack by two Russian FPV drones on a Humvee of the Kastus Kalinouski Regiment from the driver's helmet camera. A fire support group consisting of Belarusian volunteers fighting on the Ukrainian side was returning from a combat mission on the Zaporizhzhia front line. After direct hits by the enemy drone on the vehicle's windshield, and later on the side, the vehicle caught fire at full speed. Fortunate…
❤12🔥3👍1🤮1
Video, posted without a caption
❤9💩2😢2👏1
Video, posted without a caption
🥴13😭12😢7❤4👏2😁2💩1
Showing the 12 most recent of 20 posts we hold for @ukrainosrusijoskaras. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Russia vs Ukraine war footage” (@ukrainosrusijoskaras), 10,465 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ukrainosrusijoskaras.
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.