Channel

Ручения за @matizqqq

@ruchmatiz

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

3subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID	-1003465944739
Type	Channel
Username	@ruchmatiz
Created	26 December 2025 — measured — dated from the channel’s first post
First recorded	14 August 2026
Last confirmed live	5 September 2026
Measurements held	2
Confirmed unchanged	4 times, most recently 5 September 2026
On Telegram	t.me/ruchmatiz

Growth

2 measurements spanning 1 day. 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 2–4 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
15 Aug 2026, 16:14	3	no change
14 Aug 2026, 06:46	3	first reading

Engagement

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

Recent posts

9 Apr 2026, 16:51 UTC103 viewsread 14 August 2026

Forwarded from @kharonm_RemoverPhoto

🏆 • | Я @kharonm назначаю на роль гаранта чатов: @matizqqq 👑 - | Суммой доверия - 100$. ⌛ - | Сроком - до первого скама. 💎- | Привилегии услуг. 📰- | Правила подопечного. 🛡 Правило проведения сделки с гарантом: - обязательно вступить в чат уточнения ручения. - уточнить ручение по образцу. - в случае, если вы не уточнили ручение на гаранта и он вас обманул, то я не буду обязан вам возмещать причиненный ущерб. 🪙- | Акт…

10 Mar 2026, 17:29 UTC175 views0 reactionsread 14 August 2026

Forwarded from @ruchsqwirzayPhoto

🔴—| Я - @sqwirzay наняла вечного заместителя @matizqqq 💸 - На сумму: до 2000₽. 🔴 - На срок: до первого скама. ➡️—| Проверить актуальность ручения ‼️Обязательно перед сделкой уточняйте в чате ручений и ждите моего ответа. В случае того если вы не дождались моего ответа, я не буду обязана вам что-либо возмещать. ✅ Приобрести услугу — @sqwirzay

10 Mar 2026, 14:11 UTC166 viewsread 14 August 2026

Forwarded from @RyhHarlitasPhoto

Я @Harlitas и @mityaigrizzly взяли – @matizqqq в качестве гаранта чата «Империя» 💰Сумма - до 50$ - 4000р. |❗|Обязательно перед сделкой уточняйте в чате ручений без моего ответа, возврата не будет в случае скама со стороны гаранта чата . |💼| 🛡 услуги: @Harlitas

10 Mar 2026, 14:11 UTC149 viewsread 14 August 2026

Photo

📌 | Я @mityaigrizzly и @Harlitas Наняли гаранта чата @matizqqq 🔜 | Сроком: до первого скама 💰| На сумму: до 50 💵 Страховка ❌ ❗️Обязательно уточняйте ручения в чате ручений 👽 Если вы не дождались моего ответа в чате я не обязан ничего вам возвращать ❌ 💼 | Приобрести услуги: @mityaigrizzly

19 Feb 2026, 15:41 UTC258 viewsread 14 August 2026

У меня еще есть, но мне жоско лень добавлять, хавайте это

3 Jan 2026, 22:56 UTC821 viewsread 14 August 2026

Forwarded from @Dialekt_ruchPhoto

❄️| Я @DialektCVV нанял зама - @matizqqq ❗️| назначаю свои вечным заместителем суммой до 5555₽. ⛔️| ОБЯЗАТЕЛЬНО перед сделкой уточняйте ручение в чате ручей - @ruch_chat, без уточнения, или без моего ответа, возврата не будет в случае скама. Страховка от сноса? - отсутствует |❌|.

3 Jan 2026, 22:32 UTC867 viewsread 14 August 2026

Forwarded from @rychotlitvinnaPhoto

|🔖| Я @Litvinn нанял гаранта чата - @matizqqq |💎| Сумма - 42$ |🚫| Страховка - ❌ |📰/ проверить на скам |🔉|Обязательно перед сделкой уточняйте в чате, без уточнения, или без моего ответа, возврата не будет в случае скама со стороны рученца. |🔔| услуги: @litvinnyslygi

2 Jan 2026, 13:33 UTC103 viewsread 14 August 2026

Forwarded from @Dialekt_ruchPhoto

❄️| Я @DialektCVV нанял зама - @matizqqq ❗️| назначаю свои вечным заместителем суммой до 3000₽. ⛔️| ОБЯЗАТЕЛЬНО перед сделкой уточняйте ручение в чате ручей - @ruch_chat, без уточнения, или без моего ответа, возврата не будет в случае скама. Страховка от сноса? - отсутствует |❌|.

30 Dec 2025, 11:06 UTC508 viewsread 14 August 2026

Forwarded from @rychotlitvinnaPhoto

|🔖| Я @Litvinn взял в качестве стажа - @matizqqq |💎| Сумма - 1500₽ |➕| Кол-во сделок - 55 |🚫| Страховка - ❌ |📰/ проверить на скам |🔉|Обязательно перед сделкой уточняйте в чате, без уточнения, или без моего ответа, возврата не будет в случае скама со стороны рученца. |🔔| услуги: @litvinnyslygi

30 Dec 2025, 10:32 UTC407 viewsread 14 August 2026

Forwarded from @kharonm_RemoverPhoto

🚀 —| Я @kharonm — нанял в качестве рученца @matizqqq 💸 — На сумму: до 7000₽. ⌛ — На срок: до первого скама. ➡️ | — Проверить актуальность ручения. ‼️Обязательно перед сделкой уточняйте в чате ручений и ожидайте моего ответа. В случае, если вы не дождались моего ответа, то я не буду обязан возмещать вам причененный ущерб. ✅Приобрести ручение — @kharonm

26 Dec 2025, 15:36 UTC329 viewsread 14 August 2026

Forwarded from @ruchdlxPhoto

🔔—| Я - @delya нанял рученца @matizqqq 💰 - На сумму: до 1000₽. 🕞 - На срок: до первого скама. 🔗—| Проверить актуальность ручения ⚠️Обязательно перед сделкой уточняйте в чате ручений и ждите моего ответа. В случае того если вы не дождались моего ответа, я не буду обязан вам что-либо возмещать. 🔵Купить ручение — @delya

26 Dec 2025, 15:35 UTCviews —

Channel created

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

Ручения от - @DialektCVV.
@Dialekt_ruch · 8822 posts Haron | Канал ручений
@kharonm_Remover · 4272 posts Канал Подопечных: @Litvinn
@rychotlitvinna · 442 posts Ручения от: @delya
@ruchdlx · 3,2601 post Ручения от @sqwirzay
@ruchsqwirzay · 1191 post Ручᴇниᴋи @Harlitas
@RyhHarlitas · 31 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 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.

Adapter — @matizqqq
@adaptmatiz · 61 post

Names

Channels on the register whose handles appear in this channel's posts.

б
@matizqqq · 210 posts Переехал
@kharonm · 1812 posts @litvinn
@Litvinn · 12 posts Покупка Продажа Подарков
@nft_yslygi · 6,7912 posts Переходник от @DialektCVV.
@ruch_chat · 1542 posts Канал Подопечных: @Litvinn
@rychotlitvinna · 442 posts 𝗰𝗼𝗻𝘁𝗶𝗻𝗲𝗻𝘁𝗮𝗹 переходник
@SenyaIncel · 6222 posts Привелегии Харона
@Hatonigw · 3161 post Правила от: @kharonm
@informationClis · 1961 post Haron | Канал ручений
@kharonm_Remover · 4271 post Ручения от: @delya
@ruchdlx · 3,2601 post Ручения от @sqwirzay
@ruchsqwirzay · 1191 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.

Handles this channel named that no longer answer

Dead references: 1; handles named in this channel’s posts, vacant today
Evidenced gone: 0; we ourselves saw one of these resolve, at some point
Never seen alive: 1; vacant every time we have ever looked

@ruchmatiz named 1 handle 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.

Never seen alive

References a handle that is not a live channel — we have no record it ever was one.

@litvinnyslygi
named in 1 post, 15 August 2026 – 15 August 2026

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

“Ручения за @matizqqq” (@ruchmatiz), 3 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/ruchmatiz.

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.