Channel
@ruchotp9lkma
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
24subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003274951277 |
|---|---|
| Type | Channel |
| Username | @ruchotp9lkma |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 30 September 2026 |
| Measurements held | 7 |
| On Telegram | t.me/ruchotp9lkma |
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 51% 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.
@ruchotp9lkma 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Sept 2026, 04:22 | 24 | no change |
| 30 Sept 2026, 03:47 | 24 | no change |
| 10 Sept 2026, 06:20 | 24 | +1 |
| 31 Aug 2026, 19:35 | 23 | -3 |
| 23 Aug 2026, 23:33 | 26 | +2 |
| 11 Aug 2026, 10:31 | 24 | no change |
| 7 Aug 2026, 17:08 | 24 | first reading |
40 posts held, back to 13 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 2 pages of Telegram’s post history, 20 posts per page.
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 22 September 2026 |
|---|---|
| Posts held | 40 (13 May 2026 – 22 September 2026) |
| Views total | 1,427 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Sept 2026, 04: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.
Lifetime counters from Telegram’s own channel header, read 30 September 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.
🔥Я @p9lkma назначаю заместителем @garant_rab до 1500₽. Сроком на неделю. В дальнейшем ручаюсь до 1000р ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
🔥Я @p9lkma ручаюсь за @chsvshny до 700₽. Сроком до первого скама. ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
🔥Я @p9lkma назначаю гарантом чата @mandew до 100$. Сроком до первого скама. ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
🔥Я @p9lkma ручаюсь за @goldsfarm до 1000₽. Сроком до первого скама. ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
🔥Я @p9lkma ручаюсь за @Razorbill_0 до 500₽. Сроком до первого скама. ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
🔥Я @p9lkma ручаюсь за @Mopdox до 600₽. Сроком до первого скама. ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
🔥Я @p9lkma ручаюсь за @molodoj_gg до 1000₽. Сроком до первого скама. ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
Снят, скам
🔥 / @Yes_Skam1 - успешно окончил пост заместителя. 🫀 / В дальнейшем ручаюсь за данную личность при моём одобрении на сумму до 1000₽. ⚠️ Перед сделкой уточняйте у меня @p9lkma ручаюсь я или нет и ждите моего ответа, если не дождетесь ответа и пойдете на его доверие, то, увы, я не буду обязан вам что либо вернуть.
Снят, скам
Псж
🔥Я @p9lkma ручаюсь за @usedp2p до 800₽. Сроком до первого скама. ‼️Обязательно перед сделкой уточняйте в лс. В случае того если вы не дождались моего ответа либо не спросили у меня, я не буду обязан вам что-либо возвращать. Страховка от сноса: ❌
Showing the 12 most recent of 40 posts we hold for @ruchotp9lkma. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 30 September 2026 — this entry's latest reading, not the date you are reading this.
“Ручения от Пикмы” (@ruchotp9lkma), 24 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/ruchotp9lkma.
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.