![Telegram profile photo for :[🥢𝔼𝕋𝔼ℝℕ𝕀𝕋𝕐🥢]:](https://cdn.tgregister.com/av/a4/a4e0ffdd30b885683c4431fc386707866c0eb3f4b9ad65091e202f9ead5e1b1c.jpg)
Channel
@deatheternitydeath
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001442374684 |
|---|---|
| Type | Channel |
| Username | @deatheternitydeath |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/deatheternitydeath |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 06:45 | 3 | no change |
| 31 Aug 2026, 06:30 | 3 | first reading |
15 posts held, back to 22 February 2023 — 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 15 posts for this entry, the most recent from 17 August 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 31 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 3 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.
16 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 8 | 50.0% | |
| ❤ | 2 | 12.5% | |
| 🍾 | 2 | 12.5% | |
| 👏 | 1 | 6.25% | |
| 💋 | 1 | 6.25% | |
| 🕊 | 1 | 6.25% | |
| 🤔 | 1 | 6.25% |
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 8 of the 15 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 22 February 2023 to 17 August 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
ещё одно обращение к союзникам. напишите пожалуйста через — :: канал вашего кф и с кем из ваших админов у нас союз. думаю понятно выразился.
❤1🍾1🔥1
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
дорогие союзники. мы меняем канал клана. просим вас не разрывать союз. юз нашего нового канала. @RadishevskyRaidsky
🔥2🍾1💋1🤔1
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
ೋ #участник ೋ ೋ Хаос. °• •°• 1748. ❧ гей. ಇ уни. ☬ занят. ♪ @dadahaos
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
ну как-то #ᴇᴛᴇʀɴɪᴛʏꜰᴍ #видосики
🕊1
Signed безумный шляпник 𝕽𝖆𝖋𝖆𝖊𝖑 прекрасный ᶠʳ ᵈⁱˢʰᵉᅠ
ೋ #участник ೋ ೋчайок °• •°• 21 ❧би ಇпассив ☬свободна ♪ @Teaoke
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
– Репка,показывай дорогу к замку Хаула, ты-то точно не соврешь,– сказали наши дорогие странники @deatheternitydeath. а Репка привел их к замку,где они и встретились с @lostsouulls. надеемся,что их дружба будет долгой,так сказать на века!
❤1👏1🔥1
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
ೋ #участник ೋ ೋиэн°• •°• 19 ❧гей ಇуни ☬свобден. ♪ @Iol_yes
🔥1
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
›. || NEW UNI.ON . ⅄ 𖥔 @deatheternitydeath & @neezdato —— удâчнøгô нām сóюзã! (ᵔᴥᵔ)
🔥1
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
⫘⫘⫘⫘⫘⫘⫘⫘⫘⫘⫘⫘ ᴋᴧᴀн ᴨᴩиᴦᴧᴀᴄиᴧ @deatheternitydeath ʙ ʙᴇчн᧐ᴇ ᴨуᴛᴇɯᴇᴄᴛʙиᴇ @respectskiee нᴀдᴇᴇʍᴄя нᴀ д᧐ᴧᴦ᧐ᴇ ᴨуᴛᴇɯᴇᴄᴛʙиᴇ ⫘⫘⫘⫘⫘⫘⫘⫘⫘⫘⫘⫘
🔥1
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
ты конечно не веревка а я не мыло, но из нас бы вышла отличная пара.
🔥1
Signed 𝒱Милкович.ᶠʳ ᵈⁱˢʰᵉᥫ᭡
Showing the 12 most recent of 15 posts we hold for @deatheternitydeath. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“:[🥢𝔼𝕋𝔼ℝℕ𝕀𝕋𝕐🥢]:” (@deatheternitydeath), 3 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/deatheternitydeath.
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.