Telegram RegisterThe public register of Telegram
Telegram profile photo for ios|dump

Channel

ios|dump

@iosdumpzzz

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

16,919subscribers

+1,825 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002559880678
TypeChannel
Username@iosdumpzzz
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/iosdumpzzz

Topic

Software piracy — 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 94% 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 the other topics.

Growth

15,09416,91916,006.56 August 202610 November 2026
64 measurements spanning 96 days, net +1,825. 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 14,820–17,193 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 12:3616,919+17
8 Nov 2026, 23:4716,902+29
7 Nov 2026, 13:0116,873+16
6 Nov 2026, 16:2016,857+18
5 Nov 2026, 16:0616,839+51
4 Nov 2026, 12:5116,788+54
3 Nov 2026, 09:5516,734+8
2 Nov 2026, 11:0516,726+10
1 Nov 2026, 10:0616,716+7
31 Oct 2026, 12:0716,709+5
30 Oct 2026, 10:2816,704+8
29 Oct 2026, 11:0516,696+9
28 Oct 2026, 11:0916,687+7
27 Oct 2026, 11:3616,680+24
26 Oct 2026, 09:3116,656+11
25 Oct 2026, 05:5716,645+6
24 Oct 2026, 06:4416,639+7
23 Oct 2026, 07:5016,632+8
22 Oct 2026, 06:1816,624+22
20 Oct 2026, 20:1916,602first reading

Engagement

59 posts held, back to 29 July 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 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
36.8%
avg views ÷ 16,919 subscribers
Avg views / post
6,220
8 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
8
of 59 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
WindowRolling 30 days · latest post in window 7 November 2026
Posts held59 (29 July 2026 – 7 November 2026)
Views total49,780
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 16: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
29
Videos
8
Links
70

Lifetime counters from Telegram’s own channel header, read 11 November 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
25s
Average length
13s

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.

Recent posts

Telegram’s own ‘edited’ marker: 4 of 8 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 06:14 UTC≈3,420 viewsread 11 November 2026
File

测试哔哩哔哩 9.18.0 无设置项默认去广告、支持保存视频内容包括动漫 影视 播放视频右上角三点按钮菜单或分享按钮菜单内触发下载

5 Nov 2026, 01:47 UTC≈4,730 viewsread 11 November 2026
File

无设置项,支持保存图片/视频/实况图跟防撤回消息

5 Nov 2026, 01:46 UTC≈4,310 viewsread 11 November 2026
File

0.0.3 改成三指双击呼出设置页 修复无法保存部分实况 修复保存部分视频无声音

14 Oct 2026, 12:02 UTC≈10,500 viewsread 11 November 2026
Forwarded from @nixiangyepFile

解锁完整会员 https://apps.apple.com/us/app/%E4%BA%9A%E7%91%9F%E6%B5%8F%E8%A7%88%E5%99%A8-m3u8%E8%A7%86%E9%A2%91%E6%8A%95%E5%B1%8F%E5%90%88%E5%B9%B6/id1551893305?l=zh-Hans-CN

12 Oct 2026, 10:00 UTC≈10,600 viewsread 11 November 2026
File

SHELLX_11.3 1.修复分词面板标点符号丢失问题 2.优化分词面板提示气泡 3.新增长按电源键手势 4.修复手势面板卸掉的应用无法删除问题 5.图片/文本记录限制修改为自定义与无限制张数设置,之前无限制设置自定义张数后原有无限制记录不会删除按照现有记录条数开始计 6.新增水印截图指令:prefs://root=shellx_wm 7.记录面板收藏页新增左滑可备注 8.优化手势菜单系统图标某些场景下看不清问题 9. 修复app浮窗导致底部白条手势失效的问题 10.新增sbtrim内存优化,大幅度降低内存占用减少因内存占用高sb被杀问题 11.新增可在设置键盘听写按钮用来呼出记录面板 12.其它优化

9 Oct 2026, 16:53 UTC≈9,470 viewsread 11 November 2026
Forwarded from @nixiangyepFile

解锁永久会员 https://apps.apple.com/app/id6448362669

6 Oct 2026, 06:38 UTC≈10,600 viewsread 11 November 2026
File

JumpSelect_1.3 1.新增跳转面板兼容横屏 2.修复通过Safari/Shortcuts跳转时拦截失效问题

Showing the 12 most recent of 59 posts we hold for @iosdumpzzz. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 4 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.

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.

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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“ios|dump” (@iosdumpzzz), 16,919 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/iosdumpzzz.

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.