🌈红包发送成功🀄️ 📱欧易ouyi 发送了 一个红包! 🤑总金额: 1888 U🪙 🚦剩余: 68/88 🥇 128.88 USDT - 褪黑素…. 🥈 98.26 USDT - 爱吃鼠标78 🥉 78.61 USDT - 松欢
Signed 辛巴

Channel
@xueluoqingyan
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
10,519subscribers
+1,716 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002208281727 |
|---|---|
| Type | Channel |
| Username | @xueluoqingyan |
| Created | 14 August 2024 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/xueluoqingyan |
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 08:38 | 10,519 | +1,930 |
| 16 Sept 2026, 14:18 | 8,589 | +43 |
| 12 Sept 2026, 11:56 | 8,546 | +28 |
| 8 Sept 2026, 01:38 | 8,518 | -24 |
| 3 Sept 2026, 06:07 | 8,542 | -23 |
| 31 Aug 2026, 03:46 | 8,565 | -9 |
| 28 Aug 2026, 05:54 | 8,574 | -12 |
| 25 Aug 2026, 13:16 | 8,586 | -24 |
| 22 Aug 2026, 11:07 | 8,610 | -25 |
| 19 Aug 2026, 10:35 | 8,635 | -71 |
| 16 Aug 2026, 21:17 | 8,706 | -40 |
| 13 Aug 2026, 10:35 | 8,746 | -40 |
| 10 Aug 2026, 04:58 | 8,786 | -19 |
| 7 Aug 2026, 03:56 | 8,805 | +2 |
| 6 Aug 2026, 23:02 | 8,803 | first reading |
105 posts held, back to 14 August 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 28 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. It is computed over the 1 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 105 (14 August 2024 – 28 August 2026) |
| Views total | 1,118 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 16:58 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.
71 reactions across 13 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 71 | 100.0% |
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 18 of the 105 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 105 most recent posts we hold, published 14 August 2024 to 28 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.
🌈红包发送成功🀄️ 📱欧易ouyi 发送了 一个红包! 🤑总金额: 1888 U🪙 🚦剩余: 68/88 🥇 128.88 USDT - 褪黑素…. 🥈 98.26 USDT - 爱吃鼠标78 🥉 78.61 USDT - 松欢
Signed 辛巴
❗️❗️soso搜索资源群 🥰 🥰🥰🥰 ✅频道主推荐 TG最全soso资源搜索群🔍 🥰加入即可搜索🥰 https://t.me/+H90cuCmBz38zMjEx https://t.me/+V_GTlzQIjVY4NDhk https://t.me/+y9aA26qr19c0YWRh 免费开户 千元红包 免费数据号 公益内核 破解美化 免费看篇 八卦吃瓜 抖音热搜…… 点击下方按钮加入🌐
Signed 辛巴
🇨🇳『转转』数据号【质量】🙈 ✅售后24小时在线 (服务拉满!) 主营:『和平无限授权号』『和平Q直登V扫码号 『安卓iOS和平数据号』『三角洲无畏契约数据号』 😀新增全网最低价无限授权号😀 😙卡网售卖游戏账号 🎚和平精英 👍无畏契约 ❤️三角洲 🎚PUBG 🔗24小时自助下单链接🔗 👍购买链接: 卡网1: https://luoye.yjsfk.cn/shop/LQ2XVETA 卡网2: https://luoye.yjsfk.cn/shop/LQ2XVETA 【全网唯一低价质量靠谱数据号】 😋二卖出门被车撞死😋 👍圈钱出门被车撞死👍 😡 售后客服 @NIMEIPY 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道
Signed 晚安『做单秒结』🅥
封禁挂圈森岛886
Signed 一滴泪名真心
Photo, posted without a caption
Signed 一滴泪名真心
我被预告了兄弟们
❤1
Signed 一滴泪名真心
低价飞机号卡网👑 内置低价TG号 快手接码 微信接码 后续会添加更多的账号售卖💎 低价TG号❗️只需2块❗️ 卡网链接: https://shop.ymy9.com/shop/huanjue 频道: @xueluoqingyan
Signed 一滴泪名真心
🇨🇳『转转』数据号【质量】🙈 ✅售后24小时在线 (服务拉满!) 主营:『和平无限授权号』『和平Q直登V扫码号 『安卓iOS和平数据号』『三角洲无畏契约数据号』 😀新增全网最低价无限授权号😀 😙卡网售卖游戏账号 🎚和平精英 👍无畏契约 ❤️三角洲 🎚王者荣耀 🔗24小时自助下单链接🔗 👍购买链接: 卡网1: https://luoye.chyidc.cn/shop/LQ2XVETA 卡网2:https://luoye.chyidc.cn/shop/LQ2XVETA 【全网唯一低价质量靠谱数据号】 😋二卖出门被车撞死😋 👍圈钱出门被车撞死👍 😡 售后客服 @NIMEIPY 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道
Signed 晚安『做单秒结』🅥
◻️欧易钱包 马年福利季已达到! ⚡️⚡️⚡️⚡️ 豪礼相送!⚡️ 🤥 欧易空投钱包【疯狂送钱中】 发送了一个空投红包🤑 🪙总金额: 35000 USDT💰 剩余:1762/1888 🥇 533.52(10:22:29) 💰 - 无畏无 🥈 433.10(10:22:31) 💰 - SoujiT... 🥉 421.34(10:22:32) 💰 - 顾北 ✨ 350.54(10:23:13) 💰 - AKS ✨ 331.49(10:23:27) 💰 - 四季(好大哥... ✨ 325.27(10:23:05) 💰 - 小泽 ⭐️ 297.25(10:23:15) 💰 - (阿骏)地址... ⭐️ 284.25(10:23:26) 💰 - 阿成 ⭐️ 274.96(10:23:25) 💰 - 伊总💋
Signed 辛巴
🇨🇳『转转』数据号【质量】🙈 ✅售后24小时在线 (服务拉满!) 主营:『和平无限授权号』『和平Q直登V扫码号 『安卓iOS和平数据号』『三角洲无畏契约数据号』 😀新增全网最低价无限授权号😀 😙卡网售卖游戏账号 🎚和平精英 👍无畏契约 ❤️三角洲 🎚PUBG 🔗24小时自助下单链接🔗 👍购买链接: 卡网1: https://luoye.chyidc.cn/shop/LQ2XVETA 卡网2:https://luoye.chyidc.cn/shop/LQ2XVETA 【全网唯一低价质量靠谱数据号】 😋二卖出门被车撞死😋 👍圈钱出门被车撞死👍 😡 售后客服 @NIMEIPY 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道
Signed 晚安『做单秒结』🅥
❗️❗️soso搜索资源群 🥰 🥰🥰🥰 ✅频道主推荐 TG最全soso资源搜索群🔍 🥰加入即可搜索🥰 https://t.me/+H90cuCmBz38zMjEx https://t.me/+V_GTlzQIjVY4NDhk https://t.me/+y9aA26qr19c0YWRh 免费开户 千元红包 免费数据号 公益内核 破解美化 免费看篇 八卦吃瓜 抖音热搜…… 点击下方按钮加入🌐
Signed 辛巴
好累 钱没赚到多少好像都在只出不进
Signed 一滴泪名真心
Showing the 12 most recent of 105 posts we hold for @xueluoqingyan. 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.
@xueluoqingyan edited 2 posts 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.
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.
Named by 5 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.
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.
@xueluoqingyan named 3 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“幻觉官方频道” (@xueluoqingyan), 10,519 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/xueluoqingyan.
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.