Telegram RegisterThe public register of Telegram

Channel

Miko Notification

@wsy666HD

On this record: Growth · Engagement · Posts · Citations · Cite this entry

6,779subscribers

+13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002399793317
TypeChannel
Username@wsy666HD
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/wsy666HD

Growth

6,7656,7796,7727 August 2026 — 6,766 subscribers7 August 2026 — 6,765 subscribers10 August 2026 — 6,777 subscribers14 August 2026 — 6,779 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net +13. 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 6,763–6,781 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:466,779+2
10 Aug 2026, 23:086,777+12
7 Aug 2026, 19:316,765-1
7 Aug 2026, 10:456,766first reading

Engagement

18 posts held, back to 27 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 10 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.0%
avg views ÷ 6,779 subscribers
Avg views / post
1,700
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
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
WindowRolling 30 days · latest post in window 7 August 2026
Posts held18 (27 January 20267 August 2026)
Views total8,487
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:46 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.

Recent posts

7 Aug 2026, 08:23 UTC967 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

sh 造梦无双伤害倍率.sh 10 只测了宝塔和主线(25倍) 别开太高有人造6开999拉闸了

Signed k0nf1g

7 Aug 2026, 05:16 UTC≈1,060 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

造梦西游6伤害倍率修改脚本 请以Root权限执行(默认倍率为2) 或通过终端以详细参数启动 ./造梦西游6伤害倍率修改.sh 10 请勿在多人模式使用此脚本 我也不知道会发生什么 @MikoCIBuilds

Signed k0nf1g

4 Aug 2026, 13:28 UTC≈1,720 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

仅作测试版本 新增 自动抢红包/自动收款 领取通知 新增 自动抢红包/自动收款 领取后私聊 新增 自动抢红包/自动收款 关键词抢/不抢 新增 聊天记录总结 新增 以图片形式打开表情 新增 语音转发 微信原生界面/Compose界面 新增 移除通话时聊天限制 新增 状态防删除 新增 拦截朋友圈广告 新增 朋友圈自动点赞 新增 微信mcp 新增 显示消息详情支持显示脱敏实名 新增 自定义气泡 新增 美化会话列表 新增 系统浏览器 新增 语音转文字 新增 聊天分组标签 优化 js脚本 移除 半年时间锁 优化 模块体积 ...

Signed k0nf1g

30 Jul 2026, 22:57 UTC≈2,720 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

测试版本,有BUG请到评论区反馈,赞赏用户数据未同步,无法正常显示用户信息 https://t.me/+taxeUPGZwpA5OTE1

Signed kyousuke

28 Jun 2026, 15:09 UTC≈5,670 viewsread 12 August 2026
Forwarded from @MikoCIBuilds

出北京去天津了,已经拿到我的笔记本,晚上开始coding https://t.me/+taxeUPGZwpA5OTE1 为了加快开发进度,特创建测试组用于测试模块稳定性和提供建议,测试组完全免费且随时解散,有兴趣参与模块测试的用户可以尝试加入 然后就是,感谢两位朋友在我旅游的时候帮我编写后端和UI控件,我们会更好

Signed 小明

30 May 2026, 09:30 UTC≈9,730 viewsread 12 August 2026
File

显示消息时间增加自定义大小 by 小明 新增清理 QQ 缓存 by 玄鹤zZ 修复屏蔽弹出动画在 QQ9.2.80 上失效 支持自定义精简快捷栏按钮 重构 UI 布局并在多个页面集成搜索功能 修复 QQ9.2.80 以上私聊上传文件重命名失效 修复 QQ9.2.25 左右版本屏蔽新版QQ秀失效 梵高死后人们才会开始欣赏他的作品......

Signed 可敬

19 Apr 2026, 07:48 UTC≈9,950 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

修复 微信8.0.70打开设置闪退问题

Signed 可敬

21 Feb 2026, 10:06 UTC≈13,100 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

新增 联系人-聊天归拢 修复若干问题 后续应该不再更新

Signed 小明

15 Feb 2026, 15:32 UTC≈10,800 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

临时版本 1.为所有用户解锁自动抢红包和自动收款 2.修复8.0.68+自动收款失效(Hd) 3.各位新年快乐

Signed 北敬

15 Feb 2026, 15:04 UTC≈9,470 viewsread 12 August 2026
Forwarded from @MikoCIBuilds

暂时先别通过网站赞赏,服务器一直在遭受攻击,那没办法了毕竟我也要过年,大概过几个小时我会发一个临时版本附带抢红包和自动收款功能。有效期七天。没办法毕竟技术不行人家一直打你能说什么(๑•̌.•̑๑)ˀ̣ˀ̣

Signed 北敬

9 Feb 2026, 16:44 UTC≈9,250 viewsread 12 August 2026
Forwarded from @MikoCIBuildsFile

修复 未激活的问题 新增 游戏作弊(LonDon Ryan) tip: 8.0.69的设置混淆没有变动,可以放心升级8.0.69

Signed 北敬

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

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.

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

“Miko Notification” (@wsy666HD), 6,779 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/wsy666HD.

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.