3 measurements spanning 1 day, net +2. 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 101–103 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Aug 2026, 09:32
103
no change
9 Aug 2026, 08:31
103
+2
8 Aug 2026, 09:04
101
first reading
Engagement
10 posts held, back to 29 September 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 pageof 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 1 October 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Videos
3
Lifetime counters from Telegram’s own channel header, read 9 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.
Video runtime
9m 37s
Average length
3m 12s
Measured directly from 3 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.
Reaction mix
3 reactions across 3 posts, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🕊
3
100.0%
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 3 of the 10 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 29 September 2025 to 1 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🪽𝐑𝐔𝐋𝐄𝐒🪽
⚡️OPEN APP iOS⚡️
🕳️هنگام گرفتن اوپن اپ و نشان دادن باتری از شارژ کردن دیوایس خود خودداری کنید🕳️
🕳️از باز کردن شرت کات جدید در قسمت شرت کات خودداری کنید درصورت داشتن باید محتوای داخل ان را نشان دهید🕳️
🕳️از داشتن یک اپل ایدی برو روی دو دوایس ایپد خودداری کنید🕳️
🕳️تمامی مراحل اوپن اپ را طبق ویدیو انجام دهید✅
🪽𝐑𝐔𝐋𝐄𝐒🪽
⚡️OPEN APP ANDROID⚡️
💢اوپن اپ حتماً باید پیوسته با آخرین فایت شما باشد ✅
💢هیچگونه اوپن اپ بجز اوپن اپ فوق قابل قبول نمیباشد ✅
👾 مراحل انجام اوپن اپ اندروید 👾
🔤 پلی کردن کالاف از بازار - مایکت - گوگل پلی
🔤 چک کردن فایل ها ( تک به تک فایل ها باید باز شود و حتماً داخل فایل ها هاد و سنس رو باید نشون بدید )
🔤 چک کردن بخش VPN در ستینگ
🔤 چک کردن بخش DNS در ستینگ
🔤 اگر با وای فای پلی میدید طبق …
🪽𝐑𝐔𝐋𝐄𝐒🪽
⚡️OPEN APP PC⚡️
👾 مراحل انجام اپن اپ PC 👾
🔤نشان دادن تمامیه فایل های گیم
🔤نشان دادن قسمت Task Manager
processes , app history , startup ,Users , Details , Services
🔤نشان دادن DNS از طریق Control panel
🔤نشان دادن programs از طریق control panel
🔤کد های cmd به شرح زیر میباشد :
nslookup
ipconfig /all
🔤نشان دادن ستینگ گیم لوپ قسمت انجین
🪽𝐑𝐔𝐋𝐄𝐒🪽
🤩تمامی پلیر ها موظف هستند که در تمامی بازی ها فول رکورد اوپن اپ باشند یعنی از اول بازی تا اخر اوپن اپ رکورد باشند و درصورت خواستن بدون کات خوردگی و ادیت ارسال کنند🖤
🤩درصورت عدم ارائه رکورد اوپن اپ پلیر
پوینت تیم در مچی که پلیر ریپورت خورده صفر می شود🖤
🤩درصورت رکورد اوپن اپ ناقص پلیر
پوینت پلیر در مچی که ریپورت خورده صفر می شود🖤
🤩تمامی پلیر ها در هر مچ رنکینگ باید دارای فول رکورد و اوپن اپ طبق نمونه اتحادی…
🪽𝐑𝐔𝐋𝐄𝐒🪽
💢Things that cause a player to be banned❌
1️⃣Cheat
2️⃣Confing
3️⃣Dns
4️⃣Team UP
5️⃣Failure to provide open app records frequently
🖤All players must have a full record and a full open app when playing 🖤
🪽𝐑𝐔𝐋𝐄𝐒🪽
🔹 موارد پوینت منفی و مثبت به شرح زیر میباشد❗️
1️⃣استفاده از موارد گان بن : 5 پوینت منفی برای استفاده کننده و 5 پوینت مثبت برای فرد ناک شده دارد
2️⃣استفاده از وسایل نقلیه در 𝟑 زون اخر 5 پوینت منفی دارد
ناک کردن یا دمیج کردن انمی با وسایل نقلیه 5 پوینت منفی و 5 پوینت مثبت برای فرد ناک شده یا دمیج شده به همراه خواهد داشت
3️⃣کمپ بیش از حد در زون های اول با تشخیص هاست رنکینگ 5 پوینت منفی برای تیمی که کمپ کرده…
Showing the 10 most recent of 10 posts we hold for @Rules_RANKiNGS. 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.
Citation-graph rank
Citation-graph rank — 186,132 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 3 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.
Named by
Channels on the register whose posts name this channel's handle.
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 9 August 2026 — this
entry's latest reading, not the date you are reading this.
“• 𝐑𝐮𝐥𝐞𝐬 𝐑𝐀𝐍𝐊𝐢𝐍𝐆𝐒 •” (@Rules_RANKiNGS), 103 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Rules_RANKiNGS.
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.