22 Apr 2026, 09:38 UTC≈1,020 viewsread 14 August 2026
Forwarded from @TubirinFess
[]. Kami tidak menerima permintaan takedown MF ya, kecuali jika MF itu berisikan hoax/tidak sesuai kenyataannya.
Channel
Tubirin Rules 🛡️
@Tubirules
On this record: Growth · Engagement · Posts · Citations · Cite this entry
13subscribers
+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 | -1003589270679 |
|---|---|
| Type | Channel |
| Username | @Tubirules |
| Created | 7 February 2026 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 4 times, most recently 9 September 2026 |
| On Telegram | t.me/Tubirules |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 14:38 | 13 | no change |
| 14 Aug 2026, 23:02 | 13 | first reading |
Engagement
14 posts held, back to 7 February 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 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 14 posts for this entry, the most recent from 22 April 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
16 Mar 2026, 12:54 UTC≈1,990 viewsread 14 August 2026
Sticker
Sticker, posted without a caption
14 Mar 2026, 17:07 UTC≈2,020 viewsread 14 August 2026
Banned Words @TubirinFess! N. Please refrain from using thess listed words, or you can be automaticly muted. • Jancok, Asu, Yatim, Boti, Autis, Autism, Bajingan. Bagi yang melanggar, akan terkena auto-mute dan baru bisa kami un-mute sehari setelahnya (harus konfirmasi ke bot).
7 Feb 2026, 16:02 UTC≈1,900 viewsread 14 August 2026
Sticker
Sticker, posted without a caption
7 Feb 2026, 16:01 UTC≈1,850 viewsread 14 August 2026
Explanation of #Tubirin, #Ngespill, and #TuAsk! • #Tubirin, For venting and emotional release only. Share you feelings and experiences without encouraging harassment or targeted attacks. • #Ngespill, For sharing stories, situations, or experiences. Partial personal details are allowed (e.g. Telegram usernames and ID). Private chats may be shared as long as not related information is hidden/blurred. Spills that are…
7 Feb 2026, 15:51 UTC≈1,560 viewsread 14 August 2026
Sticker
Sticker, posted without a caption
7 Feb 2026, 13:00 UTC≈1,570 viewsread 14 August 2026
Photo
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ SHOULDN’T DO; 1. Any content that attacking race, religion, nationality, gender, sexuality, or communities is not allowed. 2. Extremely Sensitive posts will not be posted. 3. Do not include full names, usernames, & screenshot contains not-related person. 4. Questions meant to provoke, drama, judgement, or mass backlash is strictly prohibited. 5. Un-censored NSFW media (1821+,…
7 Feb 2026, 12:58 UTC≈1,290 viewsread 14 August 2026
Photo
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ SHOULD DO; 1. This is a ROLEPLAYER BASE. Every Roleplayers Account is allowed to join and interact within this Base, EXCEPT for Non Roleplayer-Account. 2. Every menfess must be sent only to @TubirinBot! We DO NOT have any other BOT for sending menfess. 3. Must subscribe to @TubirinFess before sending your menfess. 4. You only can send #Tubirin for Tubir, #Ngespill for Spill, a…
7 Feb 2026, 12:42 UTC≈1,070 viewsread 14 August 2026
Those rules will be shared below. Every rules is EFFECTIVE for everyone.
7 Feb 2026, 11:44 UTC≈1,080 viewsread 14 August 2026
Sticker
Sticker, posted without a caption
7 Feb 2026, 11:41 UTC≈1,080 viewsread 14 August 2026
Photo
@TubirinFess is a safe place for you to trash-talks about someone you dislike! Even tho, we still have a rules for you to obey!
7 Feb 2026, 11:12 UTC≈1,060 viewsread 14 August 2026
Sticker
Sticker, posted without a caption
Showing the 12 most recent of 14 posts we hold for @Tubirules. 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Tubirin Rules 🛡️” (@Tubirules), 13 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Tubirules.
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.