Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 89% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
32 measurements spanning 43 days, net -264. 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 15,760–16,104 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)
Subscribers
Change
18 Sept 2026, 22:15
15,800
-15
16 Sept 2026, 14:00
15,815
-22
14 Sept 2026, 16:18
15,837
-4
13 Sept 2026, 04:01
15,841
-9
11 Sept 2026, 07:57
15,850
-14
8 Sept 2026, 14:39
15,864
-20
5 Sept 2026, 04:57
15,884
-11
3 Sept 2026, 10:15
15,895
-10
2 Sept 2026, 04:01
15,905
-6
1 Sept 2026, 00:37
15,911
-4
31 Aug 2026, 00:35
15,915
-6
30 Aug 2026, 03:57
15,921
-3
29 Aug 2026, 05:03
15,924
-6
28 Aug 2026, 03:17
15,930
-3
27 Aug 2026, 01:06
15,933
-6
26 Aug 2026, 04:13
15,939
-2
25 Aug 2026, 02:33
15,941
-17
23 Aug 2026, 16:37
15,958
-14
21 Aug 2026, 23:48
15,972
-7
20 Aug 2026, 19:12
15,979
first reading
Engagement
21 posts held, back to 20 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 54 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
17.0%
avg views ÷ 15,800 subscribers
Avg views / post
2,690
1 post measured
Reaction rate
1.30%
reactions ÷ views · ER floor
Posts in window
1
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 28 August 2026
Posts held
21 (20 February 2026 – 28 August 2026)
Views total
2,690
Reactions total
35
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 10:12 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
Video runtime
2m 04s
Average length
1m 02s
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
854 reactions across 21 posts, in 9 distinct kinds. The most used accounts for 55.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
471
55.2%
🔥
158
18.5%
👍
72
8.43%
😁
53
6.21%
😱
41
4.80%
🤯
35
4.10%
👏
10
1.17%
🤔
9
1.05%
🥰
5
0.585%
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 21 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 854 reactions 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 20 February 2026 to 28 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.
Apple make some Patches for A12 & A13 Hello Mode Bypass ramdisk
What You Need to Know!
You might notice some apps throwing errors or behaving unexpectedly after the patch for bypass hello modo.
The good news:
some developers have already pushed fixes, so keep your apps updated.
@myicloud1nfo
New Lanrui V587 engineering usb adapter for iPhones
Auto DFU MODE plug&play
No need to unplug or shut down the phone. You can easily switch to recovery mode, DFU mode, or use the one-button restart feature from the main screen. No need to remove the battery to force a reboot when your phone gets stuck
https://youtube.com/shorts/Z4zg8PaES6M?feature=share
⚔ FIRST IN THE WORLD⚔
🔥 NEW UPDATE 🔥
🔤 HFZ Activator Ramdisk
-Bypass Iwatch (Hello screen) One click
-support watchOS 10.5 to 10.6.2
🚀Supported Models🚀
-Apple Watch Series SE
-Apple Watch Series S4
-Apple Watch Series S5
How to use ?
0. Put apple watch into AWRT adapter. iBUS, MagicAWRT, Apple AWRT, JCID AWRT, ...
1. Connect device in recovery mode
2. Run precheck
3. enter dfu
4. pwn with pico
5. boot ramdi…
iSkorpion - iOSTool v8.1
Windows / Mac / Linux
On of most stable Multitools for iOS Repair tools
-Bypass A5 up to A11
-Bypass A12+
-MDM bypass
-Open Menu
-Free Erase for A12 A13 models (need USBLITER8)
And More ...
Now support A12 - A13
What's New:
• ⚡️MagicCFG/Purple/SpongeBob Mode up to 11 Pro Max "FREE" ⚡️
• ⚡️Erase Xs to 11 Pro Max (USBLITER8) "FREE"⚡️
• Fixed PWNDFU for Checkm8 Devices
• Enhanced Overall stab…
Apple News update
Important info for old models
If you have any 32-bit cellular devices (iPhone 5c and earlier, or iPad 4 or earlier), DO NOT ATTEMPT TO RESTORE YOUR DEVICE. Apple has unsigned ipsw / baseband every version including the latest for all cellular A6 devices, all cellular A5 devices except for iPad2,2, and the iPhone 4 CDMA has also been unsigned, with other A4 devices likely to follow. It is currently …
Free A12 & A13 Passcode Erasing Tool Released - bobik_eraser
A new free utility has been released for the iOS repair and research community, allowing users to erase the passcode screen on supported A12 and A13 devices and restore them to the Hello (activation) screen and Keep old iOS.
Download :
https://myicloud.info/free-a12-a13-passcode-erasing-tool-released/
follow for more: @myicloud1nfo
Usbliter8 a novel sophisticated USB controller exploit that breaks SecureROM on A12, A13, S4/S5, AND A12X/Z (UNTESTED) chips Apple devices, “unpatchable”
full documentation:
https://github.com/prdgmshift/usbliter8
https://ps.tc/pages/blog-usbliter8.html
what we can have soon?
Jailbreak on latest iOS
Passcode bypass for this models
Bypass on latest iOS
New Purple Mode
Tested:
👉 iPhone XSiPhone XS MaxiPhone XRiPad A…
The IMPOSSIBLE Happened! New iOS BootROM Exploit RELEASED (A12 & A13) - iOS 27 JAILBREAK Now Possible (usbliter8)
Similar to checkm8, it requires a USB, it can load firmware, PaleRa1n-like JB is now possible forever on iPhone XS, XR, 11, SE 2
New tools soon stay tuned
@myicloud1nfo
The Premium Solution for Wi-Fi iPads has Arrived.
Wi-Fi iPad Only
🚀 Now Available: The Premium Wi-Fi iPad Solution
⚡ Powerful New Technology.
🔥 The Solution Everyone Has Been Waiting For.
🎯 Unlock Your Wi-Fi iPad Today.
Make sure you deal only with trusted and verified dealers, or you may get scammed.
Extremely low prices, anonymous sellers, fake groups, and unrealistic promises are all red flags.
Always verify who…
New iOS26 lock screen glitch 2026
https://youtube.com/shorts/wiS4oB8XIxg
The lockscreen becomes available for a few seconds when you call emergency services and go to the home screen via shortcut , you can not really use the phone and nothing to do with icloud bypass but might be possible do many other things if you explore this glitch.
follow for more @myicloud1nfo
❤22👍5😁4
Showing the 12 most recent of 21 posts we hold for @myicloud1nfo. 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
Named by 2 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
@myicloud1nfo 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.
@myicloudinfo named in 8 posts, 8 August 2026 – 3 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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“myicloud.info All About iCloud” (@myicloud1nfo), 15,800 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/myicloud1nfo.
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.