8 треков 2# августа

Channel
umeru #кошмары
@killmeumeru
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
59subscribers
+11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003667197007 |
|---|---|
| Type | Channel |
| Username | @killmeumeru |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/killmeumeru |
Topic
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 29 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 03:48 | 59 | +1 |
| 17 Sept 2026, 17:37 | 58 | +1 |
| 8 Sept 2026, 23:39 | 57 | +4 |
| 30 Aug 2026, 18:13 | 53 | +2 |
| 23 Aug 2026, 00:56 | 51 | +1 |
| 15 Aug 2026, 07:36 | 50 | +2 |
| 10 Aug 2026, 12:46 | 48 | no change |
| 6 Aug 2026, 19:45 | 48 | first reading |
Engagement
20 posts held, back to 23 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 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 14s
- Average length
- 14s
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.
Reaction mix
15 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 5 | 33.3% | |
| 🔥 | 4 | 26.7% | |
| 🐳 | 3 | 20.0% | |
| 🕊 | 2 | 13.3% | |
| ⚡ | 1 | 6.67% |
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 7 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 15 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 23 July 2026 to 9 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.
Recent posts
bllck - единым mix: bllck cover: bllck слушать: https://soundcloud.com/bllck001/edinim?si=777151da1ca94cf08b6709ad445bba52&utm_source=clipboard&utm_medium=text&utm_campaign=social_sharing
Photo, posted without a caption
❤🔥1
блюй скоро
File, posted without a caption
umeru, lilithh, bllck - ОНА АФИГЕННАЯ КИБЕРШАЛАВА ОНА АФИГЕННАЯ CYBER ШАЛАВА на СК слушать: https://soundcloud.com/umeru/shalava
❤🔥3⚡1🔥1
ща трек будет
Photo, posted without a caption
человек переплыл океан и снял сниппет, чтобы обосраться в луже...
umreu, bllck - блюй #БЛЮЙ В АВГУСТЕ
Video message, posted without a caption
завтра в 17:00, вас ждёт некий прайм
🔥3
Showing the 12 most recent of 20 posts we hold for @killmeumeru. 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.
Forward network
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.
Mentions
Named by 28 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@bllckszn · 1733 postsдемаксимка #кошмары
@d5m5ks5mk5 · 673 postsgoodnightreze||#кошмары||
@goodnightreze · 323 postscry07
@ccry07 · 2932 postspariah // par1ah #кошмары
@Iampar1ah · 1982 postsдневник плаксы лили
@liliadura · 992 postsебашим #кошмары продакшн
@salt2production · 232 postsAfaan
@af44n44 · 1,5211 post8D AUDIO
@eightdimensional · 611 postblazze?.chr / furrydoki
@FCKMEblaZze · 1,2651 post#кошмары
@hashnightmares · 401 postlilithh.chr
@lilithinchains · 4321 postлиля водкина
@lilivodka · 521 postlqmiexd #кошмары
@lqmiexd · 701 postмилим?
@milimuenava · 261 postмайндфлеер #кошмары
@mindflayerstas · 121 postвендсук #MONEYMAMMYGANG
@moaikamni · 801 post#кошмары изгоя
@pariahshit · 471 postпосос года #кошмары
@pososoftheyear · 281 post.
@s3r3nada · 11 post@shoegazzzebaby
@shoegazzzebaby · 21 posttenomori.chr
@tenomori · 1151 postяблочные щитпосты / #SHRILANKA
@yablochkocor · 791 postzeexiddddd/kirumee #кошмары
@zeexidiee · 301 post
Names
Channels on the register whose handles appear in this channel's posts.
@bllckszn · 1733 postslilithh.chr
@lilithinchains · 4323 postsblazze?.chr / furrydoki
@FCKMEblaZze · 1,2652 postst.me/bllckszn
@bllckurdie · 21 postcry07
@ccry07 · 2931 postddоki // lаbel ♬
@ddoki_label · 2461 post𝚏𝚕𝚞𝚔𝚜𝚊.𝚌𝚑𝚛 // 𝚍𝚍𝚘𝚔𝚒
@fluksa7 · 7591 postVanHellsing
@markusdavies · 661 post.
@s3r3nada · 11 post@shoegazzzebaby
@shoegazzzebaby · 21 postмусорка хиспа \ #моральныйурод
@splitingheadache · 3411 post1O
@TENTmint · 1241 postthebubblesfan45
@thebubblesfan45 · 1871 postВинсерааа🌺
@vinceragghh · 261 postweakkidd.chr
@weakkiddd · 1261 post
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.
Cite this entry
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“umeru #кошмары” (@killmeumeru), 59 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/killmeumeru.
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.