🥀
custom 521094562107414899811custom 52111097489543995796custom 52111232566265439535

Channel
@blackbloodds
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
437subscribers
-17 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002163773660 |
|---|---|
| Type | Channel |
| Username | @blackbloodds |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/blackbloodds |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 |
|---|---|---|
| 12 Sept 2026, 17:55 | 437 | -5 |
| 4 Sept 2026, 10:20 | 442 | -1 |
| 28 Aug 2026, 05:35 | 443 | -1 |
| 22 Aug 2026, 00:24 | 444 | -3 |
| 15 Aug 2026, 00:35 | 447 | -7 |
| 8 Aug 2026, 16:13 | 454 | no change |
| 8 Aug 2026, 13:01 | 454 | first reading |
12 posts held, back to 29 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 12 posts for this entry, the most recent from 6 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.
339 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 41.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5210945621074148998 | 139 | 41.0% | |
| custom 5211123256626543953 | 103 | 30.4% | |
| custom 5211109748954399579 | 97 | 28.6% |
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 12 of the 12 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 339 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 29 July 2026 to 6 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 521094562107414899811custom 52111097489543995796custom 52111232566265439535
вот сука,хоть один нахуй раз,все может быть хорошо??
custom 521110974895439957913custom 52109456210741489985custom 52111232566265439535
слабенькие вы чет,вас 450 типов а реакций еле как 20 набирается🥀
custom 521094562107414899819custom 52111232566265439534custom 52111097489543995793
Photo, posted without a caption
custom 521094562107414899826custom 521112325662654395317custom 521110974895439957916
by @amnezzia_official
custom 521112325662654395315custom 52111097489543995798custom 52109456210741489986
I know you want to meet eye to eye, but I'm not sure if I want the same.
custom 521110974895439957916custom 52109456210741489989custom 52111232566265439537
Photo, posted without a caption
custom 521112325662654395313custom 52111097489543995797custom 52109456210741489985
галямит
custom 521094562107414899816custom 521112325662654395310custom 52111097489543995799
второй час на кента смотрю,а мой крабсбургер еще не готов
custom 521094562107414899810custom 52111097489543995793custom 52111232566265439533
Photo, posted without a caption
custom 521094562107414899813custom 52111232566265439534custom 52111097489543995793
Video, posted without a caption
custom 521094562107414899812custom 52111232566265439535custom 52111097489543995794
i’m back сука
custom 521112325662654395315custom 52111097489543995799custom 52109456210741489987
Showing the 12 most recent of 12 posts we hold for @blackbloodds. 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“b1ackblood” (@blackbloodds), 437 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/blackbloodds.
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.