11月02日 22:30,Daxak Team对阵iLTW TEAM Fonbet Media Eleague下一轮有这组对阵:Daxak Team vs iLTW TEAM。时间是11月02日 22:30,打BO3。 目前能确认的只有赛程信息,首发和临场变化等官方更新后再看。 ✅ 电竞赛事频道 @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
28,021subscribers
-2,044 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 |
| 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 | 2 November 2026 |
| Measurements held | 56 |
| Confirmed unchanged | 1 time, most recently 2 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 |
|---|---|---|
| 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 | -193 |
| 21 Oct 2026, 15:40 | 29,658 | -185 |
| 20 Oct 2026, 09:41 | 29,843 | -217 |
| 19 Oct 2026, 09:17 | 30,060 | -162 |
| 18 Oct 2026, 05:47 | 30,222 | -126 |
| 17 Oct 2026, 02:19 | 30,348 | -313 |
| 16 Oct 2026, 04:35 | 30,661 | -272 |
| 15 Oct 2026, 05:09 | 30,933 | -255 |
| 14 Oct 2026, 04:20 | 31,188 | first reading |
Engagement
2,957 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 155 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.88%
- avg views ÷ 28,021 subscribers
- Avg views / post
- 1,930
- 1,147 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1,147
- of 2,957 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 2 November 2026 |
|---|---|
| Posts held | 2,957 (6 August 2026 – 2 November 2026) |
| Views total | 2,211,887 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Nov 2026, 13: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.
What this channel posts
- Video runtime
- 45s
- Average length
- 3s
Measured directly from 15 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
11月04日 06:00,BESTIA Academy对阵Zetta Games 这场安排在11月04日 06:00进行,属于CCT South America,对阵是BESTIA Academy和Zetta Games,赛制BO3。 目前能确认的只有赛程信息,首发和临场变化等官方更新后再看。 ✅ 电竞赛事频道 @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…
QUINTESSÊNCIA vs RED Canids Academy|开赛时间已定 先把时间放这里:QUINTESSÊNCIA与RED Canids Academy将在11月04日 03:00碰面,赛事为CCT South America,赛制BO3。 先记时间和对阵,临场名单、地图等信息有更新再补。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
11月04日 00:00,Mira对阵tao toma CCT South America下一轮有这组对阵:Mira vs tao toma。时间是11月04日 00:00,打BO3。 现阶段不硬猜走势,等阵容和赛前状态补齐后再判断。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
CCT South America赛程|MIBR fe vs Rush CCT South America下一轮有这组对阵:MIBR fe vs Rush。时间是11月03日 21:00,打BO3。 先记时间和对阵,临场名单、地图等信息有更新再补。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
Cyber Hero打Bushido Wildcats,这场赛历先记下 先把时间放这里:Cyber Hero与Bushido Wildcats将在11月02日 23:00碰面,赛事为BetBoom Rise of Legends,赛制BO3。 这条先做赛程提醒,不提前写胜负;阵容与临场信息以赛前更新为准。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
Damajuana对上MEIA NOITE,我先看前两局谁更连贯 11月04日 21:00,CCT South America,Series 8 2026·小组赛,赛制为BO3。 MEIA NOITE最近打出了0比2不敌Tropa do KinGui、2比1拿下Procyon Gaming;Damajuana这边的近况是1比2不敌Hacha Esports、1比2不敌your end、2比0拿下A NATA。 我的选择是Damajuana。理由很直接,MEIA NOITE最近掉图更快,Damajuana至少没那么容易被一波带走。MEIA NOITE如果能先把开局站稳,系列赛仍有拉长的空间;如果前半段连续让出主动,Damajuana会更容易把近期状态兑现出来。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
IEM赛程|Legacy vs B8 这场安排在11月03日 10:00进行,属于IEM,对阵是Legacy和B8,赛制BO3。 现阶段不硬猜走势,等阵容和赛前状态补齐后再判断。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
BakS eSports vs Honvéd|开赛时间已定 先把时间放这里:BakS eSports与Honvéd将在11月05日 17:00碰面,赛事为NODWIN Clutch Series,赛制BO3。 目前能确认的只有赛程信息,首发和临场变化等官方更新后再看。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
Worlds赛程|Karmine Corp vs T1 赛程信息已经确认:11月05日 06:00,Worlds,Karmine Corp对阵T1,BO5。 目前能确认的只有赛程信息,首发和临场变化等官方更新后再看。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
11月05日 03:00,Team Allied对阵Team Lynx Asgard Championship下一轮有这组对阵:Team Allied vs Team Lynx。时间是11月05日 03:00,打BO3。 现阶段不硬猜走势,等阵容和赛前状态补齐后再判断。 ✅ 电竞赛事频道 @qz8768 🌐 联盟导航 @LM667788 🐖 商务合作 @yh184
Showing the 12 most recent of 2,957 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 · 97,4352,597 posts缅甸大事件🇲🇲
@bx6682 · 9,93162 posts迪拜大事件🇦🇪
@bx6684 · 11,06762 posts金三角大事件🇱🇦
@bx6685 · 10,45362 posts泰国大事件🇹🇭
@bx6687 · 9,57562 posts东南亚大事件·曝光·吃瓜·悬赏🌏
@dnydsj89 · 7,61662 posts菲律宾大事件🇵🇭
@FLBDSJ89 · 6,80462 posts柬埔寨大事件🇰🇭
@jpzdsj898 · 7,47862 posts东南亚曝光吃瓜008
@bgcg5 · 2,91561 posts东南亚曝光吃瓜009
@bgcg89 · 2,79661 posts生活研究认知提升002
@bx66cc · 2,29461 posts东南亚大事件曝光吃瓜007
@bx66g · 3,88261 posts电竞赛事分析LOL LSK KPL
@djsj81 · 2,38561 posts电竞赛事分析LOL LSK KPL002
@djtd3 · 2,43761 posts电竞赛事分析LOL LSK KPL 003
@djtd86 · 2,50561 posts热播短剧精品短剧美女短剧001
@duanju8 · 2,40261 posts加密货币crypto资讯001
@jmhb3 · 2,18161 posts加密货币BTC ETH资讯004
@jmhb84 · 2,55561 posts马来西亚大事件🇲🇾
@MDDSJ89 · 8,72461 posts马达加斯加大事件非洲大事件004
@mdjsj83 · 2,75761 posts精品短剧
@meinv94 · 21,27561 posts马来西亚大事件🇲🇾
@mlxy80 · 25,65061 postsPolymarket预测市场002
@polym2 · 2,39861 postsPolymarket预测市场005
@polym4 · 2,36461 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“电竞赛事分析🎮” (@qz8768), 28,021 subscribers as measured 2 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.