Telegram RegisterThe public register of Telegram
Telegram profile photo for Ручения за Нагиева

Channel

Ручения за Нагиева

@ruchzanagieva

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003232043504
TypeChannel
Username@ruchzanagieva
Created9 November 2025 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 September 2026
Measurements held2
On Telegramt.me/ruchzanagieva

Growth

27 August 2026 — 2 subscribers13 August 2026 — 2 subscribers7 August 202613 August 2026
2 measurements spanning 6 days. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 22:502no change
7 Aug 2026, 20:172first reading

Engagement

10 posts held, back to 9 November 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 10 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
8
Links
5

Lifetime counters from Telegram’s own channel header, read 13 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.

Recent posts

7 Aug 2026, 21:10 UTC33 viewsread 13 August 2026
Forwarded from @W1ar4ik_RuchPhoto

❄️| Я @W1ar4ik нанял рученца — @nagg1kww ❤| ручаюсь за данную личность на сумму в 1500₽ — сроком: до первого скама. ⚠️|Обязательно перед сделкой уточняйте ручение в чате ручей - Chat_Ruch, без уточнения, или без моего ответа, возврата не будет в случае скама. ⌛Страховка от сноса? - отсутствует |❌|

7 Aug 2026, 20:31 UTC24 viewsread 13 August 2026
Forwarded from @VlgRuchenciPhoto

🔖 = | Я @Valigonov нанял рученца @nagg1kww 🪙= | до 1500 💵 🖼= | Страховка от сноса 📦 = | Актуальность поста 🗣️-| Ручение уточнять обязательно, без уточнения ручения - не будет возврата ваших средств. Правила - RULES 🖼= | Уточнить ручение 🗃= | Как стать рученцем ℹ️ - С любовью и уважением - @Valigonov

3 Aug 2026, 16:34 UTC44 viewsread 13 August 2026
Forwarded from @skynetikiPhoto

🔉—| Я - @sskyynet нанял на роль гарант чата: @nagg1kww 💰- На сумму: до 101$ 🕘 - На срок: до первого скама. 🔖—| Проверить актуальность ручения Обязательно перед сделкой уточняйте в чате и ждите моего ответа. В случае того если вы не дождались моего ответа, я не буду обязан вам что-либо возмещать ➡️Купить ручение — @sskyynet

30 Jul 2026, 21:25 UTC62 views0 reactionsread 13 August 2026
Forwarded from @ruchflexaPhoto

👤 | Я @shmotflex ручаюсь за: @womxi 🕞 | Сроком: до первого скама 🌐 | На сумму: до 500₽ 🪪 | Проверить актуальность ❗️ Обязательно перед сделкой уточняйте в чате ручений и ждите моего ответа. В случае того если вы не дождались моего ответа, я ничего не верну. 💼 | Мои услуги: @costflex

24 Jul 2026, 21:46 UTC74 viewsread 13 August 2026
Forwarded from @ruch_ot_menyaPhoto

💎Я, @sytener нанял рученца: @womxi 🖥Информация о рученце и его привилегиях: — имеет доверие до 500₽ — ручение действует до первого скама. — страховка от сноса отсутствует. ❗️Важно, перед сделкой уточнить ручение за данного человека у @sytener, чтобы я в случае скама возместил вам средства и снял с должности данную личность (в ином случае возврат средств невозможен)❗️

23 Jul 2026, 18:50 UTC103 viewsread 13 August 2026
Forwarded from @ruchyykPhoto

Я @s1dyyys нанял в качестве гаранта чатов - @nagg1kww. 🍀 Сумма - 52$. 🏷 Сроком - до первого скама. 💻 Страховка от сноса - отсутствует. ✍️ | Если вы не уточнили о том, ручаюсь ли я за данную личность, и он вас обманул, увы - я не обязан что либо вам возвращать.

16 Jun 2026, 20:33 UTC272 views0 reactionsread 13 August 2026
Forwarded from @ruchhayzeraPhoto

👤//– Я @Hayzer_tag назначаю @nagg1kww своим рученцем. ✅| Сумма доверия: 666₽. 🕔| Сроком: До первого скама. 📦| Страховка от сноса: отсутствует. 🔎/ Перед проведением сделки: - заход в чат уточнения ручений. - уточнение ручения по образцу. 🔖//– Примечание: В случае если вас обманул мой подопечный, но вы не уточняли ручение - увы я не буду вам обязан ничего возвращать.

4 Jun 2026, 11:31 UTC325 viewsread 13 August 2026
Forwarded from @Dialekt_ruchPhoto

💎Я, @DialektCVV нанял рученца: @nagg1kww 🖥Информация о рученце и его привилегиях: — имеет доверие до 1500₽. — ручение действует до первого скама. — страховка от сноса отсутствует. ⚠️Важно, перед сделкой уточнить ручение за данного заместителя в @ruch_chat, чтобы в случае скама я возместил вам средства и снял с должности данную личность. 🚫Если вы не уточнили ручение, или не получили моего ответа и вас обманул мой подо…

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

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.

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

“Ручения за Нагиева” (@ruchzanagieva), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ruchzanagieva.

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.