🏁 赛果|G2 1-2 Falcons ✅ 全局获胜:Falcons ❌ 地图比分:0 - 2 ❌ 地图让分:Falcons-1.5 ❌ 地图大小:小2.5 本场命中 1/4 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184

Channel
电竞赛事分析🎮
@qz8768
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
26,250subscribers
-3,815 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003633470467 |
|---|---|
| Type | Channel |
| Username | @qz8768 |
| Description | 🌍联盟导航 @LM667788 永不失联💯 💎 商务合作 @yh184 电竞赛事分析|赛前前瞻|焦点战报 覆盖 MLBB、CS2、VALORANT、DOTA2、LOL 每日更新赛事快讯、赛程信息、对局分析、赛后复盘 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/qz8768 |
Topic
Gambling & betting — 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 58% 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 |
|---|---|---|
| 12 Nov 2026, 20:56 | 26,250 | -193 |
| 10 Nov 2026, 17:46 | 26,443 | -750 |
| 9 Nov 2026, 04:10 | 27,193 | -98 |
| 8 Nov 2026, 00:09 | 27,291 | -141 |
| 6 Nov 2026, 19:21 | 27,432 | -97 |
| 5 Nov 2026, 22:16 | 27,529 | -185 |
| 4 Nov 2026, 22:06 | 27,714 | -80 |
| 3 Nov 2026, 18:09 | 27,794 | -227 |
| 2 Nov 2026, 14:44 | 28,021 | -63 |
| 1 Nov 2026, 15:21 | 28,084 | -131 |
| 31 Oct 2026, 17:20 | 28,215 | -113 |
| 30 Oct 2026, 19:20 | 28,328 | -151 |
| 29 Oct 2026, 20:59 | 28,479 | -153 |
| 28 Oct 2026, 17:37 | 28,632 | -84 |
| 27 Oct 2026, 18:29 | 28,716 | -51 |
| 26 Oct 2026, 20:27 | 28,767 | -89 |
| 25 Oct 2026, 18:17 | 28,856 | -245 |
| 24 Oct 2026, 15:35 | 29,101 | -254 |
| 23 Oct 2026, 17:28 | 29,355 | -110 |
| 22 Oct 2026, 18:27 | 29,465 | first reading |
Engagement
3,330 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 177 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.12%
- avg views ÷ 26,250 subscribers
- Avg views / post
- 1,610
- 1,083 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1,083
- of 3,330 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 13 November 2026 |
|---|---|
| Posts held | 3,330 (6 August 2026 – 13 November 2026) |
| Views total | 1,739,266 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 14:33 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
- ≈9,430
- Videos
- ≈467
- Links
- ≈920
Lifetime counters from Telegram’s own channel header, read 13 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
- 2h 08m
- Average length
- 1m 54s
Measured directly from 68 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1,083 posts held from the last 30 days (0%) 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).
#高光名场面 #王者荣耀 🎬 KPL总决赛最离谱的奇迹,真就独一份 这操作放小说里都得被骂太假 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
✨✨✨✨📣📣📣📣📣📣 13+ 官方矩阵 · 80+ 官方社群 100W+ 用户覆盖 🌐 旗下核心矩阵: 1️⃣ 东南亚各国大事件矩阵 ☺️ 东南亚大事件频道 @yhxw1 ☺️各国官方社群 (共计8个社群) ☺️ 东南亚大事件 @dnydsj89 ☺️ 斯里兰卡 @TGDSJ89 ☺️ 老挝特区 @bx6685 ☺️ 柬埔寨 @jpzdsj898 ☺️ 菲律宾 @FLBDSJ89 ☺️ 泰国 @bx6687 ☺️ 缅甸 @bx6682 ☺️ 迪拜 @bx6684 2️⃣ 东南亚大事件矩阵 ☺️官方频道 @bx6680 ☺️官方社群 (共计8个社群) @bx66h @bx66j @bx66i @bx66v @bx66p @bx66g @bx66s @bx66r 3️⃣东南亚曝光吃瓜矩阵 ☺️ 官方频道 @yh105 ☺️ 官方社群 (共计7个社群) @bgcg2 @bgcg9 @bgcg7 @bg…
#比赛预测 #CS2 BLAST Rivals 秋季赛 BO3 G2 - VS - Falcons 第三局获胜:Falcons 回合让分:Falcons-3.5 回合总是大小:小21.5 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
🏁 赛果 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
#电竞资讯 #英雄联盟 📰 LCK四大明星选手被AI性转😆 Zeus、Faker、Keria、Chovy被AI转成女性形象,搬到韩国社区后网友炸锅,调侃像无名女网红,还催更后续。 #LCK #AI ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
#比赛预测 #CS2 BLAST Rivals 秋季赛 BO3 G2 - VS - Falcons 第二局获胜:Falcons 回合让分:Falcons-2.5 回合总是大小:小21.5 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
#手游专区 #王者荣耀国际服 🎬 花木兰双世界皮肤,一个角色两副面孔😳 换个皮肤像换了个人,这设计真敢玩 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
#电竞资讯 #英雄联盟 📰 BLG掀翻T1,半个娱乐圈都来打call🔥 S15半决赛BLG 3比1淘汰T1,成首支在S赛BO5赢T1的LPL战队。樊振东、张靓颖、龚俊都发文祝贺,11月15日决赛对阵GEN。 #S15 #BLG ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
#高光名场面 #英雄联盟 🎬 左手对线细节拉满,BLG打HLE中路稳了 左手这操作,HLE中单怕是要失眠了 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
#高光名场面 #王者荣耀 🎬 超级兵偷家也能拿MVP? KPL五大偷家,看完想给兵线磕头🤣 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
#比赛预测 #CS2 BLAST Rivals 秋季赛 BO3 G2 - VS - Falcons 第一局获胜:Falcons 回合让分:Falcons-3.5 回合总是大小:小21.5 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
Showing the 12 most recent of 3,330 posts we hold for @qz8768. 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.
Mentions
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.
@LM667788 · 94,9292,920 posts缅甸大事件🇲🇲
@bx6682 · 7,50072 posts迪拜大事件🇦🇪
@bx6684 · 8,79972 posts金三角大事件🇱🇦
@bx6685 · 7,77172 posts泰国大事件🇹🇭
@bx6687 · 7,42272 posts东南亚大事件·曝光·吃瓜·悬赏🌏
@dnydsj89 · 7,73672 posts菲律宾大事件🇵🇭
@FLBDSJ89 · 6,77672 posts柬埔寨大事件🇰🇭
@jpzdsj898 · 7,50872 posts东南亚曝光吃瓜008
@bgcg5 · 2,96471 posts东南亚曝光吃瓜009
@bgcg89 · 2,84371 posts东南亚曝光吃瓜004
@bgcg9 · 1,93771 posts东南亚头条·大事件
@bx6680 · 24,40971 posts东南亚大事件曝光吃瓜007
@bx66g · 3,20371 posts东南亚大事件曝光吃瓜003
@bx66i · 2,24771 posts电竞赛事分析LOL LSK KPL 004
@djtd87 · 2,45771 posts加密货币crypto资讯
@jmhb1 · 21,68571 posts加密货币crypto资讯001
@jmhb3 · 2,14771 posts加密货币BTC ETH资讯002
@jmhb5 · 2,34971 posts加密货币BTC ETH资讯004
@jmhb84 · 2,56571 posts马来西亚大事件🇲🇾
@MDDSJ89 · 8,71971 posts马达加斯加大事件非洲马岛
@mdjsj86 · 3,06071 posts马来西亚大事件🇲🇾
@mlxy80 · 23,92171 posts马来大事件吉隆坡大事件001
@mlxy81 · 2,73071 postsPolymarket预测市场002
@polym2 · 2,40871 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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@qz8768 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.
Evidenced gone
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.
named in 9 posts, 8 August 2026 – 2 September 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 9 posts, 8 August 2026 – 2 September 2026
named in 9 posts, 8 August 2026 – 2 September 2026
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“电竞赛事分析🎮” (@qz8768), 26,250 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/qz8768.
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.