Channel
Все сливы @yanamsfblog
@yanamsfblog
On this record: Topic · Growth · Engagement · Cite this entry
1,317subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001644139193 |
|---|---|
| Type | Channel |
| Username | @yanamsfblog |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/yanamsfblog |
Topic
Hacking & security — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 38% 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 |
|---|---|---|
| 6 Oct 2026, 05:57 | 1,317 | -2 |
| 1 Oct 2026, 17:25 | 1,319 | no change |
| 29 Sept 2026, 07:02 | 1,319 | -2 |
| 12 Sept 2026, 02:39 | 1,321 | -2 |
| 7 Sept 2026, 15:18 | 1,323 | -2 |
| 2 Sept 2026, 17:55 | 1,325 | -2 |
| 30 Aug 2026, 19:46 | 1,327 | -5 |
| 28 Aug 2026, 00:12 | 1,332 | -2 |
| 25 Aug 2026, 04:04 | 1,334 | -1 |
| 15 Aug 2026, 04:48 | 1,335 | +2 |
| 11 Aug 2026, 18:12 | 1,333 | -1 |
| 8 Aug 2026, 08:37 | 1,334 | -2 |
| 7 Aug 2026, 13:42 | 1,336 | 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“Все сливы @yanamsfblog” (@yanamsfblog), 1,317 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/yanamsfblog.
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.