Telegram RegisterThe public register of Telegram
Telegram profile photo for Rem01 Project

Channel

Rem01 Project

@rem01schannel

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

10,766subscribers

+128 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001796191434
TypeChannel
Username@rem01schannel
CreatedBetween 1 February 2022 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live31 August 2026
Measurements held22
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/rem01schannel

Growth

10,63810,76610,7027 August 2026 — 10,638 subscribers8 August 2026 — 10,641 subscribers9 August 2026 — 10,654 subscribers10 August 2026 — 10,666 subscribers11 August 2026 — 10,685 subscribers12 August 2026 — 10,699 subscribers13 August 2026 — 10,705 subscribers14 August 2026 — 10,715 subscribers16 August 2026 — 10,721 subscribers17 August 2026 — 10,725 subscribers18 August 2026 — 10,721 subscribers19 August 2026 — 10,719 subscribers20 August 2026 — 10,727 subscribers21 August 2026 — 10,730 subscribers22 August 2026 — 10,743 subscribers24 August 2026 — 10,748 subscribers26 August 2026 — 10,751 subscribers27 August 2026 — 10,754 subscribers28 August 2026 — 10,757 subscribers29 August 2026 — 10,758 subscribers30 August 2026 — 10,762 subscribers31 August 2026 — 10,766 subscribers7 August 202631 August 2026
22 measurements spanning 24 days, net +128. 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 10,619–10,785 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
31 Aug 2026, 10:1410,766+4
30 Aug 2026, 09:4410,762+4
29 Aug 2026, 10:3510,758+1
28 Aug 2026, 09:5310,757+3
27 Aug 2026, 09:3810,754+3
26 Aug 2026, 12:5310,751+3
24 Aug 2026, 08:0410,748+5
22 Aug 2026, 18:1610,743+13
21 Aug 2026, 11:1310,730+3
20 Aug 2026, 11:1210,727+8
19 Aug 2026, 09:0310,719-2
18 Aug 2026, 10:5410,721-4
17 Aug 2026, 12:2310,725+4
16 Aug 2026, 03:2610,721+6
14 Aug 2026, 16:0710,715+10
13 Aug 2026, 06:5510,705+6
12 Aug 2026, 09:3810,699+14
11 Aug 2026, 10:4310,685+19
10 Aug 2026, 09:5210,666+12
9 Aug 2026, 07:1110,654first reading

Engagement

22 posts held, back to 13 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 36 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
33.4%
avg views ÷ 10,766 subscribers
Avg views / post
3,600
2 posts measured
Reaction rate
1.18%
reactions ÷ views · ER floor
Posts in window
2
of 22 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 August 2026
Posts held22 (13 August 202517 August 2026)
Views total7,190
Reactions total85
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 12:53 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.

Reaction mix

2,376 reactions across 22 posts, in 15 distinct kinds. The most used accounts for 49.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,16649.1%
76332.1%
👏974.08%
🤩974.08%
👍954.00%
🤔301.26%
🗿281.18%
🤯241.01%
🙏200.842%
❤‍🔥190.8%
👌110.463%
😁110.463%
🥰100.421%
🕊30.126%
👀20.084%

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 22 of the 22 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 2,376reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 13 August 2025 to 17 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.

Telegram Stars

Stars received
6
across the posts below
Posts paid on
5
of 22 we hold a reading for · 23%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rem01schannel. 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 22 most recent posts we hold for this entry, published 13 August 2025 to 17 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.

Recent posts

17 Aug 2026, 06:20 UTC≈2,500 views45 reactionsread 29 August 2026
Forwarded from @pgsfdcPhoto

🇮🇩 Selamat HUT ke-81 Republik Indonesia! 81 tahun merdeka, satu tanah air, satu bangsa, satu Indonesia. Mari terus menjaga persatuan dan kesatuan demi Indonesia yang lebih baik. Merdeka! ❤️🤍

🔥358❤‍🔥1😁1

Signed ꦠꦾꦎꦴꦭꦶꦪ

9 Aug 2026, 12:27 UTC≈4,690 views40 reactionsread 29 August 2026
Forwarded from @COPG_modulePhoto

✨COPG SPOOF✨ An advanced Zygisk device spoofer that makes your games and apps believe they're running on a Different Device — unlocking high-FPS modes, HD graphics and premium features gated to specific hardware. Per-app, no reboot. 🔵Telegram Channel 🐱GitHub Repo ⬇️Download 🔞Support the Project 🧑‍💻Alireza Parsi

🔥2413❤‍🔥3

Signed Rem01 Gaming

16 Jul 2026, 23:04 UTC≈9,450 views49 reactionsread 29 August 2026
Photo

Encore Bypass Charging 2.1 is Here Enable bypass charging automatically when playing games, protecting battery health during game sessions. Changelog • Adjust charging switches • Add 5s delay before measuring current to stabilize system • Add multi token support to mitigate SN collision • Other misc changes and optimizations Note Not all device or kernel support bypass charging, please test the bypass charging by

🔥2413👍7🗿5

Signed Rem01 Gaming

10 Jul 2026, 03:59 UTC≈14,400 views88 reactionsread 29 August 2026
Photo

Encore Tweaks 5.2.1 is Here A Magisk Module created to enhance device performance during gaming sessions, while keeping battery life optimized for normal use. Changelog • Fix addon modules doesn't working when disable tweaks is enabled • Fix DND mode did not reset after exiting the game 🌐 Chat Group 🌐 GitHub Repo 🌐 Website | Download ✨ Support My Project 🧑‍💻 Rem01 Project

🔥6115🗿7👍5

Signed Rem01 Gaming

4 Jul 2026, 15:10 UTC≈16,300 views90 reactionsread 29 August 2026
Photo

Encore Tweaks 5.2 is Here A Magisk Module created to enhance device performance during gaming sessions, while keeping battery life optimized for normal use. Changelog • Implement binder monitor for system monitoring • Fix daemon crash due java companion issue on certain devices • Fix frequency locking on Adreno GPU • Fix module.prop corruption issue • GPU frequency now will be locked at high frequency on performanc

🔥7216❤‍🔥1👍1

Signed Rem01 Gaming

27 Jun 2026, 12:39 UTC≈11,200 views80 reactionsread 29 August 2026
Photo

Changes On Upcoming Encore Tweaks 5.2 We’re rolling out some important refinements in the next update — focused on reliability, clarity, and a smoother user experience. Here’s what’s changing: Monitoring daemon changes We are dropping the Java companion daemon in favor of direct binder monitor on native C++. It is significantly lighter on system resources and theoretically provides a much more reliable background

🔥4528👍6👏1

Signed Rem01 Gaming

14 May 2026, 08:25 UTC≈15,400 views42 reactionsread 29 August 2026
Photo

Encore Bypass Charging 2.0 is Here Enable bypass charging automatically when playing games, protecting battery health during game sessions. Changelog • Improve bypass charging test • Fix bypass charging reset on charger disconnect • Security patches • Other misc changes and optimizations Note Not all device or kernel support bypass charging, please test the bypass charging by installing the module before paying.

36🔥6

Signed Rem01 Gaming

4 May 2026, 11:50 UTC≈17,000 views61 reactionsread 29 August 2026
Photo

Amber Thermal 2.0 is Here A smart thermal module that automatically disables thermal throttling when playing games. Changelog • Massive internal refactoring and code migration • Fix thermal services not disabled • Fix thermal throttling on Xiaomi devices • Security patches • Other misc changes and optimization 🌐 Chat Group 📥 Download 💳 Pricing 🧑‍💻 Rem01 Project

🔥3718🕊3🥰3

Signed Rem01 Gaming

20 Apr 2026, 08:38 UTC≈16,600 views137 reactions2 Starsread 29 August 2026
Photo

Encore Tweaks Reached 100k All Time Downloads on GitHub! I am thrilled to announce that Encore Tweaks has reached a major milestone of 100k downloads on GitHub. What started as a small project has grown into a tool used by thousands worldwide. Thank you to all the contributors and users for your continued support and trust in Rem01 Project. 🌐 Chat Group 🌐 Website ✨ Support My Project 🧑‍💻 Rem01 Project

101🔥32👌3🤔1

Signed Rem01 Gaming

19 Apr 2026, 08:03 UTC≈14,900 views28 reactionsread 29 August 2026

What's the solution? "I don't want Encore's Tweaks but I need Amber Thermal" We understand that some users may want specific addons like Amber Thermal without applying the full Encore Tweaks suite. To accommodate this, we are introducing a "Disable Tweaks" feature. This allows you to turn off all core Encore optimizations while still providing the necessary framework for your preferred addons to operate. Please no

24🔥2👀1👏1

Signed Rem01 Gaming

19 Apr 2026, 08:03 UTC≈13,000 views20 reactionsread 29 August 2026
Photo

Important Changes Upoming to Encore Tweaks Addons and Moving Forward We're planning to update Encore Tweaks Addon modules such as Amber Thermal and Bypass Charging. however, due to the sheer complexity of current Encore Tweaks, we're forced to eliminate the internal monitor on these addon modules. What This Means for You With Encore Tweaks: If you use Encore Tweaks alongside these addons, everything will continue

19👀1

Signed Rem01 Gaming

18 Apr 2026, 08:25 UTC≈11,100 views40 reactionsread 29 August 2026
Photo

We Are Adding an End User License Agreement for Paid Modules Hi everyone, we're adding an EULA for paid Encore Tweaks addon modules such as Amber Thermal and Bypass Charging. This EULA governs your use of these modules and contains important terms regarding liability, data collection, license revocation, refund policy, and your legal rights. Sesuai dengan hukum Indonesia yang berlaku, termasuk UU No. 24/2009 tentan

17🤔16❤‍🔥4🤯3

Signed Rem01 Gaming

Showing the 12 most recent of 22 posts we hold for @rem01schannel. 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.

Citation-graph rank

Citation-graph rank — 211,027 of 1,628,927entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

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.

Appears in Telegram’s recommendations for other channels

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.

Magisk alpha
@magiskalpha · 65,449
Telegram ranks this channel #38 of 40 here — alongside 39 others — read 21 August 2026

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.

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 31 August 2026 — this entry's latest reading, not the date you are reading this.

“Rem01 Project” (@rem01schannel), 10,766 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/rem01schannel.

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.