я считаю леруса нахуй надо
Signed 69

Channel
@KillsZooma
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
17subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002216834969 |
|---|---|
| Type | Channel |
| Username | @KillsZooma |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 9 October 2026 |
| On Telegram | t.me/KillsZooma |
Gaming — 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 52% 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 |
|---|---|---|
| 7 Sept 2026, 01:54 | 17 | -1 |
| 11 Aug 2026, 18:31 | 18 | no change |
| 7 Aug 2026, 13:01 | 18 | first reading |
20 posts held, back to 12 April 2025 — 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 30 July 2025. An engagement rate over an empty window would be a number about nothing.
я считаю леруса нахуй надо
Signed 69
когда не делали
Signed 69
Так же ща идет конкурс
Signed 69
Можете подписаться я там за 2 дня на стримах разыграл тысяч 15 мейби 20
Signed 69
https://t.me/+zv6TcXnShRNkZTI1
Signed 69
канал мертвый я его купил
Signed 69
так здарова паарни
Signed 69
@official_lerus
Signed Lerus
оке
Signed Lerus
Нету
Signed cvsxr
займи 5 уе пж
Signed Lerus
эм...
Signed Lerus
Showing the 12 most recent of 20 posts we hold for @KillsZooma. 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.
@KillsZooma named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Kill ZOOMA DRAGON” (@KillsZooma), 17 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/KillsZooma.
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.