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 291–292 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Aug 2026, 01:37
291
-1
6 Aug 2026, 22:48
292
no change
6 Aug 2026, 05:47
292
first reading
Engagement
18 posts held, back to 26 December 2025 — 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.
ERR · 30 days
124.7%
avg views ÷ 291 subscribers
Avg views / post
363
2 posts measured
Reaction rate
0.964%
reactions ÷ views · ER floor
Posts in window
2
of 18 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 6 August 2026
Posts held
18 (26 December 2025 – 6 August 2026)
Views total
726
Reactions total
7
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 22:48 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
143 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 51.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
74
51.7%
🔥
44
30.8%
👏
11
7.69%
🤯
7
4.90%
👍
3
2.10%
😭
2
1.40%
💯
1
0.699%
😱
1
0.699%
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 18 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 143reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 26 December 2025 to 6 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.
LunarisAOSP | 3.12 | Baklava QPR2 | Vince_4_19
Author: 『 リュウᯓ 』
Build Date : Agustus 06, 2026
Download
Screenshot
Support
Donate
Install Steps
Changelog :
• Initial build dynamic partition
• Shiped with NaughtyKernel
• Added Viper4Android
Notes :
• Recomended use NikGapps
• Report bug with log
• Save the original link and please don't share it to keep supporting me
Known Issue :
• DT2W from kernel side
Credits :
• …
Naughty | 4.19.325 | Kernel | Mi8953
Target: Redmi S2/Y2/5/5Plus/Note 4/4X/MI 5X
Author: 『 リュウᯓ 』
Build Date: 16/07/26"
Kernel: 4.19.325-chip17-st17
Download: Github
Known Issue: https://t.me/Mi_8953/92
Changelog:
- fix fingerprint for all variant
- fix msm_vidc for sdm450
- Add Mi 5x support
- Add support 8 KSU Manager
Notes:
- Do not use more than one manager because it will cause multiple roots to be detected …
Hmm, I'm not yet sure if I'll make time if I can to work on Mi8953 device tree and other remaining devices, like markw, for kernel (since I happen to own those devices). And yeah, these devices won't be around much longer, so I'll work on them at a leisurely pace whenever I have time; the next step after that is moving to mainline.
Mi MSM8953 - Kernel | Mi8953_a
Target: Redmi S2/Y2/5/5Plus/Note 4/4X (excluding tissot/daisy/tiffany/sakura)
Kernel: 4.9.337
Download: Telegram
Initial changelog : https://t.me/me_alts/87
Notes:
• Support A11-15
• Fingerprint/Camera/frontflash is not working on Rosy (wip)
• "Tissot/Daisy/Tiffany/Sakura" will never be added here because they share the same board, and some also feature A/B versions.
Credits:
• for…
Btw, if you're interested in the mainline kernel for the mi8953 family, you can join here @aosp_mainline_playground
This is being worked on directly by the skilled developer 0xCAFEBABE.
LineageOS | 23.2 | Baklava QPR2 | Vince_4_19
Author: @AmiaAlt
Build Date: Febuary 02, 2026
Kernel: 4.19.325-cip127-st11-perf
Download: Pixeldrain
(Pixeldrain expiry: 30 days)
Changelog:
• LineageOS 23.2
• kernel: Merge LineageOS/android_kernel_qcom_sm8250
Known Issues:
• https://t.me/me_alts/92
• Bluetooth Fixed
Notes:
• Do NOT dirty flash from 4.9 Rom
• Flash use this recovery "do not use any other recovery"
C…
it worked. It's just that Bluetooth isn't working. I forgot to fix the Bluetooth, maybe tonight :D
Edit : fixed
🔥8❤4
Signed RenzAlt
Showing the 12 most recent of 18 posts we hold for @Mi_8953. 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 — 569,063 of 1,160,990entries 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.
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
@Mi_8953 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.
@me_alts named in 6 posts, 8 August 2026 – 8 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 7 August 2026 — this
entry's latest reading, not the date you are reading this.
“RenzAlt stuff” (@Mi_8953), 291 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Mi_8953.
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.
