Channel
@ucrania_guerra_muerto
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,566subscribers
+128 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001577262007 |
|---|---|
| Type | Channel |
| Username | @ucrania_guerra_muerto |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/ucrania_guerra_muerto |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 27 Sept 2026, 04:16 | 3,566 | +58 |
| 18 Sept 2026, 02:40 | 3,508 | +14 |
| 13 Sept 2026, 22:37 | 3,494 | +12 |
| 9 Sept 2026, 19:40 | 3,482 | +25 |
| 4 Sept 2026, 06:15 | 3,457 | +5 |
| 1 Sept 2026, 00:48 | 3,452 | +14 |
| 28 Aug 2026, 14:24 | 3,438 | no change |
| 28 Aug 2026, 09:30 | 3,438 | first reading |
9 posts held, back to 18 August 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 9 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 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.
14 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 4 | 28.6% | |
| ❤ | 3 | 21.4% | |
| 🍾 | 2 | 14.3% | |
| 🤮 | 2 | 14.3% | |
| 🥰 | 2 | 14.3% | |
| 🤣 | 1 | 7.14% |
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 9 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 18 August 2026 to 27 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.
In Saint Petersburg, a Russian army lieutenant colonel died in a car explosion. A homemade explosive device detonated when the car started moving. The military officer and his wife were inside the vehicle. The husband died at the scene, while his wife survived and is in intensive care.
🍾2🥰1
18+ People are jumping out of the windows of a shopping center in Lozova that was destroyed by a Russian strike. Later, to increase the number of victims, the russians delivered a second strike.
🤮1
Our drones are striking Wildberries — after the attack, one of the largest sorting centers in the Tambov region was destroyed by fire. Subscribe to me
❤2
🔥 WITHOUT A CAR, WE CANNOT SURVIVE! 1st Assault Battalion of the 225th Separate Assault Regiment. 📍 Zaporizhzhia direction. The defenders carry out combat missions every day. After one of these missions, the car burned to the ground. Without a car in this direction, it is impossible. We cannot deliver what is needed. We cannot deliver ammunition. We cannot conduct rotation. We cannot evacuate the wounded. PayPal htt…
🤮1
18+ Russian degenerates published a video of them hitting a civilian on a bicycle with an FPV drone near Kramatorsk. This is genocide. It is exactly what the Russians are committing.
🤬3
FATUM strikes the enemy's front line and rear The pilots of FATUM of the 60th Separate Mechanized Brigade neutralized enemy infantry, a BTR-82A, a cannon, an MLRS, an equipment depot, and a drone lying in ambush. Subscribe to me
❗In the Russian Federation, under Putin's fascist regime, a concert was announced for Kanye West, a rapper who is a supporter of Hitler and fascism. Subscribe to me
❤1
Our pilots on Su-27s are driving out enemy scum from the buildings in Kostyantynivka. Subscribe to me
russian bastards killed 10 people in Pechenihy on Kharkivshchyna. Another 8 people were injured. As a result of a missile strike, private houses and civilian infrastructure were damaged.
🤣1🤬1🥰1
Showing the 9 most recent of 9 posts we hold for @ucrania_guerra_muerto. 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.
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.
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.
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 1 seed channel's Telegram-generated recommendation list 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“War in ukraina🔞” (@ucrania_guerra_muerto), 3,566 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/ucrania_guerra_muerto.
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.