Channel
@ruchenik
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002420601235 |
|---|---|
| Type | Channel |
| Username | @ruchenik |
| Description | Правила для ручеников: @RuchRulesGG |
| Created | 4 November 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ruchenik |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:16 | 6 | no change |
| 12 Aug 2026, 03:01 | 6 | first reading |
10 posts held, back to 4 November 2024 — 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 pageof 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 10 posts for this entry, the most recent from 28 December 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
3 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 2 | 66.7% | |
| 👍 | 1 | 33.3% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 4 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 4 November 2024 to 28 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Я @Soldat ручаюсь за @delauu на сумму до 1000₽ 🕞Срок ручения до 1-го скама 💼Уточнить ручение 🔎Проверка на актуальность поста ✅5091689558 Если вы пошли на доверие и не дождались моего ответа по поводу ручения, вы останетесь без возврата средств в случае скама‼️
@Shamsha_mini - Снят. Скам.
Я @GG_Soldier ручаюсь за @h9tsu на сумму до 500💸 🕞Срок ручения до 1-го скама Обязательно уточняйте у меня в ЛС ручаюсь ли я за данного человека ‼️ ✅5852830819 Если вы пошли на доверие и не дождались моего ответа по поводу ручения, вы останетесь без возврата средств в случае скама‼️ Проверить не скамнулся ли рученец @ruchSoldata
Не ручаюсь за данную личность!
👍1
Я @GG_Soldier ручаюсь за @Numbro_FIZ на сумму до 300💸 🕞Срок ручения до 1-го скама Обязательно уточняйте у меня в ЛС ручаюсь ли я за данного человека ‼️ ✅7686000067 Если вы пошли на доверие и не дождались моего ответа по поводу ручения, вы останетесь без возврата средств в случае скама‼️ Проверить не скамнулся ли рученец @ruchSoldata
Я @GG_Soldier ручаюсь за @AlexanderMakidonsky на сумму до 1000💸 🕞Срок ручения до 1-го скама Обязательно уточняйте у меня в ЛС ручаюсь ли я за данного человека ‼️ ✅7063790778 Если вы пошли на доверие и не дождались моего ответа по поводу ручения, вы останетесь без возврата средств в случае скама‼️ Проверить не скамнулся ли рученец @ruchSoldata
Снят. Ушел ПСЖ!
Снят. Скам.
👎2
Здесь будут все личности за которых буду ручаться я @GG_Soldier Перед приобретением данной услуги ознакомьтесь с правилами @RuchRulesGG Цена данной услуги 150🛍 То есть, сумма на которую вы хотите ручение + 50% Условно вы хотите ручение на 1000₽ 1000₽ + 50% = 1500₽ Минимальная сумма ручения 500💸
Channel created
Showing the 10 most recent of 10 posts we hold for @ruchenik. 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.
Named by 1 registered channel — 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.
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.
@ruchenik named 3 handles 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Ручения от GG_Soldier” (@ruchenik), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ruchenik.
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.