Channel
@qingzhu54188
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6,543subscribers
-80 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002449111811 |
|---|---|
| Type | Channel |
| Username | @qingzhu54188 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/qingzhu54188 |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 71% 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.
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 word for word on 2 other registered channels. 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 |
|---|---|---|---|
| @lingyunnb/290467 Aug 2026, 04:56 UTC | @qingzhu54188/28486 · this entry7 Aug 2026, 08:42 UTC | 1.00 | 3.8 hours |
| @qingzhu54188/28531 · this entry7 Aug 2026, 17:03 UTC | @lingyunnb/290537 Aug 2026, 17:03 UTC | 1.00 | under a minute |
| @lingyunnb/290457 Aug 2026, 04:56 UTC | @qingzhu54188/28532 · this entry7 Aug 2026, 17:03 UTC | 1.00 | 12 hours |
| @qingzhu54188/28544 · this entry7 Aug 2026, 19:49 UTC | @lingyunnb/290557 Aug 2026, 19:50 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @lingyunnb | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (3–2) |
| @xbnb6661 | 8 (5/8 hand-verifiable sample passed) | 1.00 | 4.8 hours | even |
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. 3 of the 3 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 39 comparable posts for this entry, running 6 August 2026 to 7 August 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.
Across the whole group of 3, the earliest publisher we hold is @qingzhu54188 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 8 August 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’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 12 Aug 2026, 14:15 | 6,543 | -35 |
| 9 Aug 2026, 22:31 | 6,578 | -39 |
| 6 Aug 2026, 23:22 | 6,617 | -6 |
| 6 Aug 2026, 08:33 | 6,623 | first reading |
143 posts held, back to 6 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 12 pagesof 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 66 of 143 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 143 (6 August 2026 – 12 August 2026) |
| Views total | 641 |
| Reactions total | 99 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03: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.
Measured directly from 18 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.
88 reactions across 56 posts, in 3 distinct kinds. The most used accounts for 85.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 75 | 85.2% | |
| 😁 | 8 | 9.09% | |
| ❤🔥 | 5 | 5.68% |
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 66 of the 143 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 99reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 143 most recent posts we hold, published 6 August 2026 to 12 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.
✔️小新高质量无限授权自营✔️ 😀和平/数据号/授权号/直登号/😀 ➡️😃😃退游号😃😃退游号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 🥇一年诚信经营，三年售后兜底 ✅授权号 ✅皮肤号 ✅直登号 😙😍😗😋😝🙃😜🤨😜 👍👍购买链接： https://luoye.chyidc.cn/shop/318719mm https://luoye.chyidc.cn/shop/318719mm https://luoye.chyidc.cn/shop/318719mm ✅无限授权网站： http://kssq1.com/ ✅所有账号问题都包售后 ✅全新自动去鉴别上号器 ✅一手号商 ✅专业售后 ❤️官方频道 https://t.me/nbxxnb67 😀😀😀😀😀😀 🔥全天在线客服联系：@bbbyyy91
庆祝频道人数6k 给大家发一个红包
💰 转账给你 23.89 U 请在24小时内领取
❤️ZOLO和平正式回归🎮 🟢正版老外作者，还是熟悉的感觉 🟢回归去年暑假的稳定性 🟢添加防录屏 🟢经过很久的研发测试，无任何禁令已正式发布 🥰卡密购买链接 https://shop.zmfaka.cn/shop/Y4PU65F3 官方频道 @bxzolo 官方频道 @bxzolo 官方频道 @bxzolo
Signed 冰雪
✅频道主推荐 TG最全soso资源搜索群🔍 免费开户 千元红包 免费数据号 公益内核 破解美化 免费看篇 八卦吃瓜 抖音热搜…… 🥰点击下方按钮加入即可搜索🥰
期九期和平刷刀体质v1 支持功能 1.6奔跑加速 330°广角 中能量加速 满能量极速 倒地行走/游泳加速 站立前后左右加速 趴下前后左右加速 蹲下前后左右加速 冰冻手雷加速 全模式通用 北青主频道 https://t.me/QXHNJ 北青副频道 https://t.me/BQnb69 期九期主频道 https://t.me/MQnb91 期九期副频道 https://t.me/yqobb 泛滥各大文件 https://t.me/sngf666888 已上传云盘 低价刷赞刷/qq会员/卡网
⭐残念单枪皮美化v192 ✅头发10(银色)=修复秃头 ✅湖蓝色名流一套=沙丘之主双生特效 ✅单枪皮美化➕经典地铁对应击中 ✅地铁金光+0战备+局内贴图 ✅投掷物手持+纯金仓库 ✅内置配料表 防重置 无需原版 —————————————— 😙下载链接: 点击前往123云盘高速下载 点击加入内部群 🌟🙃🌟🕠🕠 😄@CNWJNB 😄@CANNIANNB6
期九期和平刷刀体质v1 支持功能 1.6奔跑加速 330°广角 中能量加速 满能量极速 倒地行走/游泳加速 站立前后左右加速 趴下前后左右加速 蹲下前后左右加速 冰冻手雷加速 全模式通用 北青主频道 https://t.me/QXHNJ 北青副频道 https://t.me/BQnb69 期九期主频道 https://t.me/MQnb91 期九期副频道 https://t.me/yqobb 泛滥各大文件 https://t.me/sngf666888 已上传云盘 低价刷赞刷/qq会员/卡网
🎮清尘博尔特体质v2️⃣8️⃣ 🫠作者：🌟清尘 ⭐功能 ✅奔跑加速2️⃣倍加速✅蹲伏奔跑2️⃣倍加速 ✅匍匐爬行2️⃣倍加速✅濒死行走2️⃣倍加速 ✅站立后退2️⃣倍加速✅站立横移2️⃣倍加速 ✅蹲伏移动2️⃣倍加速✅蹲伏后退2️⃣倍加速 ✅蹲伏横移2️⃣倍加速✅趴下爬行2️⃣倍加速 ✅趴下后退2️⃣倍加速✅趴下横移2️⃣倍加速 ✅站立横移2️⃣倍加速✅站立前进2️⃣倍加速 ✅站立后退2️⃣倍加速✅蹲伏前进2️⃣倍加速 ✅蹲伏后退2️⃣倍加速✅蹲伏横移2️⃣倍加速 ✅冰冻移速2️⃣倍加速✅濒死游泳2️⃣倍加速 ✅中等能量2️⃣倍加速✅打满能量2️⃣倍加速 😇🙃😉@QCGWJNB 😇🙃😉@SHENYUANNB888 高速下载链接👇👇👇 https://pan.baidu.com/s/1dfDap5j6-JR7mImSym5cNA?pwd=QCNB 使用不点表情包，不加频道司马
🎮清尘博尔特体质v2️⃣8️⃣ 🫠作者：🌟清尘 ⭐功能 ✅奔跑加速2️⃣倍加速✅蹲伏奔跑2️⃣倍加速 ✅匍匐爬行2️⃣倍加速✅濒死行走2️⃣倍加速 ✅站立后退2️⃣倍加速✅站立横移2️⃣倍加速 ✅蹲伏移动2️⃣倍加速✅蹲伏后退2️⃣倍加速 ✅蹲伏横移2️⃣倍加速✅趴下爬行2️⃣倍加速 ✅趴下后退2️⃣倍加速✅趴下横移2️⃣倍加速 ✅站立横移2️⃣倍加速✅站立前进2️⃣倍加速 ✅站立后退2️⃣倍加速✅蹲伏前进2️⃣倍加速 ✅蹲伏后退2️⃣倍加速✅蹲伏横移2️⃣倍加速 ✅冰冻移速2️⃣倍加速✅濒死游泳2️⃣倍加速 ✅中等能量2️⃣倍加速✅打满能量2️⃣倍加速 😇🙃😉@QCGWJNB 😇🙃😉@SHENYUANNB888 高速下载链接👇👇👇 https://pan.baidu.com/s/1dfDap5j6-JR7mImSym5cNA?pwd=QCNB 使用不点表情包，不加频道司马
❤️ZOLO和平正式回归🎮 🟢正版老外作者，还是熟悉的感觉 🟢回归去年暑假的稳定性 🟢添加防录屏 🟢经过很久的研发测试，无任何禁令已正式发布 🥰卡密购买链接 https://shop.zmfaka.cn/shop/Y4PU65F3 官方频道 @bxzolo 官方频道 @bxzolo 官方频道 @bxzolo
👍1
Signed 冰雪
⭐璟程联手北青/沐屿付费 ✅频道 @Doro789/@sngf666888 ✅动态无后座80%辅助瞄准吸附 ✅辅瞄拉枪提升888%Max ✅腰射降低扩散命中率提升 ✅sav动态范围/追踪打击手感提升 ✅增强枪械属性提升：M416/AKM/Aug等热门枪械提升 ✅左右动态控制弹道命中率提升 ✅提升头部命中效果80% ✅头部打击感提升588% ✅魔法子弹大黄特效拉满 ✅无后座/防抖动亲测有效 💰💰下单链接：https://www.549fk.com/item/20jr7d
👍2
Signed ti me
Showing the 12 most recent of 143 posts we hold for @qingzhu54188. 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.
Citation-graph rank — 1,096,983 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 1 registered channel — 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.
@qingzhu54188 named 1 handle 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“清筑改文件主频道［冲10k］” (@qingzhu54188), 6,543 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/qingzhu54188.
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.