Channel
Someone💤
@bloodiy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
429subscribers
-10 since we began measuring on 6 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001859870702 |
|---|---|
| Type | Channel |
| Username | @bloodiy |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 October 2026 |
| Last confirmed live | 21 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 21 October 2026 |
| On Telegram | t.me/bloodiy |
Topic
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 21 Oct 2026, 00:26 | 429 | -3 |
| 13 Oct 2026, 20:00 | 432 | -1 |
| 12 Oct 2026, 18:30 | 433 | no change |
| 3 Oct 2026, 08:40 | 433 | -6 |
| 17 Sept 2026, 20:59 | 439 | +2 |
| 9 Sept 2026, 23:20 | 437 | -2 |
| 6 Sept 2026, 16:47 | 439 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
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.
@General_information · 31,278
Telegram ranks this channel #14 of 69 here — alongside 68 others — read 6 September 2026
@stayeshmortzvi · 25,753
Telegram ranks this channel #18 of 72 here — alongside 71 others — read 14 September 2026
@Hamim · 26,379
Telegram ranks this channel #22 of 59 here — alongside 58 others — read 11 September 2026
@u3_k6 · 20,134
Telegram ranks this channel #51 of 80 here — alongside 79 others — read 28 September 2026
@Efsha_Bad_Tv · 22,470
Telegram ranks this channel #52 of 64 here — alongside 63 others — read 18 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 21 October 2026 — this entry's latest reading, not the date you are reading this.
“Someone💤” (@bloodiy), 429 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/bloodiy.
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.