Channel
@gudang_public
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
2,149subscribers
+4 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001494592866 |
|---|---|
| Type | Channel |
| Username | @gudang_public |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/gudang_public |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 22:19 | 2,149 | -2 |
| 11 Sept 2026, 19:38 | 2,151 | -1 |
| 7 Sept 2026, 05:20 | 2,152 | +7 |
| 2 Sept 2026, 05:30 | 2,145 | no change |
| 2 Sept 2026, 05:15 | 2,145 | first reading |
19 posts held, back to 7 March 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 19 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
120 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 36.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 44 | 36.7% | |
| 🔥 | 24 | 20.0% | |
| 👍 | 23 | 19.2% | |
| 🤣 | 9 | 7.50% | |
| 😱 | 5 | 4.17% | |
| 😢 | 3 | 2.50% | |
| 🤔 | 3 | 2.50% | |
| 👌 | 2 | 1.67% | |
| 👎 | 2 | 1.67% | |
| 👏 | 2 | 1.67% | |
| 🤯 | 1 | 0.833% | |
| 🥰 | 1 | 0.833% | |
| 🥴 | 1 | 0.833% |
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 17 of the 19 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 120 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 7 March 2026 to 19 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gudang_public. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 19 most recent posts we hold for this entry, published 7 March 2026 to 19 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Some apps were showed as "Unsupported" or "Unavailable" while using stock fingerprint, even it's strong integrity. There's a simple fix: use PIF module: Install PIF module > fetch a new fingerprint > make sure spoof build and spoof build (for play store) turned on > clear data play store and wait Google have something special? 🤔
🤣5❤3🤔3
Signed NVG-064
ZygiskNext 1.4.4 temporary root solution? 😁😁
❤1
Signed NVG-064
But don't worry, IsolPolicy module helps Magisk users 😇 https://t.me/gudang_public/437
👍4❤1🤣1🥰1
Signed NVG-064
Now BRImo also detects SELinux modification. Magisk users are dead? 💀☠️
🤣3😢3❤1
Signed NVG-064
Channel photo updated
ZygiskNext users... Update to this build (820) to fix Futile Hide 08 detections. Some real apps (MyBCA) detect these. Other real apps may detect, too https://t.me/real5ec1cff/279?comment=127243
🔥5❤3
Signed NVG-064
For APatch user, use this KPM to hide selinux: https://t.me/APatch_nightly/142
❤1
Signed NVG-064
Another proof that BRImo uses sepolicy to check root: https://t.me/krenlol/2623
❤1
Signed NVG-064
For Magisk and old version KSU (version 3.2.4-61 or lower) users, you can try these modules: https://t.me/mhm72dd/170 How to: 1. Install as normal app 2. Activate it through LSPosed 3. Only tick recommended 4. Reboot 5. Open the app 6. Select an app you want to hide
👍8❤5👎2
Signed NVG-064
Someone tested BRImo working with these methods, by enabling "Hide SELinux modification" feature. This may also works with other applications like OCTO by CIMB Niaga Thanks to @niCknaMe134 👍👍 Edit: You can also install avc selinux spoof module. If you have it built-it, enable under settings
❤5
Signed NVG-064
For those who want to see the configuration *Note: ignore bindhosts section. I just want to show that I don't add the zimperium host to block
❤3🔥2👏1
Signed NVG-064
Fix OCTO by CIMB Niaga version 3.1.60 or above *bindhosts module no longer needed Requirements: - Hybrid Mount metamodules (or similar meta modules that able to mount as EXT4. For example: mountify) - TrickyStore (or TrickyStore OSS) - ZygiskNext (or other zygisk provider like NeoZygisk) - Hide My Applist (or HMA OSS or HMA OSS Zygisk) Steps: 1. Install hybrid mount meta modules. Configure it as EXT4 overlay mode.…
❤4👍3👏1
Signed NVG-064
Showing the 12 most recent of 19 posts we hold for @gudang_public. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Gudang Public” (@gudang_public), 2,149 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/gudang_public.
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.