Telegram RegisterThe public register of Telegram
Telegram profile photo for 电竞风暴赛事推单 78.com 【独家冠名】(接广告合作)

Channel

电竞风暴赛事推单 78.com 【独家冠名】(接广告合作)

@QSTY2

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

42,622subscribers

-20,113 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001229895566
TypeChannel
Username@QSTY2
Description78.com 【独家冠名】 🎮 电竞风暴|聚焦全球电竞热点! 这里是电竞爱好者的专属阵地!实时追踪 LOL、DOTA2、CS2、王者荣耀、和平精英等热门电竞赛事,汇集最新比赛资讯、战队动态、选手消息、赛事战报与精彩操作。紧跟电竞潮流,掌握赛场风云,每一次对决都值得关注!🔥
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 October 2026
Measurements held48
Confirmed unchanged1 time, most recently 25 October 2026
On Telegramt.me/QSTY2

Topic

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 83% 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.

Growth

41,92862,73552,331.56 August 2026 — 62,735 subscribers7 August 2026 — 62,711 subscribers8 August 2026 — 62,564 subscribers9 August 2026 — 62,357 subscribers10 August 2026 — 62,240 subscribers11 August 2026 — 62,067 subscribers12 August 2026 — 61,927 subscribers13 August 2026 — 61,856 subscribers14 August 2026 — 61,656 subscribers16 August 2026 — 61,379 subscribers17 August 2026 — 61,225 subscribers18 August 2026 — 56,498 subscribers19 August 2026 — 56,355 subscribers20 August 2026 — 52,547 subscribers22 August 2026 — 52,424 subscribers24 August 2026 — 52,047 subscribers25 August 2026 — 51,826 subscribers26 August 2026 — 51,642 subscribers27 August 2026 — 51,528 subscribers28 August 2026 — 51,442 subscribers29 August 2026 — 51,326 subscribers30 August 2026 — 51,178 subscribers31 August 2026 — 51,067 subscribers1 September 2026 — 50,974 subscribers2 September 2026 — 50,840 subscribers3 September 2026 — 50,618 subscribers5 September 2026 — 50,505 subscribers8 September 2026 — 50,023 subscribers11 September 2026 — 49,570 subscribers13 September 2026 — 49,318 subscribers14 September 2026 — 49,206 subscribers16 September 2026 — 49,024 subscribers19 September 2026 — 48,862 subscribers25 September 2026 — 47,523 subscribers4 October 2026 — 44,651 subscribers8 October 2026 — 43,340 subscribers13 October 2026 — 42,919 subscribers14 October 2026 — 42,743 subscribers15 October 2026 — 42,605 subscribers16 October 2026 — 42,502 subscribers17 October 2026 — 42,482 subscribers18 October 2026 — 42,328 subscribers19 October 2026 — 42,167 subscribers20 October 2026 — 41,928 subscribers22 October 2026 — 42,680 subscribers23 October 2026 — 42,999 subscribers24 October 2026 — 42,733 subscribers25 October 2026 — 42,622 subscribers42,6226 August 202625 October 2026
48 measurements spanning 79 days, net -20,113. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 38,807–65,856 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
25 Oct 2026, 04:5042,622-111
24 Oct 2026, 06:1642,733-266
23 Oct 2026, 05:2142,999+319
22 Oct 2026, 05:2942,680+752
20 Oct 2026, 22:4741,928-239
19 Oct 2026, 19:5742,167-161
18 Oct 2026, 16:1942,328-154
17 Oct 2026, 19:2142,482-20
16 Oct 2026, 21:2742,502-103
15 Oct 2026, 18:4642,605-138
14 Oct 2026, 16:5442,743-176
13 Oct 2026, 05:2042,919-421
8 Oct 2026, 19:5743,340-1,311
4 Oct 2026, 07:1844,651-2,872
25 Sept 2026, 14:1547,523-1,339
19 Sept 2026, 04:5548,862-162
16 Sept 2026, 18:3749,024-182
14 Sept 2026, 19:2049,206-112
13 Sept 2026, 05:5649,318-252
11 Sept 2026, 07:1949,570first reading

Engagement

670 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 167 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.23%
avg views ÷ 42,622 subscribers
Avg views / post
1,380
211 posts measured
Reaction rate
0.075%
reactions ÷ views · ER floor
Posts in window
213
of 670 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. It is computed over the 11 of 211 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 October 2026
Posts held670 (6 August 2026 – 25 October 2026)
Views total290,136
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Oct 2026, 19:08 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
≈5,520
Videos
≈1,150
Links
≈3

Lifetime counters from Telegram’s own channel header, read 25 October 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
4h 03m
Average length
3m 07s

Measured directly from 78 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.

Reaction mix

219 reactions across 173 posts, in 10 distinct kinds. The most used accounts for 49.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10849.3%
👍5525.1%
👏2310.5%
🔥209.13%
👌31.37%
💯31.37%
🥰31.37%
👀20.913%
👎10.457%
😍10.457%

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 173 of the 670 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 219 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 670 most recent posts we hold, published 6 August 2026 to 25 October 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.

Recent posts

25 Oct 2026, 13:52 UTC≈1,110 viewsread 25 October 2026
Photo

【S16瑞士轮第三轮赛程:26日首战IG对阵HLE,AL 27日迎生死战】 今日赛事官方公布S16瑞士轮第三轮赛程,具体如下(以下为北京时间): 10月26日(周一) 01:00 HLE vs IG BO1 02:00 G2 vs TES BO1 03:00 MKOI vs DK BO3 06:00 GEN vs LYON BO3 10月27日(周二) 01:00 CFO vs T1 BO1 02:00 BLG vs KC BO1 03:00 LOS vs TSW BO3 06:00 TLAW vs AL BO3

25 Oct 2026, 13:45 UTC≈1,180 viewsread 25 October 2026
Photo

#LOL 2026 全球总决赛 - 瑞士轮 GEN 对战 LYON(BO3) 全局获胜:GEN 地图比分:2 - 1 地图让分:LYON+1.5 地图大小:大2.5

25 Oct 2026, 13:45 UTC≈1,180 viewsread 25 October 2026
Photo

#LOL 2026 全球总决赛 - 瑞士轮 DK 对战 MKOI(BO3) 全局获胜:DK 地图比分:2 - 0 地图让分:DK-1.5 地图大小:小2.5

25 Oct 2026, 13:45 UTC≈1,150 viewsread 25 October 2026
Photo

#LOL 2026 全球总决赛 - 瑞士轮 TES 对战 G2(BO1) 第一局独赢:TES 击杀让分:TES+3.5 击杀人头:大26.5 比赛时间:大32

25 Oct 2026, 13:45 UTC≈1,220 viewsread 25 October 2026
Photo

#LOL 2026 全球总决赛 - 瑞士轮 HLE 对战 IG(BO1) 第一局独赢:IG 击杀让分:IG+9.5 击杀人头:大28.5 比赛时间:小30

25 Oct 2026, 06:45 UTC≈1,130 viewsread 25 October 2026
Video

🤩🤩🤩🤩 🤩🤩🤩🤩🤩 0审核|包出款🤩🤩🤩 东南亚大事件联合担保🤩🤩🤩🤩🤩(电子) 🤩亿级域名|78.COM 🤩官方飞投|充提自由 🔝实力派:78.COM 数字够短 品牌够大 🔥香港六合彩 · 独家盈利无上限! 🤩所有的特码🤩🤩倍 🤩连码三中三🤩🤩🤩倍 🤩百家乐全网最高起步返水🤩% 🤩电子|棋牌|捕鱼起步返水🤩.🤩% 🤩十三水|德州自主组队,无抽佣; 🏆电子单注🤩🤩🤩🤩U一拉; ⭐️百家乐真人视讯台红🤩🤩万U; 🚩诚招代理合作 1.打码返佣,限指定平台; 2.可叠加占成,自选占成比例及游戏平台; 🤩🤩🤩🤩:@DL78 💥高额战绩,巅峰记录持续刷新: 🥇PP电子|极速糖果1000 玩家游戏中购买30000u超级免费旋转,高倍爆奖,最终拿下378万U,已出款; 🥈PG电子|麻将胡了 又又又欧气爆棚,5000U一拉,连番触发,单局斩获233万U; 🥉香港六合彩|特码49倍 爱拼才会赢,大佬单码下注18万U, 一注直接拿下本期最…

25 Oct 2026, 06:30 UTC≈1,210 viewsread 25 October 2026
Photo

【IG发布对阵HLE赛前海报:乘胜追击,極境连捷!】 今日IG发布对阵HLE赛前海报,配文如下: 乘胜追击,極境连捷! IG作为LPL赛区四号种子,在2026英雄联盟全球总决赛瑞士轮首轮不敌LCK赛区一号种子GEN,第二轮击败LCP赛区一号种子TSW,以1胜1负的战绩进入1-1组,将于北京时间10月26日凌晨2点出战瑞士轮第三轮BO1比赛,对手为LCK赛区二号种子HLE。

25 Oct 2026, 06:27 UTC≈1,370 viewsread 25 October 2026
Video

【369更新视频动态- JKL:9哥他没毛病】 TES作为LPL赛区三号种子,在2026英雄联盟全球总决赛瑞士轮首轮不敌LCK赛区二号种子HLE,第二轮击败同赛区一号种子AL,以1胜1负的战绩进入1-1组,将于北京时间10月26日凌晨2点出战瑞士轮第三轮BO1比赛,对手为LEC赛区一号种子G2。

25 Oct 2026, 06:23 UTC22 viewsread 25 October 2026
Photo

【S16瑞士轮第三日LPL赛区对阵预告:HLE对战IG;G2对战TES】 2026全球总决赛瑞士轮第三日的赛事将于10月26日1:00开赛,LPL赛区对阵预告如下。 10月26日 1:00 HLE对战IG(BO1) 10月26日 约2:00 G2对战TES (BO1) 解说席:毛毛、鼓鼓、米勒、王多多、吴雨凡、957 主持人:松琪

25 Oct 2026, 06:23 UTC≈1,180 viewsread 25 October 2026
Photo

【TES发布对阵G2赛前海报:滔搏加油!】 2026全球总决赛瑞士轮-第三轮G2对战TES(BO1)的赛事将于10月26日约02:00开赛。 TES官方发布赛前海报,配文:滔搏加油! 首发阵容:369、Tian、Creme、JackeyLove、Zhuo 2026英雄联盟全球总决赛LPL赛区三号种子TES目前战绩。 瑞士轮第1轮:TES 0-1不敌HLE(LCK二号种子) 瑞士轮第2轮:TES 1-0战胜AL(LPL一号种子)

24 Oct 2026, 14:57 UTC≈1,020 viewsread 25 October 2026
Photo

#LOL 2026 全球总决赛 - 瑞士轮 TL 对战 BLG(BO1) 第一局独赢:BLG 击杀让分:BLG-7.5 击杀人头:大27.5 比赛时间:小31

24 Oct 2026, 14:57 UTC≈1,010 viewsread 25 October 2026
Photo

#LOL 2026 全球总决赛 - 瑞士轮 DK 对战 T1(BO1) 第一局独赢:T1 击杀让分:DK+6.5 击杀人头:大27.5 比赛时间:大32

Showing the 12 most recent of 670 posts we hold for @QSTY2. 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.

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.

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 25 October 2026 — this entry's latest reading, not the date you are reading this.

“电竞风暴赛事推单 78.com 【独家冠名】(接广告合作)” (@QSTY2), 42,622 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/QSTY2.

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.