2 measurements taken within a single day. 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 1,393–1,395 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Sept 2026, 02:40
1,394
no change
15 Sept 2026, 03:22
1,394
first reading
Engagement
14 posts held, back to 16 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.
ERR · 30 days
114.1%
avg views ÷ 1,394 subscribers
Avg views / post
1,590
2 posts measured
Reaction rate
1.38%
reactions ÷ views · ER floor
Posts in window
2
of 14 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 22 August 2026
Posts held
14 (16 February 2026 – 22 August 2026)
Views total
3,180
Reactions total
44
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
15 Sept 2026, 03:22 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
318 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 53.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
171
53.8%
🔥
65
20.4%
👍
54
17.0%
👏
15
4.72%
👎
3
0.943%
🖕
2
0.629%
🤩
2
0.629%
🤬
2
0.629%
🥰
2
0.629%
😭
1
0.314%
🤯
1
0.314%
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 14 of the 14 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 318 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 16 February 2026 to 22 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.
📱LineageOS 24.0 | Android 17 | #Houji
▪️ Date:- 22/08/2026
✅ Flashing Instructions:-
▪️ Flash Zip via Twrp or Lineage Recovery
▪️ Format Data
▪️ Reboot
💥 Changelog :-
- initial Android 17 build
👀Download :- Link
📝Notes:
- dt2w and sofod is quirky will fix next build
- miuicamera 6.x (i forgot which one), 2x is partially working, this build compile with nothing modify
- small quirks exists, unlike other rom, i c…
As per the majority votes we are going forward with the donation drive to our dev @lilydess 🏖 for Android 17 builds and those who want to donate can donate via UPI 😀
These donations will be received by our admin Cherry who will later send it to the dev by his accepted payment method 🤩
UPI Details:- (For India)
charantej94-2@okhdfcbank
Paypal Link:- (If you are from other country you can donate directly to the dev)…
🚀 Android 17 Successfully Booted on Xiaomi 14 (Houji)!
The wait is over... we've officially achieved our first successful Android 17 boot on the Xiaomi 14 (Houji)! 🎉
This is only the beginning. Expect more updates as we work towards:
• 🛠️ Fixing remaining issues
• ⚡ Improving stability & performance
• 📱 Daily driver readiness
Stay tuned for more development updates!
Credit: @lilydess ❤️
#Android17 #LineageOS24 …
🔥 Mi8G3-Unlocker – Free
🤩Bootloader Unlock Tool for Xiaomi Snapdragon 8 Gen 3 Devices
A useful community-made Windows tool for Xiaomi devices powered by Snapdragon 8 Gen 3. It automates the bootloader unlock process through a simple script and is reported to support HyperOS builds across multiple patch levels. The project provides a one-click style workflow using ADB/Fastboot, making the process easier than traditio…
#ProjectZK #houji
ProjectZK v3.0 🔥
Maintainer: Zurimuka
🚀 Changelog
👨🦼 Screenshots
💻 Download
📝 Notes
👍Credits & Thanks:
👋@Xiaomi.eu for bases and apps
👨🦼@kashis_cringey_stuffs for alot mod apps, settings layout
👉 @lokallion, @dulquersalmaan22 for mod apps
💻@Jefino9488 for framework patcher
💻@Kousei_vn aka KaoriOS for Toolbox
😉@maianhisme2006 for some build functions
🚘@clasky_404 for some UI mods
✈️@james34602, @…
🚀 KRYPTON GPU CONTROL ⚡️
Switch OpenGL ↔️ Vulkan (No Root)
🔥 Smoother UI | Less Heat | Better Stability
✔️ System UI on Vulkan
✔️ One-click toggle
⚙️ Features:
• Scan renderer
• Enable Vulkan
• Revert OpenGL
📌 Requirements: ADB + USB Debugging
🚨 Note: Not all apps use Vulkan (normal)
📥 Download: https://drive.google.com/file/d/1IYlrvMSr8_f01OLVl4TPgWxIkagYjsfg/view?usp=drive_link
🦸 Made by THANASES
Follow:- @X…
👍6❤4🥰1
Signed Cherri
Showing the 12 most recent of 14 posts we hold for @Xiaomi14Update. 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.
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.
Handles this channel named that no longer answer
Dead references
2
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
2
vacant every time we have ever looked
@Xiaomi14Update named 2 handles 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.
@therealahrion named in 2 posts, 16 September 2026 – 16 September 2026
@tungho80 named in 2 posts, 16 September 2026 – 16 September 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 16 September 2026 — this
entry's latest reading, not the date you are reading this.
“Xiaomi 14 | Updates” (@Xiaomi14Update), 1,394 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Xiaomi14Update.
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.