Telegram RegisterThe public register of Telegram
Telegram profile photo for π—₯π—¨π—Ÿπ—˜π—¦ π—¨π——π—šπŸ­πŸ³

Channel

π—₯π—¨π—Ÿπ—˜π—¦ π—¨π——π—šπŸ­πŸ³

@RULESUDG

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

35subscribers

+1 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003505456533
TypeChannel
Username@RULESUDG
CreatedBetween 1 December 2025 and 31 May 2026β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/RULESUDG

Growth

343534.511 Aug 2026, 12:50 β€” 34 subscribers11 Aug 2026, 13:01 β€” 34 subscribers12 Aug 2026, 03:18 β€” 35 subscribers11 Aug 2026, 12:5012 Aug 2026, 03:18
3 measurements taken within a single day, net +1. 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 34–35 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 03:1835+1
11 Aug 2026, 13:0134no change
11 Aug 2026, 12:5034first reading

Engagement

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

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❀2100.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 2 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 2reactions 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 16 June 2026 to 16 June 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

16 Jun 2026, 02:35 UTC97 viewsread 11 August 2026

☠ RULES KONTEN ☠ ⭐. Team konten / podcast wajib memahami peran utama dalam pembuatan, peng elolaan, dan publikasi konten serta podcast resmi underground. ⭐. Setiap anggota tim wajib menghasilkan ide konten yang kreatif, relevan, dan sesuai dengan citra underground. Ide harus dibahas dan disetujui tim sebelum dipublikasikan. ⭐. Wajib mengikuti jadwal recording, editing. Keterlambatan akan memengaruhi alur publikasi…

16 Jun 2026, 02:35 UTC96 viewsread 11 August 2026

☠ RULES EDITING ☠ ⭐. Team editing wajib memahami peran utama dalam proses penyuntingan audio, video, visual, serta memastikan hasil akhir sesuai standar dan identitas underground. ⭐. Setiap editor wajib menghasilkan output yang rapi, presisi, dan layak publikasi. Editing harus memperhatikan detail teknis seperti transisi, audio balance, color grading, timing, serta konsistensi branding. ⭐. Wajib mengikuti timeline…

16 Jun 2026, 02:35 UTC82 viewsread 11 August 2026

☠RULES CO- FOUNDER☠ ⭐. co-founder wajib memahami secara menyeluruh aturan, sistem kerja, serta struktur kepengurusan underground. seorang pemimpin tidak hanya mengetahui peraturan, tetapi konsisten menerapkannya dalam setiap tindakan. ⭐. Jabatan Founder dan co-founder tidak diperuntukkan bagi individu yang setengah setengah. Posisi ini hanya layak diisi oleh mereka yang memiliki tujuan jelas untuk membangun, menja…

16 Jun 2026, 02:35 UTC108 viewsread 11 August 2026

☠RULES C/OWNER☠ ⭐. Setiap owner dan c-owner wajib mengetahui, memahami, serta menjalankan seluruh sistem dan peraturan underground. Peran ini menjadi penghubung penting antara kebijakan pimpinan dan pelaksanaan tim. ⭐. Diharapkan mampu menjalankan tugas dengan penuh tanggung jawab serta memiliki inisiatif tinggi dalam menyelesaikan permasalahan tanpa bergantung pada arahan terus menerus. ⭐. Wajib memahami alur ker…

Showing the 12 most recent of 20 posts we hold for @RULESUDG. 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 β€” 1,314,364 of 1,480,975entries 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 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.

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 12 August 2026 β€” this entry's latest reading, not the date you are reading this.

β€œπ—₯π—¨π—Ÿπ—˜π—¦ π—¨π——π—šπŸ­πŸ³β€ (@RULESUDG), 35 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/RULESUDG.

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.