本周赛博领鸡蛋(11.6~11.12):《遗忘国度:放置勇士》《浮游世界》《巴别塔圣歌》 via 小众软件

Channel
zrj766的频道
@zrj96
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
17,787subscribers
+1,098 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 | -1001141209746 |
|---|---|
| Type | Channel |
| Username | @zrj96 |
| Description | 🤝 特别感谢NodeSupport和YxVM @yxvmcom 对本频道的赞助和支持。 🌏 个人小店:https://my.766im.com 😀 兴趣杂食向频道,有时候会当朋友圈用,不喜勿喷,友善交流; 🤖 主要内容:手机数码,VPS/独服,蚊子腿毛,热点资讯,沙雕图等; ⛔️ 不接推广,转发商业内容仅为体验后推荐。 |
| Created | 4 August 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/zrj96 |
Topic
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 85% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 06:46 | 17,787 | +6 |
| 5 Nov 2026, 06:57 | 17,781 | +8 |
| 4 Nov 2026, 05:27 | 17,773 | +11 |
| 3 Nov 2026, 04:07 | 17,762 | +9 |
| 2 Nov 2026, 05:09 | 17,753 | +25 |
| 1 Nov 2026, 06:31 | 17,728 | +8 |
| 31 Oct 2026, 09:27 | 17,720 | +12 |
| 30 Oct 2026, 09:55 | 17,708 | +19 |
| 29 Oct 2026, 10:41 | 17,689 | +6 |
| 28 Oct 2026, 11:17 | 17,683 | +3 |
| 27 Oct 2026, 13:50 | 17,680 | +12 |
| 26 Oct 2026, 14:30 | 17,668 | +21 |
| 25 Oct 2026, 13:05 | 17,647 | +18 |
| 24 Oct 2026, 11:17 | 17,629 | +16 |
| 23 Oct 2026, 10:29 | 17,613 | +6 |
| 22 Oct 2026, 13:01 | 17,607 | +24 |
| 21 Oct 2026, 05:46 | 17,583 | +18 |
| 20 Oct 2026, 05:29 | 17,565 | +22 |
| 19 Oct 2026, 01:45 | 17,543 | +11 |
| 18 Oct 2026, 05:01 | 17,532 | first reading |
Engagement
526 posts held, back to 5 August 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 62 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 14.1%
- avg views ÷ 17,787 subscribers
- Avg views / post
- 2,500
- 63 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 63
- of 526 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.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 526 (5 August 2026 – 6 November 2026) |
| Views total | 157,690 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 16:01 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
- ≈8,780
- Videos
- ≈246
- Links
- ≈24,900
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 7m 15s
- Average length
- 33s
Measured directly from 13 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
4,650 reactions across 284 posts, in 44 distinct kinds. The most used accounts for 32.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 1,527 | 32.8% | |
| 💩 | 713 | 15.3% | |
| 🤡 | 340 | 7.31% | |
| 👍 | 332 | 7.14% | |
| 🤣 | 308 | 6.62% | |
| ❤ | 170 | 3.66% | |
| 😭 | 145 | 3.12% | |
| 👎 | 122 | 2.62% | |
| 🥰 | 99 | 2.13% | |
| 🙏 | 86 | 1.85% | |
| 🤮 | 84 | 1.81% | |
| 🤬 | 71 | 1.53% | |
| 😱 | 51 | 1.10% | |
| 💅 | 42 | 0.903% | |
| 😇 | 42 | 0.903% | |
| 🤓 | 40 | 0.86% | |
| 🤯 | 38 | 0.817% | |
| 🤔 | 37 | 0.796% | |
| 🆒 | 36 | 0.774% | |
| 🔥 | 34 | 0.731% | |
| 24 further kinds | 333 | 7.16% |
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 314 of the 526 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 4,797 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 526 most recent posts we hold, published 5 August 2026 to 6 November 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
Telegram’s own ‘edited’ marker: 4 of 63 posts held from the last 30 days (6.35%) 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).
著名 Mac 菜单栏日历 Itsycal 更新:现在可以显示苹果提醒事项了 via 小众软件
宝藏 Mac 工具 NotchNook 满血复活 via 小众软件
JCloudHosting 西班牙产品 测评 via MeowVPS
不过了
小米18U 已取消 Find X10U 项目暂停
群晖发布教程:保护 NAS 免受勒索软件攻击 via 小众软件
OpenSSH 爆出 10 年老漏洞:输入超长密码,就能绕过 SSH 登录验证|CVE-2026-123158 via 小众软件
小米17 Max也差不多这个价了,16+512国补后3719,和K100PM对比,拿掉BOSE喇叭、更大的电池和新屏幕,换一个更好的影像算法,以及正面窄边框。 淘宝百亿补贴好像更便宜,3499?不过得准点领金刚券啥的,不是很好抢。
荣耀700系列预热,全系原生1.72英寸背屏 6.57英寸 1.5K 四等边 1.72英寸背屏 最大9000mAh电池+80W有线快充 200Mp主摄+50Mp潜望长焦,支持200mm增距镜 700S、700标准版(8s Gen4)、700 Pro(8 Gen5)
https://www.v2ex.com/t/1254864
Debian 13配置Nginx启用HTTP/3 via 荒岛
Showing the 12 most recent of 526 posts we hold for @zrj96. 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.
Posts edited after publishing
@zrj96 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 22 August 2026
- Most recent edit
- 22 August 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 51 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
@funny_fyj · 58 posts今天abc看了啥🤔
@abcthoughts · 7,1327 posts//iplc.best 搬运分享
@iplc_best_share · 337 posts季悠然の垃圾桶
@pr_233 · 27 postsLᴜᴄʏ
@LUCYChannel_1024 · 7,9784 postsVPStry 推送频道
@vpstry · 1,0184 posts缤纷世界的彩色冒险
@bunte_Welt · 7,2913 postsShare some interesting things | CTCGFW's Channel
@ctcgfw_sbsays · 1983 posts鲜橙汁真的好喝
@ouuomi · 793 postsmoenjoy
@oxyTG · 1333 posts733 Tech Tips (Public)
@tech_tips_733 · 7613 posts1024社区 | 1024.day
@Hello_1024 · 12,4802 postsMarkson 的梦话空间
@MarksonHonSaid · 3282 posts2.5次元日常 🍉
@acgdaily · 17,2502 posts我喜欢你
@bakaPD · 10,8432 posts搞机助手·R 官方频道
@gjzsr_channel · 15,7292 posts惶心 Monologue ™
@huangxinn · 1822 postsアミナ・コイムのひみつ基地
@meme_sammlung · 3,3272 postskaze channel
@rclogs · 852 postsVPSMarket-channel
@vpsmarkets · 6,7982 posts主机百科资讯分享
@zhujiwiki_info · 10,6722 posts果果家的报刊栏
@Guoguo · 3671 post这是一个正经的羊毛频道🐑
@LetsBaa · 811 post🐱MiaoTony's Box | 困困困 zzz
@MiaoTonyChannel · 1,9091 postMirraの杂货铺 | Link to HUAWEI!
@NekoMirra · 1,3451 post<NullPointerException> 二周目
@NullPointerA · 9201 postPika广播电台 | 上班中
@PikaRadio · 1201 post特价VPS分享
@Tjjcfx · 17,8761 post听荼蘼逼逼 | 多打点🤡
@TomyJan_Channel · 3,6601 postAlex的数字难民营地 🏕️
@alexzkcom · 3551 post得体
@all_in_ton · 81 postAPI
@apifind · 21 post老粗的杂记
@bignotes · 271 postEyte Channel
@eytechannel · 51 post泽边
@frommarshside · 3291 postgd1214b的频道
@gd1214b_channel · 771 post极客盐选
@geeksalt · 2,9281 post是芙莉莲
@iReallyHateTheWorld · 651 posttg信息分享
@jdjdlb · 1,3291 post空明明空明
@kmzs123 · 21 post𝓜𝓪𝓻𝓲𝓪的小屋
@mariaswea · 2401 post老鬼的博客(Oldking.net)
@oldkinginfo · 101 post普拉姆的胡言乱语
@plumzme · 7621 post妄想7号店/www.qiao7.xyz
@qiao7blog · 31 post纷飞的小窝
@sena_yuki_chan · 3961 post各种限免~专业白嫖
@share_free · 2,8191 post⏰ 闪购提醒
@virmach_sale · 1,1921 postFaker的个人频道
@wtfbugtoday · 3,1621 post
Republishes
Channels on the register whose posts this channel has forwarded.
@MyGo_Crychic · 924 posts蓝点网订阅频道
@landiansub · 46,9444 postsLANG=zh_CN tail -f /var/log/DMIT.log
@DMIT_INC_CN · 11,1041 post灵车漂移
@Hearse_Drifting · 10,8511 post追尾游戏热点
@Vwyxrd · 4,2761 post今天abc看了啥🤔
@abcthoughts · 7,1321 postfree347 免费资源分享
@free347 · 27,9021 postHAT's Public Channel |
@hatschannel · 3,8711 postJavDB.com
@javdbnews · 144,1441 postlowendaff
@lowendaff_blog · 6,2181 postLow End Web Deals
@lowendweb · 2,5591 postNanase的随记
@nanaselog · 4,1601 post秋名山啥都发
@qmseee · 7,5361 post小众机场测评
@sstrojan · 23,5531 post
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
@zaihuapd · 289,1289 posts在花小茶馆🍵
@zaihuaSpace · 7,3904 posts蓝点网订阅频道
@landiansub · 46,9442 postsClash by Clash Channel
@clashbyclash · 5,3441 posttail -f /var/log/DMIT.log
@DMIT_INC · 6,6161 postLoopDNS资讯播报
@DNSPODT · 73,2051 postencmasuta
@encmasuta · 13,9151 postfree347 免费资源分享
@free347 · 27,9021 postlowendaff
@lowendaff_blog · 6,2181 postOmi Mac/iOS App Channel Chat
@macappsupportgroup · 23,8131 postNanase的随记
@nanaselog · 4,1601 postSurge & Loon & QX 脚本收集
@NobyDa · 64,3871 postRFCHost Official
@real_rfchost · 12,6551 postNodeMach通知频道
@vircscom_announcements · 4,0221 postZouter.io Channel
@Zouter_Channel · 8,6691 post
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@youyousharechannel · 92,291
Telegram ranks this channel #9 of 43 here — alongside 42 others — read 17 August 2026
@cnbeta_com · 27,446
Telegram ranks this channel #10 of 55 here — alongside 54 others — read 10 September 2026
@qunyouwen · 89,086
Telegram ranks this channel #10 of 67 here — alongside 66 others — read 17 August 2026
@abskoop · 303,928
Telegram ranks this channel #11 of 50 here — alongside 49 others — read 17 August 2026
@github_2dust · 92,760
Telegram ranks this channel #12 of 71 here — alongside 70 others — read 17 August 2026
@moviepilot_channel · 19,971
Telegram ranks this channel #16 of 40 here — alongside 39 others — read 30 September 2026
@WidgetChannel · 106,905
Telegram ranks this channel #16 of 44 here — alongside 43 others — read 17 August 2026
@MlgmXyysd_bibilailai · 22,448
Telegram ranks this channel #17 of 54 here — alongside 53 others — read 23 September 2026
@scriptalking · 27,972
Telegram ranks this channel #18 of 41 here — alongside 40 others — read 10 September 2026
@projectXtls · 30,414
Telegram ranks this channel #22 of 58 here — alongside 57 others — read 8 September 2026
@chxpd · 157,108
Telegram ranks this channel #24 of 51 here — alongside 50 others — read 17 August 2026
@goworkbitch · 25,239
Telegram ranks this channel #27 of 52 here — alongside 51 others — read 15 September 2026
@mightyflame · 25,445
Telegram ranks this channel #29 of 42 here — alongside 41 others — read 13 September 2026
@Legado_Channels · 93,153
Telegram ranks this channel #29 of 61 here — alongside 60 others — read 17 August 2026
@GetSomeFriesChannel · 20,330
Telegram ranks this channel #31 of 45 here — alongside 44 others — read 29 September 2026
@nmbotchannel · 34,947
Telegram ranks this channel #36 of 42 here — alongside 41 others — read 12 September 2026
@DNSPODT · 73,205
Telegram ranks this channel #36 of 59 here — alongside 58 others — read 20 August 2026
@AI_News_CN · 23,158
Telegram ranks this channel #37 of 45 here — alongside 44 others — read 22 September 2026
@ruheyushadiaoxiangchu · 28,400
Telegram ranks this channel #37 of 44 here — alongside 43 others — read 9 September 2026
@GodlyNews1 · 70,900
Telegram ranks this channel #37 of 55 here — alongside 54 others — read 20 August 2026
@cheap_proxy · 26,271
Telegram ranks this channel #41 of 49 here — alongside 48 others — read 13 September 2026
@Nexitally_Official · 21,056
Telegram ranks this channel #42 of 44 here — alongside 43 others — read 26 September 2026
@freechinese · 27,744
Telegram ranks this channel #42 of 55 here — alongside 54 others — read 10 September 2026
@iyouport · 27,611
Telegram ranks this channel #42 of 55 here — alongside 54 others — read 10 September 2026
This channel appears in 30 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“zrj766的频道” (@zrj96), 17,787 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/zrj96.
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.