качаем скиллы потихоньку как калымага по андеру
😇14

Channel
@diealone0000
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry
333subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001815571903 |
|---|---|
| Type | Channel |
| Username | @diealone0000 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/diealone0000 |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 2 Oct 2026, 16:37 | 333 | +4 |
| 18 Sept 2026, 01:58 | 329 | -3 |
| 10 Sept 2026, 01:39 | 332 | +1 |
| 31 Aug 2026, 01:08 | 331 | +1 |
| 24 Aug 2026, 19:48 | 330 | +1 |
| 8 Aug 2026, 07:17 | 329 | no change |
| 7 Aug 2026, 14:53 | 329 | first reading |
15 posts held, back to 28 May 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 7 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.
302 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 19.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😇 | 59 | 19.5% | |
| custom 5316749499006222434 | 48 | 15.9% | |
| custom 5276023420809682364 | 40 | 13.2% | |
| custom 5353033112139894282 | 35 | 11.6% | |
| custom 5355034270547088060 | 29 | 9.60% | |
| custom 5317008000202869614 | 22 | 7.28% | |
| custom 5314801263186053647 | 20 | 6.62% | |
| custom 5317020365413711373 | 20 | 6.62% | |
| custom 5319286050856664635 | 17 | 5.63% | |
| custom 5319101096679997902 | 12 | 3.97% |
Custom emoji. 9 of the rows above are 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 14 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 302 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 28 May 2026 to 7 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.
качаем скиллы потихоньку как калымага по андеру
😇14
кароч расщепление личности по нескольким каналам потому что могу
😇8
Posted without readable text
Video, posted without a caption
😇15
из интересного, сделал старому другу наколку на лице из печального, увлекся пока били и сломал руку такшто все с кем договорился летом чета бить, возможно в августе получицп
😇22
чуваки газ или не газ эскиз родившейся на потолке в общаге ахпу под церковное пение какому нибудь кру тму чуваку набить надо пропадает за зря эскиз пиздатый смачный такое готов набить чиста за респект и смелость, главноечто бы нашелся достойный хозяин распространите!!!! пропал котенок!!! ато себе придется бить😇
custom 531702036541371137320
Video message, posted without a caption
custom 531910109667999790212
какой то лвл ап в рисунке происходит я вахуи
custom 535303311213989428235
21 др спасибо всем кто меня окружает, вдохновляет и поддерживает люблю вас вы мега крутые чуваки
custom 527602342080968236440
в ходе 5 часового пиздежа с соседом я вышел из постмодерна за сутки до своего 21 годика... все супер, было тяжело картинка фейк, выход есть может это для многих было очевидно я был очень долго там, как будто лет с 18 и какой то депрешн вайб из за этого был, смысла нет и канал хотелось удалить в последнее время, но хорошо что картинка фейк, выход есть дальше двигаемся потихоньку как калымага по андеру в метамадерн
custom 531928605085666463517
12 х 6
custom 531674949900622243422
двигаемся по андеру потихоньку как калымага фанера 27 х 37 копчение церковной свечой
custom 531674949900622243426
Showing the 12 most recent of 15 posts we hold for @diealone0000. 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.
@diealone0000 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“дай алончик” (@diealone0000), 333 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/diealone0000.
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.