константин прости нас
custom 53525985215790712397custom 53120491469270185045custom 53978725578252140603custom 52918979205833813422
Signed endless spring

Channel
@iwill_diee
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
8,477subscribers
+2,907 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002878725707 |
|---|---|
| Type | Channel |
| Username | @iwill_diee |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/iwill_diee |
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 16 Sept 2026, 20:59 | 8,477 | +200 |
| 13 Sept 2026, 08:56 | 8,277 | -53 |
| 9 Sept 2026, 17:41 | 8,330 | -298 |
| 4 Sept 2026, 06:21 | 8,628 | +6,847 |
| 31 Aug 2026, 10:35 | 1,781 | +181 |
| 28 Aug 2026, 09:43 | 1,600 | -24 |
| 24 Aug 2026, 23:24 | 1,624 | -4,923 |
| 21 Aug 2026, 00:22 | 6,547 | +977 |
| 20 Aug 2026, 00:45 | 5,570 | first reading |
20 posts held, back to 16 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 20 posts for this entry, the most recent from 18 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.
124 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 23.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5354828855146211053 | 29 | 23.4% | |
| custom 5312049146927018504 | 24 | 19.4% | |
| custom 5352598521579071239 | 17 | 13.7% | |
| custom 5291897920583381342 | 16 | 12.9% | |
| custom 5408863632538752072 | 14 | 11.3% | |
| custom 5355036259116935584 | 10 | 8.06% | |
| custom 5397872557825214060 | 9 | 7.26% | |
| custom 5312364453361121127 | 2 | 1.61% | |
| custom 5398094474490430080 | 1 | 0.806% | |
| custom 5398123053202817214 | 1 | 0.806% | |
| custom 5400280690153504677 | 1 | 0.806% |
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 9 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 124 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 16 August 2026 to 18 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.
константин прости нас
custom 53525985215790712397custom 53120491469270185045custom 53978725578252140603custom 52918979205833813422
Signed endless spring
девочки у меня щас хуй стоит)))
custom 54088636325387520729custom 53120491469270185043custom 53980944744904300801custom 54002806901535046771
Signed 1
почему меня не жалеют😢
custom 53525985215790712399custom 53120491469270185045custom 53548288551462110534
Signed endless spring
стабильно несколько раз в неделю я подхватываю паничку и изрезаю себе все ноги
custom 535482885514621105310custom 53120491469270185045custom 53550362591169355844custom 53525985215790712391
Signed endless spring
о там мой вбаненый ак
Signed endless spring
хаахвхызвххы
Signed obeskrovIen
кто может выступить моим опекуном кому больше 18 лет для верификации в роблоксе✌️
Signed obeskrovIen
стандоферы залетайте ✌️
custom 53550362591169355845custom 52918979205833813421custom 53978725578252140601
Signed obeskrovIen
мне очень страшно пришлось уйти из россии деля не трогай меня пж
custom 529189792058338134210custom 53978725578252140605custom 53120491469270185044custom 54088636325387520722custom 53981230532028172141
Signed obeskrovIen
Photo, posted without a caption
Signed obeskrovIen
здравствуйте дорогие подписчики, седня мы попали в список «топ осинтера мира». Я очень боюсь то что нас с @iwavo задоксят или обольют в людном месте. Поэтому мы хотим публично извиниться перед ней…
Signed endless spring
ссылка на фрики редана https://t.me/+k-XGUNYsK3RjOWQ0
Signed obeskrovIen
Showing the 12 most recent of 20 posts we hold for @iwill_diee. 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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“опиаты вредят здоровью” (@iwill_diee), 8,477 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/iwill_diee.
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.