王者灵宝内核(月末稳定拿标) 承诺不动任何内存 纯读取算法解密,不烧心 算法解密和谐不追180 无三方无客户端 无拉外挂180风险 题卡地址 https://shop.wuyoushuzi.cn/shop/WX70JLXC 免费体验教程 https://t.me/wzlb6688/2886 带灵宝绘制反馈即可加时6小时 官方客服 @LBNH66 点击下方加入官方TG @wzlb6688
👍58❤2😍2
Signed 灵宝

Channel
@yuyannb666
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Cite this entry
128,877subscribers
+40,487 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1003471235745 |
|---|---|
| Type | Channel |
| Username | @yuyannb666 |
| Description | 于嫣通知频道 本项目完全免费公益 随缘更新 请勿将于嫣程序 上传 转发 到微信等QQ其他大陆平台 这是违法的! 本人也不会和任何作者有合作关系! |
| Created | 11 December 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/yuyannb666 |
Gaming — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 12 other registered channels. This entry also sits inside a group of 10 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @TwT_driver/217797 Sept 2026, 06:33 UTC | @yuyannb666/15224 · this entry8 Sept 2026, 04:18 UTC | 1.00 | 22 hours |
| @yuyannb666/15558 · this entry13 Sept 2026, 04:47 UTC | @TwT_driver/2250215 Sept 2026, 06:14 UTC | 1.00 | 2 days |
| @yuyannb666/16021 · this entry20 Sept 2026, 16:58 UTC | @TwT_driver/2293720 Sept 2026, 16:58 UTC | 1.00 | under a minute |
| @TwT_driver/3060018 Oct 2026, 10:56 UTC | @yuyannb666/19870 · this entry24 Oct 2026, 06:48 UTC | 1.00 | 6 days |
| @yazinh/948527 Aug 2026, 16:31 UTC | @yuyannb666/14417 · this entry27 Aug 2026, 16:55 UTC | 1.00 | 25 minutes |
| @yuyannb666/14491 · this entry28 Aug 2026, 19:49 UTC | @yazinh/982929 Aug 2026, 03:30 UTC | 1.00 | 7.7 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @TwT_driver | 46 (8/8 hand-verifiable sample passed) | 1.00 | 7.6 hours | @TwT_driver (28–18) |
| @yazinh | 35 (8/8 hand-verifiable sample passed) | 1.00 | 12 hours | this entry (19–16) |
| @HeiXuePD | 30 (8/8 hand-verifiable sample passed) | 1.00 | 3.4 hours | @HeiXuePD (24–6) |
| @ASGA8 | 18 (8/8 hand-verifiable sample passed) | 0.99 | 5.2 hours | @ASGA8 (10–8) |
| @LinYuKernel | 39 (8/8 hand-verifiable sample passed) | 1.00 | 18 hours | this entry (30–9) |
| @Cycle1337 | 13 (8/8 hand-verifiable sample passed) | 1.00 | 5.4 hours | @Cycle1337 (8–5) |
| @yuzhou86 | 13 (8/8 hand-verifiable sample passed) | 0.98 | 4.8 hours | @yuzhou86 (7–6) |
| @luoyeco | 11 (8/8 hand-verifiable sample passed) | 1.00 | 5.5 hours | this entry (6–5) |
| @zwaaa333 | 12 (8/8 hand-verifiable sample passed) | 0.98 | 15 hours | this entry (8–4) |
| @zwaaa3 | 10 (8/8 hand-verifiable sample passed) | 1.00 | 15 hours | even |
| @DUOLEA66 | 7 (7/7 hand-verifiable sample passed) | 0.98 | 11 hours | @DUOLEA66 (4–3) |
| @ssoo66668 | 12 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | @ssoo66668 (12–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 113 of the 113 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 2,110 comparable posts for this entry, running 8 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 10 channels, the one whose matching posts we hold earliest is @yuzhou86. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 10 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 21:50 | 128,877 | +1,230 |
| 13 Nov 2026, 15:50 | 127,647 | +1,011 |
| 10 Nov 2026, 23:57 | 126,636 | +538 |
| 9 Nov 2026, 12:00 | 126,098 | +576 |
| 8 Nov 2026, 00:58 | 125,522 | +596 |
| 6 Nov 2026, 23:47 | 124,926 | +399 |
| 6 Nov 2026, 00:50 | 124,527 | +285 |
| 4 Nov 2026, 23:05 | 124,242 | +302 |
| 3 Nov 2026, 22:36 | 123,940 | +159 |
| 2 Nov 2026, 23:08 | 123,781 | +275 |
| 1 Nov 2026, 20:09 | 123,506 | +444 |
| 31 Oct 2026, 21:21 | 123,062 | +523 |
| 31 Oct 2026, 00:36 | 122,539 | +404 |
| 30 Oct 2026, 03:14 | 122,135 | +183 |
| 29 Oct 2026, 03:50 | 121,952 | +229 |
| 28 Oct 2026, 04:00 | 121,723 | +430 |
| 27 Oct 2026, 02:46 | 121,293 | +302 |
| 26 Oct 2026, 03:40 | 120,991 | +313 |
| 25 Oct 2026, 00:36 | 120,678 | +474 |
| 24 Oct 2026, 00:46 | 120,204 | first reading |
3,115 posts held, back to 11 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 224 pages of Telegram’s post history, 20 posts per page.
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 16 November 2026 |
|---|---|
| Posts held | 3,115 (11 December 2025 – 16 November 2026) |
| Views total | 1,163,202 |
| Reactions total | 99,862 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 00:40 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.
Lifetime counters from Telegram’s own channel header, read 17 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.
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.
102,433 reactions across 765 posts, in 33 distinct kinds. The most used accounts for 97.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 99,446 | 97.1% | |
| 😭 | 1,200 | 1.17% | |
| ❤ | 1,063 | 1.04% | |
| 🤔 | 215 | 0.21% | |
| 😡 | 126 | 0.123% | |
| 🔥 | 104 | 0.102% | |
| 🍌 | 60 | 0.059% | |
| 😱 | 37 | 0.036% | |
| 😍 | 35 | 0.034% | |
| 😁 | 27 | 0.026% | |
| 🤪 | 14 | 0.014% | |
| 🤯 | 14 | 0.014% | |
| 🌭 | 13 | 0.013% | |
| 🤨 | 13 | 0.013% | |
| 🍾 | 10 | 0.01% | |
| 👏 | 7 | 0.007% | |
| 👾 | 6 | 0.006% | |
| 😨 | 6 | 0.006% | |
| 🤩 | 6 | 0.006% | |
| 🤓 | 5 | 0.005% | |
| 13 further kinds | 26 | 0.025% |
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 765 of the 1,000 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 102,433 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 17 October 2026 to 16 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.
Telegram’s own ‘edited’ marker: 31 of 971 posts held from the last 30 days (3.19%) 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).
王者灵宝内核(月末稳定拿标) 承诺不动任何内存 纯读取算法解密,不烧心 算法解密和谐不追180 无三方无客户端 无拉外挂180风险 题卡地址 https://shop.wuyoushuzi.cn/shop/WX70JLXC 免费体验教程 https://t.me/wzlb6688/2886 带灵宝绘制反馈即可加时6小时 官方客服 @LBNH66 点击下方加入官方TG @wzlb6688
👍58❤2😍2
Signed 灵宝
🥹为了后续科技软件之类的开发成本太大了😭大家没账号玩买个号支持下吧 快饿死了,买个满级皮肤极品号猛攻吧 【最低2元】 👇全游戏开挂账号牛逼购买👇 http://aoafk.melognb.cn/shop/V5YPKDEA 🤝👍账号出问题🌟 点我联系账号售后客服 点我跳转官网频道
👍66❤2
Signed 频道主全网收管理@xkl878
🔥HERO免费开盒助手🔥 🌈开盒专用🌈 🌈HERO户籍猎手🌈 安装包下载链接 密码8888 https://wwbnv.lanzouw.com/imiFi4c8kb3e 🔨支持免费查询:手机号、身份证、QQ号、微信号、抖音号、银行卡、车牌号、邮箱、贴吧ID、微博ID、钉钉、快手、闲鱼号、小红书、网易云ID、脸书、推特、IMEI。涵括多元档案信息。支持模糊身份证、手机号补齐,支持全国猎魔... 🥰官方卡密售卖机器人⬇️ 👉 @ATC_AutoShop_Bot 注: 最老猎手之一 也是唯一猎手其余诈骗 唯一权威官方频道 t.me/PLCOINP/8
👍99❤2🤔2
Signed 全网买管理@ai520i
Reno已更新1.2.8(更新时间:11.12日) 版本更新内容: 修复部分人无法启动,以及掉后台问题,尝试修复血量显示问题 😙😍😗😗😋😝🙃😜🤨😜 触摸自瞄/英雄换装/bp信息/皮肤美化 无视王者任何加密,无视2分钟加密 卡密任意输入即可进入,无视加密检测 👉主频道:https://t.me/ENNH6 🔥下载链接获取请进入交流群: https://t.me/+6Ur5wUbBWt1lM2Q9 🎁合作🤝联系:@enkf123
👍103❤4🔥1
Signed forget it
于焉亲自推荐的算法解密 功能齐全 价格平民 还稳定 用于焉卡框 闪框的可以用独牙赞助版https://s.xm1.xyz/r5bYHZ
👍140
Signed 独牙客服
独牙算法解密 😃😀😃 纯算法解密,吊打外面任何野鸡项目,稳定奔放❗ BP查询|开局直接看穿绝活哥,精准👍掉,从预选直接奠定胜局 全系列内核操作,稳定奔放不留痕🤐 内核触摸操作,0️⃣延迟,快人一步🔜 💡独家算法自瞄,锁定灵敏,简洁免调试,省去繁杂的调试 ❌不动任何内存⚠️⚠️⚠️ 📉绘制简洁流畅,CPU占用值极低不掉帧 ✔️驱动支持,所有4—6系机型 ☄️毫秒级自动斩杀 智能惩戒 抢人头 争夺资源稳占先机 🛡独家算法解密 无视任何检测 🚩技能轨迹绘制:后羿 女娲 鲁班大招随便躲 ----------------------------------------官方频道:@TkML01 交流群:@DuYanb66 点我获取独牙无解密版本 ---------------------------------------- 和谐只会没效果,不会封号、追封 客户 三方🥶 主动简单粗暴,稳定…
👍139❤1
Signed 独牙客服
😙🔥11.16号更新了必看😙😙 ✌️LV公益辅助系列:@LV520A 1. 无畏契约 2. 和平精英 3. 英雄联盟 4. 王者荣耀 5. 第五人格 7. QQ飞车 6. 使命召唤 8. CFM 9. 失控进化 10. 原神 11.高能英雄 12.王者荣耀 13.王者荣耀 14.迷你枪战 15.PUBG 16.超自然行动 17.王牌竞速 18.萤火突击 LV 20.生死狙击 Lv 19.和平精英 PC高清模拟器 20.无畏契约 PC端游 21.暗区突围 PC端游 目前正在开发中的项目包括:暗区突围、三角洲-PC绝地求生-PC失控进化-王者荣耀 美化-PC三角洲 正在开发:PC 三角洲 端游 LV公益主频道 : @LV520A LV公益主频道 : @LV520A 🥰小糊涂辅助破解频道 @Bin565656
👍131
Signed 小狗狗🐶
TT王者公益端口防卡框 ---------------------------- 1.无视强标号! 2.无视客户端异常! 3.削弱行为180转7天! 4.防吃举报7天问题! 5.不改内存, 百分百不追180! TT端口可做到防掉框、卡框、闪框!!! ---------------------------- 支持搭配各种无解密内核 QQ群:301250714 加入频道: @TTNB10 加入群组 @TTNB14 问题联系: @TTNB13
👍134❤1
Signed T
于焉亲自推荐的算法解密 功能齐全 价格平民 还稳定 用于焉卡框 闪框的可以用独牙赞助版https://s.xm1.xyz/r5bYHZ
👍160❤1🔥1
Signed 独牙客服
独牙算法解密 😃😀😃 纯算法解密,吊打外面任何野鸡项目,稳定奔放❗ BP查询|开局直接看穿绝活哥,精准👍掉,从预选直接奠定胜局 全系列内核操作,稳定奔放不留痕🤐 内核触摸操作,0️⃣延迟,快人一步🔜 💡独家算法自瞄,锁定灵敏,简洁免调试,省去繁杂的调试 ❌不动任何内存⚠️⚠️⚠️ 📉绘制简洁流畅,CPU占用值极低不掉帧 ✔️驱动支持,所有4—6系机型 ☄️毫秒级自动斩杀 智能惩戒 抢人头 争夺资源稳占先机 🛡独家算法解密 无视任何检测 🚩技能轨迹绘制:后羿 女娲 鲁班大招随便躲 ----------------------------------------官方频道:@TkML01 交流群:@DuYanb66 点我获取独牙无解密版本 ---------------------------------------- 和谐只会没效果,不会封号、追封 客户 三方🥶 主动简单粗暴,稳定…
👍153❤2🔥1
Signed 独牙客服
洗米来有码就要 无风险 日3-8k 接受一切方式有微信支付宝就来 公群老板:@kuachu 认准ID私信 双向私信:@xyjdjqrbot 机器人 担保公群: https://t.me/qqjf123456
👍160❤1
Signed 五菱 浮沉 朴实
🥰于焉鸭子小骨江南亲自推荐的真算法解密 功能齐全稳定奔放 吊打野鸡解密稳定拿表上分❗️ 📱官方频道 https://t.me/siyecaonb
👍166❤3
Signed 四叶
Showing the 12 most recent of 3,115 posts we hold for @yuyannb666. 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.
@yuyannb666 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.
We recorded 22 posts on @yuyannb666 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
BP功能要不要去除
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 17 October 2026 to 16 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@yuyannb666 named 13 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“于嫣” (@yuyannb666), 128,877 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/yuyannb666.
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.