Telegram RegisterThe public register of Telegram
Telegram profile photo for Руки базуки Кирилл Терешин ruki_bazyki

Channel

Руки базуки Кирилл Терешин ruki_bazyki

@ruki_bazyki

On this record: Topic · Previous handles · Growth · Engagement · Posts · Cite this entry

21subscribers

No longer on Telegram — last measured 6 September 2026

-2 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-1002737673491
TypeChannel
Username@ruki_bazyki
Created15 July 2025 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live29 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 29 September 2026
On Telegramt.me/ruki_bazyki

Topic

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Previous handles

@ruki_bazyki was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@ruki_bazyki
held 11 August 2026 – 11 August 2026

Growth

2123226 August 2026 — 23 subscribers11 August 2026 — 23 subscribers29 August 2026 — 22 subscribers6 September 2026 — 21 subscribers6 August 20266 September 2026
4 measurements spanning 31 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 21–23 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 18:5721-1
29 Aug 2026, 02:1222-1
11 Aug 2026, 11:3123no change
6 Aug 2026, 15:3923first reading

Engagement

2 posts held, back to 15 July 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 2 posts for this entry, the most recent from 15 July 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 2 most recent of 2 posts we hold for @ruki_bazyki. 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.

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 September 2026 — this entry's latest reading, not the date you are reading this.

“Руки базуки Кирилл Терешин ruki_bazyki” (@ruki_bazyki), 21 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/ruki_bazyki.

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.