Channel
@dekma_vulf
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
16,516subscribers
+61 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001665102694 |
|---|---|
| Type | Channel |
| Username | @dekma_vulf |
| Created | 11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/dekma_vulf |
Music — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 17 Sept 2026, 09:16 | 16,516 | -10 |
| 15 Sept 2026, 11:42 | 16,526 | +2 |
| 13 Sept 2026, 20:21 | 16,524 | +1 |
| 12 Sept 2026, 06:00 | 16,523 | -8 |
| 9 Sept 2026, 20:55 | 16,531 | +20 |
| 6 Sept 2026, 11:37 | 16,511 | +20 |
| 4 Sept 2026, 02:38 | 16,491 | +22 |
| 2 Sept 2026, 13:23 | 16,469 | -2 |
| 1 Sept 2026, 15:23 | 16,471 | -9 |
| 31 Aug 2026, 14:44 | 16,480 | -5 |
| 30 Aug 2026, 11:37 | 16,485 | +2 |
| 29 Aug 2026, 10:27 | 16,483 | +1 |
| 28 Aug 2026, 06:53 | 16,482 | +1 |
| 27 Aug 2026, 03:42 | 16,481 | +1 |
| 26 Aug 2026, 06:05 | 16,480 | -3 |
| 25 Aug 2026, 04:23 | 16,483 | -5 |
| 24 Aug 2026, 01:09 | 16,488 | +5 |
| 22 Aug 2026, 07:17 | 16,483 | -3 |
| 20 Aug 2026, 22:56 | 16,486 | -5 |
| 19 Aug 2026, 20:47 | 16,491 | first reading |
28 posts held, back to 16 July 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 54 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 28 (16 July 2026 – 2 September 2026) |
| Views total | 95,850 |
| Reactions total | 6,553 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 09:49 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
26,435 reactions across 28 posts, in 3 distinct kinds. The most used accounts for 53.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5449448144318247733 | 14,251 | 53.9% | |
| custom 5449807422627525218 | 6,690 | 25.3% | |
| custom 5449714458060402327 | 5,494 | 20.8% |
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 28 of the 28 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 26,435 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 28 most recent posts we hold, published 16 July 2026 to 2 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dekma_vulf. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 28 most recent posts we hold for this entry, published 16 July 2026 to 2 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
зато теперь у вас есть повод ознакомиться с визуалами к альбомам, я знал что рано или поздно оно реально пригодится https://youtube.com/playlist?list=PL47SDabD1tJZ7VHnV4e-PaN3iAbCmU5R_&si=PAVHSXvVjJO3xWav
custom 5449448144318247733313custom 5449714458060402327106custom 544980742262752521872
почти все треки агонии исчезли со спотифая бить тревогу не надо, возникли какие то проблемы на стороне дистрибьютора, официального ответа пока не было сам в ахуе, но ниче поделать не могу, сидим ждем информации, думаю (надеюсь) за пару дней все разрулится
custom 5449807422627525218579custom 5449714458060402327249custom 5449448144318247733148
File, posted without a caption
custom 5449807422627525218189custom 544971445806040232775custom 544944814431824773350
Video, posted without a caption
custom 5449714458060402327408custom 5449807422627525218103custom 544944814431824773397
это пипец нахуй а не трек
custom 5449448144318247733557custom 5449714458060402327170custom 5449807422627525218127
dekma — касания болезненны produced by yoshi1mura artwork by беомуз special thanks to @alicevocalcoach эта ситуация оставит отпечатки band.link/it_hurts
custom 5449714458060402327608custom 5449448144318247733167custom 5449807422627525218140
трек в полночь я спал гдето три часа вот бы дожить
custom 5449448144318247733766custom 5449714458060402327212custom 5449807422627525218158
@yoshi1muraxd гений кстати
custom 5449448144318247733372custom 544971445806040232799custom 544980742262752521881
все таки я выбрал лирический душераздирающий пиздец в пятницу сниппета не будет, я хз как показывать отрывок от настолько цельной композиции, наверное максимум на бусти чето залью
custom 5449807422627525218472custom 5449714458060402327121custom 5449448144318247733114
warykid — этаж all я bnd.lc/etazh
custom 5449807422627525218290custom 544971445806040232793custom 544944814431824773372
канье вест не приедет в питер вместо него мы с штрихкодом выйдем на сцену и будем час исполнять слендермена и еще час фристайлить вторую часть лохам в вип ложе за 160к
custom 54494481443182477331,450custom 5449714458060402327321custom 5449807422627525218285
я сотворил страшное
custom 54494481443182477331,510custom 5449714458060402327474custom 5449807422627525218337
Showing the 12 most recent of 28 posts we hold for @dekma_vulf. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 23 registered channels — 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.
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 2 seed channels' Telegram-generated recommendation lists 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“dekma из агонии” (@dekma_vulf), 16,516 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/dekma_vulf.
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.