This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
7 measurements spanning 5 days, net -60. 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 46,717–46,901 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 17:24
46,738
-31
11 Aug 2026, 19:57
46,769
-48
10 Aug 2026, 22:36
46,817
-25
9 Aug 2026, 23:32
46,842
-38
8 Aug 2026, 22:11
46,880
+65
8 Aug 2026, 00:00
46,815
+17
7 Aug 2026, 14:02
46,798
first reading
Engagement
21 posts held, back to 30 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 16 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
21.2%
avg views ÷ 46,738 subscribers
Avg views / post
9,920
8 posts measured
Reaction rate
0.185%
reactions ÷ views · ER floor
Posts in window
8
of 21 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
Window
Rolling 30 days · latest post in window 11 August 2026
Posts held
21 (30 June 2026 – 11 August 2026)
Views total
79,360
Reactions total
147
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 19:57 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.
What this channel posts
Photos
925
Videos
61
Links
997
Lifetime counters from Telegram’s own channel header, read 12 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
31s
Average length
16s
Measured directly from 2 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
1,911 reactions across 19 posts, in 17 distinct kinds. The most used accounts for 44.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
842
44.1%
🔥
391
20.5%
🥰
214
11.2%
🤩
200
10.5%
👍
105
5.49%
🕊
39
2.04%
😘
20
1.05%
😍
19
0.994%
❤🔥
16
0.837%
💋
12
0.628%
⚡
10
0.523%
🎉
10
0.523%
🏆
10
0.523%
💯
10
0.523%
🍾
8
0.419%
👌
3
0.157%
👏
2
0.105%
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 19 of the 21 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 1,911reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 30 June 2026 to 11 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.
𝗚𝗠𝗦 - 𝗢𝗣𝗧𝗜𝗠𝗜𝗭𝗘𝗥 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝗘𝗢𝗟-𝟰
G-Play-Service-Optimizer restricts Google Mobile Services background processes and permissions to reduce battery drain and improve system performance.
📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 :
• Detailed release.
📋 𝗡𝗼𝘁𝗲𝘀 :
• Downloads | Screenshot
• kazuyoo-stuff.github.io
• More information.
# Thanks For Using, Support My Project.
𝗖𝗘𝗟𝗘𝗦𝗧𝗜𝗔𝗟-𝗥𝗘𝗡𝗗𝗘𝗥-𝗙𝗟𝗢𝗪𝗫 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝟮.𝟮
Celestial Render FlowX is a rendering optimization module designed to improve graphics processing efficiency and speed up the rendering pipeline on Android.
📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 :
• Detailed release.
📋 𝗡𝗼𝘁𝗲𝘀 :
• Downloads | Screenshot
• kazuyoo-stuff.github.io
• Credits & Tester
# Thanks For Using, Support My Project.
𝗚𝗔𝗠𝗘-𝗔𝗦𝗦𝗘𝗧-𝗣𝗥𝗘𝗙𝗘𝗧𝗖𝗛𝗘𝗥 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝟭.𝟱
Game Asset Prefetcher (GAP) is designed to preload and lock critical game assets directly into RAM, reducing load times and storage read overhead during gameplay.
📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 :
• Detailed release.
📋 𝗡𝗼𝘁𝗲𝘀 :
• Downloads | Screenshot
• kazuyoo-stuff.github.io
• Information & Credits
# Thanks For Using, Support My Project.
𝗖𝗘𝗟𝗘𝗦𝗧𝗜𝗔𝗟-𝗗𝗜𝗦𝗔𝗕𝗟𝗘-𝗟𝗢𝗚 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝟭.𝟱
Celestial Disable Log is designed to disable non-essential Android logging, tracing, and telemetry collection to reduce background I/O load while keeping the system stable and responsive.
📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 :
• Detailed release.
📋 𝗡𝗼𝘁𝗲𝘀 :
• Downloads | Screenshot
• kazuyoo-stuff.github.io
• Credits
# Thanks For Using, Support My Project.
𝗨𝗡𝗜𝗦𝗢𝗖-𝗣𝗥𝗜𝗢𝗥𝗜𝗧𝗬-𝗨𝗙𝗪 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝟭.𝟯
Unisoc-Priority-UFW is a foreground-aware daemon that dynamically boosts scheduling, I/O, and thread priority via Unisoc's UFW controller to keep gameplay smooth.
📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 :
• Detailed release.
📋 𝗡𝗼𝘁𝗲𝘀 :
• Downloads | Screenshot
• kazuyoo-stuff.github.io
• Click action to get more information.
# Thanks For Using, Support My Project.
𝗖𝗘𝗟𝗘𝗦𝗧𝗜𝗔𝗟-𝗚𝗔𝗠𝗘-𝗢𝗣𝗧 | 𝗨𝗣𝗗𝗔𝗧𝗘 𝟯.𝟮
Celestial Game Opt for designed to enhance Android game performance while preserving system stability and responsiveness.
📧 𝗖𝗵𝗮𝗻𝗴𝗲𝗹𝗼𝗴𝘀 :
• Detailed release.
📋 𝗡𝗼𝘁𝗲𝘀 :
• Downloads | Screenshot
• kazuyoo-stuff.github.io
• Credits & Information.
• Wait a few minutes after uninstall then reboot.
# Thanks For Using, Support My Project.
Update SpeedX will be carried out on Monday this week. The SpeedX update process is currently underway.
🥰195❤69👍47🤩44🕊25🔥15❤🔥8🍾7
Signed Aldo Rafael Rizki
Showing the 12 most recent of 21 posts we hold for @ChermodzsModule. 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 — 45,556 of 1,151,006entries 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 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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@ChermodzsModule named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@nekotor1 named in 4 posts, 8 August 2026 – 12 August 2026
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.
“CHERMODZS” (@ChermodzsModule), 46,738 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ChermodzsModule.
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.