Telegram RegisterThe public register of Telegram
Telegram profile photo for 中野三玖官方频道[副频道]

Channel

中野三玖官方频道[副频道]

@ZYSJMikui

On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

682subscribers

+274 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003999927733
TypeChannel
Username@ZYSJMikui
CreatedBetween 1 April 2026 and 8 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/ZYSJMikui

Previous handles

@ZYSJMikui was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@LH520A
held 8 August 20268 August 2026

Growth

4086825457 August 2026 — 408 subscribers8 August 2026 — 408 subscribers31 August 2026 — 561 subscribers31 August 2026 — 568 subscribers10 September 2026 — 682 subscribers7 August 202610 September 2026
5 measurements spanning 33 days, net +274. 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 367–723 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 02:17682+114
31 Aug 2026, 20:14568+7
31 Aug 2026, 11:45561+153
8 Aug 2026, 05:46408no change
7 Aug 2026, 18:43408first reading

Engagement

34 posts held, back to 8 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
58.2%
avg views ÷ 682 subscribers
Avg views / post
397
12 posts measured
Reaction rate
0.6%
reactions ÷ views · ER floor
Posts in window
12
of 34 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. It is computed over the 8 of 12 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 August 2026
Posts held34 (8 July 202631 August 2026)
Views total4,766
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Aug 2026, 11:45 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
5m 06s
Average length
1m 42s

Measured directly from 3 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

40 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 55.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2255.0%
🥰820.0%
512.5%
🔥37.50%
😭25.00%

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 16 of the 34 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 40 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 34 most recent posts we hold, published 8 July 2026 to 31 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.

Recent posts

31 Aug 2026, 11:02 UTC11 viewsread 31 August 2026
Forwarded from @HDDKNBPhoto

豆豆和平公益范围文件 🎮0.6驱杆 🎮修补低陀40% 《不封号文件优化》↓ 🌟和平FPS120\144\165帧文件正在更新 🌟三角洲脚步声文与配置文件 我用夸克网盘给你分享了「豆豆百包箱」,点击链接或复制整段内容,打开「夸克APP」即可获取。https://pan.quark.cn/s/6356e19d1bde

31 Aug 2026, 10:44 UTC5 views2 reactionsread 31 August 2026

⚠️今天我整合了挂圈各大热门频道! ❤️以下频道是挂圈热门频道大合集 1️⃣仁济改文件. 2️⃣小月改文件. 3️⃣HTY改文件. 4️⃣公益内核破解. 5️⃣TG高速公益代理. 6️⃣期九期改文件. 以下为赞助商⬇️ 低价源头1元TG账号 快手账号 QQ账号 抖音账号 微信账号 库存充足 发誓要让小学生用上质量的账号

👍2

30 Aug 2026, 03:48 UTC85 viewsread 31 August 2026
Forwarded from @KYNB666000

筷雨自动注入10.0已更新 由于和平最近强检 导致个大小学生拉10年 所以 此版本为稳定版 《点我下载10.0注入》 记得转存 以免丢失 记得搭配端口使用 官方频道 @KYNB666000

29 Aug 2026, 09:32 UTC181 views4 reactionsread 31 August 2026

私端已正式收费!要买的看置顶主卡网

👍4

26 Aug 2026, 15:47 UTC≈1,550 views7 reactionsread 31 August 2026

中野三玖私端 购买地址 http://aug786.top/s/0093AA8C 注册地址http://103.37.44.214:17002/ 🥰新增功能 自定义背景图 雪花飘落 半透明设置 整体优化 100%解决禁网问题 ✅防封区域: 文件 内存 加速 全火 半火 美化 范围 内核 纯c 注入 ✅24小时循环维护 ✅接受任何测试与测评 ✅只打造纯洁与稳定 不限速下载链接:https://pan.xunlei.com/s/VP-rWYIH52L628wIIu0H_gLYA1 提取码:pqwh 你们的支持是我前进的动力,将长期为你们公益,表情包支持

🥰7

23 Aug 2026, 10:26 UTC502 views0 reactionsread 31 August 2026

1.0出现一些bug下载游玩不影响使用晚上修复好🤔

23 Aug 2026, 06:34 UTC603 views3 reactionsread 31 August 2026
Video

三玖入侵和平avatermesh文件 ☘️[所有模式有共享枪械]↓ 🌱卓越M338 🌱卓越ACE 🌱卓越PKM 🌱雪隼AA12 🌱精致SPAS 🌱MK14🌱AUG🌱P90🌱MG3 🌱G36C🌱MG36🌱UZI🌱MP5K 🌱UMP45🌱M416🌱GROZA🌱SCARL 🌱维克托🌱蜜獾🌱DP28🌱SKS🌱SLR🌱AKM 🌱QBZ🌱AWM🌱AMR🌱法玛斯🌱ARX🌱M762🌱M249 下载讯雷网盘↓ 快速下载通道链接:https://pan.xunlei.com/s/VP-hIpAsm1-cv_LDxYPShGp6A1?pwd=j8a2#

🔥3

14 Aug 2026, 15:50 UTC477 views3 reactionsread 31 August 2026

招技术人员 代理 客服 能挣多少就看你们本事了 以上这三个待遇很好

👍3

13 Aug 2026, 22:52 UTC498 views1 reactionsread 31 August 2026

中野三玖内核为你保驾护航 ➡️【手续费提卡网】:http://aug786.top/s/0093AA8C 【私端注册地址】:http://103.37.44.214:17002/ 【主网卡】:内核卡密 私端卡密 TG号[快] ➡️【0手续费副卡网】:https://wkaiw.oqzgb.com/shop/RB6RHJFH 【副卡网】:数据号 TG号[慢] 直登号 ✅【中野三玖主频道】:@ZYSJMiku ✅【中野三玖TG公益代理频道】:@TGnino520 ✅【售后服务】:@NakanoNB ✅【自瞄配置参考】:无 📊售后服务请携带订单截图·找客服给与售后服务 📊周·月·赛季用户·可以联系客服进内部V群

🥰1

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

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

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

“中野三玖官方频道[副频道]” (@ZYSJMikui), 682 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/ZYSJMikui.

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.