🤔 VODKA Need Player🤔 Active player🩵 Just 120 Fps⚡ Rol: Frag sup IGL➡️ Free time➡️ 🟢Contact: @lm_ALI_NT
Signed Ali

Channel
@ROOM_C1
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
6,505subscribers
+3,246 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003081705777 |
|---|---|
| Type | Channel |
| Username | @ROOM_C1 |
| Description | واسطه های کانال: @C1_ADMIN_1 @C1_ADMIN_2 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/ROOM_C1 |
Gaming — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 28 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @ROOM_C1/4026 · this entry30 Oct 2026, 19:17 UTC | @WIRE_MORTAL/20161 Nov 2026, 17:52 UTC | 1.00 | 47 hours |
| @WIRE_MORTAL/20172 Nov 2026, 20:34 UTC | @ROOM_C1/4089 · this entry2 Nov 2026, 20:34 UTC | 1.00 | under a minute |
| @WIRE_MORTAL/20234 Nov 2026, 16:25 UTC | @ROOM_C1/4287 · this entry10 Nov 2026, 16:19 UTC | 1.00 | 6 days |
| @WIRE_MORTAL/20315 Nov 2026, 11:42 UTC | @ROOM_C1/4334 · this entry13 Nov 2026, 20:14 UTC | 1.00 | 8 days |
| @WIRE_MORTAL/20356 Nov 2026, 14:27 UTC | @ROOM_C1/4202 · this entry7 Nov 2026, 18:21 UTC | 1.00 | 28 hours |
| @ROOM_C1/4201 · this entry7 Nov 2026, 17:44 UTC | @WIRE_MORTAL/20497 Nov 2026, 17:44 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @WIRE_MORTAL | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @WIRE_MORTAL (6–3) |
| @stark_ckicken | 5 (5/5 hand-verifiable sample passed) | 1.00 | 25 hours | this entry (3–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 8 of the 8 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 46 comparable posts for this entry, running 6 August 2026 to 15 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 28 channels, the one whose matching posts we hold earliest is @SHOP_RaaD. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 28 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
6 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 03:06 | 6,505 | -64 |
| 10 Nov 2026, 18:50 | 6,569 | -43 |
| 6 Nov 2026, 21:39 | 6,612 | +31 |
| 3 Nov 2026, 13:21 | 6,581 | +1 |
| 31 Oct 2026, 16:18 | 6,580 | +43 |
| 28 Oct 2026, 13:24 | 6,537 | +27 |
| 25 Oct 2026, 09:36 | 6,510 | +50 |
| 22 Oct 2026, 05:59 | 6,460 | +3 |
| 18 Oct 2026, 18:17 | 6,457 | +98 |
| 15 Oct 2026, 13:16 | 6,359 | +92 |
| 12 Oct 2026, 15:57 | 6,267 | +208 |
| 5 Oct 2026, 15:59 | 6,059 | +670 |
| 27 Sept 2026, 23:19 | 5,389 | +125 |
| 18 Sept 2026, 18:36 | 5,264 | +10 |
| 14 Sept 2026, 19:58 | 5,254 | +147 |
| 11 Sept 2026, 04:59 | 5,107 | +69 |
| 6 Sept 2026, 03:39 | 5,038 | +17 |
| 2 Sept 2026, 01:42 | 5,021 | +92 |
| 29 Aug 2026, 20:55 | 4,929 | +144 |
| 27 Aug 2026, 00:37 | 4,785 | first reading |
93 posts held, back to 6 August 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 13 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. It is computed over the 30 of 73 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 93 (6 August 2026 – 16 November 2026) |
| Views total | 10,331 |
| Reactions total | 113 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 16:36 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 16 November 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.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
141 reactions across 32 posts, in 6 distinct kinds. The most used accounts for 52.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 74 | 52.5% | |
| 👍 | 62 | 44.0% | |
| 🍌 | 2 | 1.42% | |
| 💔 | 1 | 0.709% | |
| 🔥 | 1 | 0.709% | |
| 🥰 | 1 | 0.709% |
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 33 of the 93 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 141 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 93 most recent posts we hold, published 6 August 2026 to 16 November 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.
Telegram’s own ‘edited’ marker: 8 of 73 posts held from the last 30 days (11.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🤔 VODKA Need Player🤔 Active player🩵 Just 120 Fps⚡ Rol: Frag sup IGL➡️ Free time➡️ 🟢Contact: @lm_ALI_NT
Signed Ali
جهت همکاری و روم مشترک به پیوی زیر مراجعه کنید ⬇️ @Ali_17_C1
Signed Ali
💥🚨 BOOM! آمادهای پینگتو رو یه تکون اساسی بدی؟ 🚨💥 🎮 DNS مخصوص پابجی آمادهست! ⚡️ اتصال روانتر، مسیر بهتر، آماده برای مچ! 📥 DNS پابجی رو همین الان از ربات دریافت کن 🪖 وارد لابی شو، مچتو بزن و آمادهی نبرد باش! 🔥 وقتی نبرد شروع میشه، هیچ چیزی نباید جلوتو بگیره! 🔥 ✅ برای دریافت DNS پابجی کلیک کنید✅ 🚨🔥 پابجی فیلتر شده؟ نگران نباش! 🔥🚨 🎮 وایرگارد رایگان برای پابجی! ⚡️ اتصال پایدارتر 🕹 مناسب برای ورود به بازی و مچدادن …
Signed Mr mmd
❤️وایرگارد پابجی موبایل❤️ ▫️ 𝗪𝗜𝗥𝗘𝗚𝗨𝗔𝗥𝗗 𝗣𝗨𝗕𝗚 ▫️ ▫️ سرور : سنگاپور 🇸🇬 یکی از بهترین سرور هاس برای گیم ✔️ ▫️ مناسب برای: همراه اول - ایرانسل - رایتل 🌐کانفینگ اختصاصی خود را دریافت کنید🛡 💎𝗥𝗘𝗖𝗘𝗜𝗩𝗘 𝗪𝗜𝗥𝗘𝗚𝗨𝗔𝗥𝗗💎 مخصوص لاگین و پلی دادن❤️ با ری اکشن های زیباتون به ما انرژی زیادی میدید💔❤️
Signed Mr mmd
وایرگارد پابجی موبایل ▫️ ▫️ سرور: آلمان✔️ 💐𝗗𝗼𝘄𝗻𝗹𝗼𝗮𝗱 𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱🔥 All Device:برا همه چی جوابه ✅ - مخصوص روم و رنکاپ ▫️▫️ برای همه کار میده ✅ ری اکشن بزنید بیشتر براتون بزارم😍 حجم 0️⃣0️⃣1️⃣ گیگ
Signed Mr mmd
⚔️ 𝗪𝗜𝗥𝗘𝗚𝗨𝗔𝗥𝗗 × 𝗣𝗨𝗕𝗚 𝗠𝗢𝗕𝗜𝗟𝗘 🇩🇪 𝗟𝗢𝗖𝗔𝗧𝗜𝗢𝗡 : 𝗚𝗘𝗥𝗠𝗔𝗡𝗬 📦 DOWNLOAD CONFIG 💎 𝗘𝗟𝗜𝗧𝗘 𝗚𝗔𝗠𝗜𝗡𝗚 𝗦𝗘𝗥𝗩𝗘𝗥 🎮 𝗗𝗘𝗦𝗜𝗚𝗡𝗘𝗗 𝗙𝗢𝗥 𝗥𝗢𝗢𝗠𝗦 & 𝗥𝗔𝗡𝗞𝗘𝗗 📱 𝗔𝗟𝗟 𝗗𝗘𝗩𝗜𝗖𝗘𝗦 | 𝗙𝗨𝗟𝗟 𝗖𝗢𝗠𝗣𝗔𝗧𝗜𝗕𝗜𝗟𝗜𝗧𝗬 ⚡️ 𝗚𝗔𝗠𝗜𝗡𝗚 • 𝗕𝗥𝗢𝗪𝗦𝗜𝗡𝗚 • 𝗗𝗢𝗪𝗡𝗟𝗢𝗔𝗗 📦 𝗧𝗢𝗧𝗔𝗟 𝗗𝗔𝗧𝗔 : 𝟭𝟬𝟬 𝗚𝗕 ⚪️⚪️⚪️⚪️⚪️⚪️⚪️⚪️ 👑 𝗪𝗔𝗡𝗧 𝗠𝗢𝗥𝗘 𝗚𝗔𝗠𝗜𝗡𝗚 𝗖𝗢𝗡𝗙𝗜𝗚𝗦❗️ ❤️ 𝗗𝗥𝗢𝗣 𝗔 𝗥𝗘𝗔𝗖𝗧 & 𝗦𝗧𝗔𝗬 𝗧𝗨𝗡𝗘𝗗✅
Signed Mr mmd
وینر پی👇 @PC_PUBG_YR
Signed Mr. Yaser
7705635 ❌
Signed Ali
آیدی روم ⬇️
❤3👍1
Signed Ali
درود خـــــســـــتـــه نــــبـــاشـــیـــد 🗺 Map : (ارانگل) 👨👩👧👦 Type : squad ⏱ time : 20:00 🎁 prize :150T ⚡️قبل از ساعت (20.00) عضو چنلا باشید⚡️ ⚡️پرایز به MVP تیم وینر داده میشه⚡️ ⛔️لول زیر 50 ممنوع ⛔️تیم آپ ممنوع ⛔️هرگونه چیت باعث بن از تمامی روما 💥@KWPIK 💥@EGO_CHEAT 💥@ROOM_C1 💥@mori_op 💥@DARK_PING_PUBG 💥@pudg_world 💥@nexguardd 💥@JAGUAR_PUBGC 💥@Ziko_lab عـضــویـت در چـنـل اسـپـانسـر الزامـیـسـت ‼️ ⚜@PU…
❤2
Signed Mr. Yaser
جهت همکاری و روم مشترک به پیوی زیر مراجعه کنید ⬇️ @Ali_17_C1
وینر پی👇 @PC_PUBG_YR
Showing the 12 most recent of 93 posts we hold for @ROOM_C1. 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.
We recorded 3 posts on @ROOM_C1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 43 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. The 18 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@ROOM_C1 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“ROOM C1/پابجی” (@ROOM_C1), 6,505 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/ROOM_C1.
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.