👤//– Я @vorknu назначаю: @drannuy рученцем. 🛡 | Сумма доверия: 500₽. 🕔 | Сроком: До первого скама. 🔎/ Перед проведением сделки: - Заход в чат уточнения ручений. - Уточнение ручения по образцу. - В случае скама без уточнения ручения я не буду обязан возместить ущерб пострадавшему.

Channel
Руч за @drannuy
@ruchzadrannuy
On this record: Growth · Engagement · Posts · Citations · Cite this entry
3subscribers
+1 since we began measuring on 18 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004227063175 |
|---|---|
| Type | Channel |
| Username | @ruchzadrannuy |
| Created | 30 May 2026 — measured — dated from the channel’s first post |
| First recorded | 18 October 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 19 October 2026 |
| On Telegram | t.me/ruchzadrannuy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Oct 2026, 16:05 | 3 | +1 |
| 18 Oct 2026, 18:22 | 2 | first reading |
Engagement
14 posts held, back to 30 May 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.
- ERR · 30 days
- 2766.7%
- avg views ÷ 3 subscribers
- Avg views / post
- 83.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 14 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 30 September 2026 |
|---|---|
| Posts held | 14 (30 May 2026 – 30 September 2026) |
| Views total | 166 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Oct 2026, 18:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
🔉—| Я - @sskyynet нанял рученца @drannuy 💰- На сумму: до 1500₽ 🕘 - На срок: 06.10.2026 Обязательно перед сделкой уточняйте в чате и ждите моего ответа. В случае того если вы не дождались моего ответа, я не буду обязан вам что-либо возмещать ➡️Купить ручение — @sskyynet
🔖 = | Я @Valigonov назначаю @drannuy на должность гарантом сетки «Alyaska» 🪙 | Суммой до 50$ 📄 | Страховка от сноса 🗃 | Актуальность поста 📌| Ручение уточнять обязательно, без уточнения ручения - не будет возврата ваших средств. Правила - RULES 📤= | Уточнить ручение 📥= | Как стать рученцем
👤| Я — @nagg1kww — нанял @drannuy на пост гаранта чата. 🪙| Сумма доверия: до 50$ ⏰| Срок: до 1-ого скама. 🗂| Страховка от сноса: отсутствует. 👁| Проверить актуальность ручения. ‼️Перед сделкой обязательно уточняйте ручение в чате (нажми). Если Вы не уточнили ручение, то Я не буду обязан что-либо Вам возмещать. 💎| Купить услугу — @pricenagg1kww
📣 Я @Bar1ga нанял рученика @drannuy суммой до 500 ₽. Сроком до первого скама. ❤️Перед сделкой уточняйте актуальность ручения у меня - @Bar1ga , если вы не уточнили ручение перед сделкой , то увы я не буду обязан вам что либо возвращать.
👤| Я — @nagg1kww — нанял @drannuy на пост рученика. 🪙| Сумма доверия: до 777₽ ⏰| Срок: до 1-ого скама. 🗂| Страховка от сноса: отсутствует. 👁| Проверить актуальность ручения. ‼️Перед сделкой обязательно уточняйте ручение в чате (нажми). Если Вы не уточнили ручение, то Я не буду обязан что-либо Вам возмещать. 💎| Купить услугу — @pricenagg1kww
👤| Я @szqwunk_tag нанял рученца @drannuy ✅| на сумму - 555₽ сроком до первого скама. страховка от сноса - нет 📎| актуальность поста ❗️| перед сделкой уточняйте тут ручаюсь я или нет, если пойдёте на доверие я ничего не буду обязан вам вернуть
Channel photo removed
💎Я, @sytener нанял рученца: @drannuy 🖥Информация о рученце и его привилегиях: — имеет доверие до 500₽ — ручение действует до первого скама. — страховка от сноса отсутствует. ❗️Важно, перед сделкой уточнить ручение за данного человека у @sytener, чтобы я в случае скама возместил вам средства и снял с должности данную личность (в ином случае возврат средств невозможен)❗️
Я @KPACOTA_YBILA ручаюсь за @drannuy на сумму до 500 рублей до первого скама ⚠️ Перед сделкой уточняйте у меня @KPACOTA_YBILA ручаюсь я или нет и ждите моего ответа, если не дождетесь ответа и пойдете на его доверие, то увы я не буду обязан вам что-то вернуть.
👤-// Я, @tagswagg, взял @drannuy на должность рученца. 💰-// На сумму: до 500₽ 🕔-// На срок: до первого скама ⛓-// Страховка от сноса: Отсутствует 💬-// Для уточнения ручения: - зайти в лс со мной. - уточнить ручение по образцу: @tagswagg руч за @тег на "сумма" ? "Суть сделки". ❗️-// Важно!, -| Если вы не уточнили ручение и вас заскамил мой рученец - Я не буду обязан вам ничего возвращать. -| Если вас заскамил мой руче…
Я @Yes_Skam1 ручаюсь за @drannuy на сумму до 777 рублей до первого скама ⚠️ Перед сделкой уточняйте у меня @Yes_Skam1 ручаюсь я или нет и ждите моего ответа, если не дождетесь ответа и пойдете на его доверие, то увы я не буду обязан вам что-то вернуть.
Showing the 12 most recent of 14 posts we hold for @ruchzadrannuy. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
@nagg1kwwruch · 92 postsРучения от YUMi
@Ruch_YUMi · 11 postРучение от @Valigonov
@VlgRuchenci · 691 postРучения от: @tagswagg
@puppetruch · 81 postРуч от @sytener
@ruch_ot_menya · 31 postРучения от чапы
@rucheniechapmana · 81 postКанал ручей Андрюшки
@rucheniki_Andruyshki · 211 postРучения от Hayzer’a
@ruchhayzera · 1,2721 postКанал ручений
@ruchszqwunk · 71 postКанал ручений
@rychotdeska · 21 post
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 2 registered channels — 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.
@nagg1kwwruch · 92 postsAlyaska сетка
@Alyaska_setka · 631 postAdapter 𝘋𝘦𝘢𝘤𝘰𝘯𝘴
@deaconssss · 431 postЧат Ручений переходник
@HayzeRchr · 1321 postПереезд
@hayzerprise · 61 postПереезд
@hzrpravila · 61 postРучения от Hayzer’a
@ruchhayzera · 1,2721 postКанал ручений
@ruchszqwunk · 71 postЧат Valigonov
@ValigonovChat · 5471 postПрайс услуг - @Valigonov
@ValigonovPrice · 1661 postПравила @Valigonov
@ValigonovRules · 121 postРучение от @Valigonov
@VlgRuchenci · 691 post
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.
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 19 October 2026 — this entry's latest reading, not the date you are reading this.
“Руч за @drannuy” (@ruchzadrannuy), 3 subscribers as measured 19 October 2026. Telegram Register, tgregister.com/channel/ruchzadrannuy.
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.