Telegram RegisterThe public register of Telegram
Telegram profile photo for ‎Подслушано ⇌ ркм

Channel

‎Подслушано ⇌ ркм

@overheardraidcm

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

496subscribers

-13 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-1003777783606
TypeChannel
Username@overheardraidcm
CreatedBetween 1 February 2026 and 6 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/overheardraidcm

Growth

496509502.57 August 2026 — 509 subscribers8 August 2026 — 509 subscribers16 August 2026 — 508 subscribers23 August 2026 — 503 subscribers30 August 2026 — 496 subscribers7 August 202630 August 2026
5 measurements spanning 23 days, net -13. 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 494–511 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 11:48496-7
23 Aug 2026, 20:15503-5
16 Aug 2026, 18:05508-1
8 Aug 2026, 04:15509no change
7 Aug 2026, 19:44509first reading

Engagement

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

Reaction mix

40 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 42.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1742.5%
💘1640.0%
👎717.5%

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 8 of the 20 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 40 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 July 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

3 Aug 2026, 15:35 UTC94 views10 reactionsread 8 August 2026

Нарц и раньше были хуйня ебаная,а когда влд стал Вальтер стало ещё хуже. Вычеты типо "Я не рейдер",АЛО ТЫ ВЛД РКФ КАКОЙ НАХУЙ НЕ РЕЙДЕР #тейк && @overheardraidcm

👍10

28 Jul 2026, 09:25 UTC182 views6 reactionsread 8 August 2026

зачем найтми делают сайт для тейков, или это круто и я не шарющий #тейк && @overheardraidcm

👍5👎1

24 Jul 2026, 17:37 UTC276 viewsread 8 August 2026

блять привет кф знаю что старую воду мутить нельзя, но давайте вспомним тссбир, она вообще была доксером? всплыла инфа опять в другом км что она сносила каналы и якобы была доксером #тейк && @overheardraidcm

22 Jul 2026, 09:27 UTC305 viewsread 8 August 2026

Меня интересует, почему нерфф и ее друзья засирают другие ркн? допустим подвалышей, у них подписчиков больше чем у вас всех вместе взятых. #тейк && @overheardraidcm

22 Jul 2026, 08:43 UTC283 viewsread 8 August 2026

сапп эочу затронуть очень давнюю тему,нооо это правда что коза (владелец уже не помню какого канала) покончила с собой после того как ее опозорили во всем км и она закрыла канал? ситуация : в ее канале должен был состояться батл в котором вроде бы все так гладко шло, но потом произошла какаято хуйня которую я уже точно не помнб, и после этой хуйни ее начали гнобить и делать разъебы на нее. скажите пожалуйста правда л

16 Jul 2026, 15:57 UTC327 views7 reactionsread 8 August 2026

что за хуйню с хантерами нам в бота кидают

💘7

10 Jul 2026, 13:22 UTC323 viewsread 8 August 2026
Forwarded from @hanterconfPhoto

⤿ хантер ⠘ канал для слива ссылок. . click ⁞ ссылка на канал ещё ᛬ ↷ это рейд канал, где вы можете слить ссылку на флуд/ролку и тд. комфортное времяпровождение, посиделки и всё-всё-все — здесь! ⨳ НАВИГАЦИЯ ⇄ все ссылки click ⁞ важное о канале ① click ⁞ вп пост ② click ⁞ чат&прайс ③ click ⁞ резерв ④ click ⁞ приват конфа ⑤ click ⁞ спам материал ⑥ ⨳ ADMINISTRATION OWN ⇆ корпсе ((🥩)) OW

10 Jul 2026, 09:15 UTC302 views4 reactionsread 8 August 2026
Photo

скажи что ты шутишь пожалуйста #тейк && @overheardraidcm

💘4

9 Jul 2026, 20:37 UTC300 viewsread 8 August 2026

Привет а то что я без рейд канала рейдил флуды с друзьями это считается что я теперь тоже в ркм? #тейк && @overheardraidcm

9 Jul 2026, 16:00 UTC316 viewsread 8 August 2026

пр подслушка, к ркм относятся кф снос тематики? типо сбт кф или нет? просто рейд обширное понятие #тейк && @overheardraidcm

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

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

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.

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

“‎Подслушано ⇌ ркм” (@overheardraidcm), 496 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/overheardraidcm.

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.