Channel
@MoZoiDStack
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
767subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002297479547 |
|---|---|
| Type | Channel |
| Username | @MoZoiDStack |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/MoZoiDStack |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 10:31 | 767 | no change |
| 8 Aug 2026, 23:30 | 767 | first reading |
17 posts held, back to 11 October 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 22 March 2026. An engagement rate over an empty window would be a number about nothing.
145 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 49.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 71 | 49.0% | |
| ❤ | 59 | 40.7% | |
| 👍 | 12 | 8.28% | |
| 🥰 | 2 | 1.38% | |
| 👌 | 1 | 0.69% |
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 15 of the 17 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 145reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 11 October 2025 to 22 March 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.
Storage Fixer for A16 QPR1+ Roms I think this app does much more thorough job with fixing storage issues for android folder in A16 QPR1+ Roms https://github.com/omersusin/StorageFixer/releases/tag/v3.0
🔥8❤4
797 GPU drivers for A640 v11.1 You can find files and instructions in the original post for 797 drivers https://t.me/MoZoiDStack/100 ->KSUNEXT 3 Users also need to install a meta module "mountify" or "Hybrid Mount" -> 11.1 update only addresses module id issue on ksunext 3 and above. No other changes ->v11.1 has A740 gpu spoof(higher refresh rates unlocked in games) and works fine on A11 to A16 qpr2. Enjoy!
❤9🔥3👍2
Script to fix android/data folder access bug in A16 qpr1-2 roms OP: https://t.me/MoZoiDStack/147 There is a weird bug in a16qpr1-2 roms where apps are unable to access their respective folders in android/data. This causes random issues in all apps like insbility to acess files or run correctly Warning: Dont accidentally delete whole Android folder. You will lose important media files from apps like whatsapp and che…
🔥5❤4
Konabess FINAL Revamped GPU Frequency profile Guide and OP: https://t.me/MoZoiDStack/2 So with v2 FINAL of revamped file, I conclude my final work on gpu frequencies for our device, never to be touched again. Logic being that power usage difference for 340 is like 0.1-0.3 %/hr compared to using a very low frequency. This would give overall fluid ui with undetectable drain increases. Freq stepped down to 340 from 3…
❤11🔥11
GMS Component Disable Script v15 released OP: https://t.me/MoZoiDStack/137 1. Run GMS_Enable_MoZoiD_v15 file in mt manager(click on file-click preferences-Enable 'execute with root permission'-execute)or FKM 2. Clear "Cache" of Google Play Services. Reboot. 3. Now run GMS_Disable_MoZoiD_v15 file 4. Reboot Changelog : -No GMS notifications delay -No functions seem affected after exhaustive testing. -Disable componen…
👍4🔥2
MODULE UPDATE: Optimal Fast Charge v2.2 by MoZoiD Any users who face charger disconnection/connection loop issue with v2.2 will have to use the following module.(very rare for some chargers) Limit Charging Speed - 3600 mah Changelog: -Fixed inconsistent fast charge in 2.1 update. Added note: Busybox module not needed. (Thanks to NumaanMustaq for testing across various roms) -Fixed issue with disappearing module in…
🔥15❤3👍1
MODULE UPDATE: Optimal Fast Charge v2.1 by MoZoiD Changelog: - Added note: Some roms like Axion may need Busybox module for this to work correctly (Thanks to NumaanMustaq for letting me know about issue) -Fixed issue with disappearing module in magisk.(v2.1) (Thanks to SonGoku for letting me know) -Fixed issue with charging connection/disconnection loop on some Xiaomi and samsung fast chargers. Thanks to @Spark2257 …
🔥10❤2👍2
Optimal Fast Charge v2 by MoZoiD released Changelog: -Fixed issue with charging connection/disconnection loop on some Xiaomi and samsung fast chargers. Thanks to @Spark2257 for letting me know about the issue. Original Post: Optimal Fast Charge v2 by MoZoiD https://t.me/MoZoiDStack/85
🔥4❤3
GMS Component Disable Script v14 released OP: https://t.me/MoZoiDStack/137 1. Run GMS_Enable_MoZoiD_v14 file in mt manager/script manager/fkm 2. Now run GMS_Disable_MoZoiD_v14 file 3. Reboot Changelog: -Fix payment redirection to gpay not working correctly during play store app purchase -Further fixes for play Store purchases payment options section -Component discovery and firebase index components are enabled for…
🔥4
GMS Component Disable Script v13 released OP: https://t.me/MoZoiDStack/137 1. Run GMS Enable MoZoiD v13 file in mt manager/script manager/fkm 2. Now run GMS_Disable_MoZoiD_v13 file 3. Reboot Changelog: -Fix payment redirection to gpay not working correctly during play store app purchase Testers: NumaanMustaq and X-Man for thoroughly testing functionalities in v12 in daily usage
🔥2👍1
GMS Drain Script OP: https://t.me/MoZoiDStack/137 Warning: I am not responsible for any issues that arise out of using this script. Use at your own risk This script disables many Google Play services component processes improving battery life and smoothness without any GMS notifications delay. 1. Run the GMS_Disable_MoZoiD_v15.sh script in a root file manager like mt manager (Click on file-click preferences-Enable…
❤13👌1👍1
File, posted without a caption
Showing the 12 most recent of 17 posts we hold for @MoZoiDStack. 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 — 654,014 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.
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.
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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“MoZoiD Stack” (@MoZoiDStack), 767 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/MoZoiDStack.
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.