Channel
@egordeathhcore
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
287subscribers
-2 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001627682715 |
|---|---|
| Type | Channel |
| Username | @egordeathhcore |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/egordeathhcore |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 17:41 | 287 | -2 |
| 31 Aug 2026, 15:08 | 289 | +1 |
| 25 Aug 2026, 05:34 | 288 | -1 |
| 17 Aug 2026, 09:24 | 289 | no change |
| 16 Aug 2026, 15:15 | 289 | first reading |
15 posts held, back to 9 June 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 15 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
251 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 21.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5348040964277543394 | 55 | 21.9% | |
| custom 5219689796531675745 | 41 | 16.3% | |
| custom 5294500430246584263 | 39 | 15.5% | |
| custom 5377762498743116673 | 33 | 13.1% | |
| custom 6033053536063851602 | 32 | 12.7% | |
| custom 5377577115069719522 | 23 | 9.16% | |
| custom 5379895190523757595 | 14 | 5.58% | |
| custom 6033081251487812808 | 14 | 5.58% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 15 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 251 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 9 June 2026 to 14 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.
Video message, posted without a caption
custom 52196897965316757454custom 52945004302465842634custom 60330812514878128084custom 53775771150697195222custom 53480409642775433941
Video message, posted without a caption
custom 53480409642775433945custom 52945004302465842633custom 53798951905237575953custom 60330535360638516023custom 53777624987431166731
Немного стилька с порога навалил
custom 537776249874311667313custom 60330535360638516027custom 60330812514878128083
Video message, posted without a caption
custom 53777624987431166735custom 52945004302465842634custom 53480409642775433944
Video message, posted without a caption
custom 52945004302465842635custom 60330535360638516024custom 53775771150697195223custom 52196897965316757451
Video message, posted without a caption
custom 53480409642775433946custom 60330535360638516026custom 52945004302465842633custom 53798951905237575951
Video, posted without a caption
custom 53775771150697195224custom 52945004302465842633custom 53798951905237575953custom 60330535360638516021
Video message, posted without a caption
custom 52196897965316757455custom 53480409642775433943custom 52945004302465842631custom 60330535360638516021
Video message, posted without a caption
custom 53480409642775433946custom 52196897965316757455custom 60330535360638516024custom 53777624987431166733custom 53775771150697195222custom 60330812514878128081
Video message, posted without a caption
custom 53777624987431166737custom 52945004302465842636custom 52196897965316757455custom 53480409642775433942custom 60330535360638516022
Я в Милане чуваки🙂
custom 53480409642775433949custom 60330812514878128086custom 52196897965316757455custom 52945004302465842631custom 53777624987431166731custom 53798951905237575951custom 60330535360638516021
Свободный эскииизз🤩 . Можно подогнать под любую часть тела🤩 . Запись на сеанс/консультацию в лс - @egordeathhcorr . ig: egordeathhcore
custom 521968979653167574513custom 52945004302465842637custom 53775771150697195227custom 53480409642775433942custom 53798951905237575951
Showing the 12 most recent of 15 posts we hold for @egordeathhcore. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“egordeathhcore” (@egordeathhcore), 287 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/egordeathhcore.
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.