Telegram RegisterThe public register of Telegram

Channel

惠州爽炮

@qiusuio

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

48,476subscribers

-1,814 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002241626083
TypeChannel
Username@qiusuio
Description娱乐怕踩雷?平台美女担保加持,安心畅玩,给你双倍快乐 交流群: https://t.me/+4fsonAbER3YwNzhh 投诉 上榜: @huizhousbbot
CreatedBetween 1 May 2024 and 31 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/qiusuio

Growth

48,47650,29049,3837 August 2026 — 50,290 subscribers8 August 2026 — 50,153 subscribers9 August 2026 — 49,711 subscribers10 August 2026 — 49,372 subscribers11 August 2026 — 49,096 subscribers12 August 2026 — 48,664 subscribers13 August 2026 — 48,476 subscribers7 August 202613 August 2026
7 measurements spanning 6 days, net -1,814. 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 48,204–50,562 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:3748,476-188
12 Aug 2026, 06:3248,664-432
11 Aug 2026, 07:2649,096-276
10 Aug 2026, 06:1749,372-339
9 Aug 2026, 03:1149,711-442
8 Aug 2026, 03:1550,153-137
7 Aug 2026, 19:1850,290first reading

Engagement

12 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.05%
avg views ÷ 48,476 subscribers
Avg views / post
994
12 posts measured
Reaction rate
0.095%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 6 of 12 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 12 August 2026
Posts held12 (2 August 202612 August 2026)
Views total11,925
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 23:40 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
958
Videos
338
Links
48

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
53s
Average length
27s

Measured directly from 2 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

5 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5100.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 6 of the 12 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 2 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.

Recent posts

12 Aug 2026, 06:07 UTC557 views1 reactionsread 13 August 2026
Photo

艺名:#涵涵 位置:#惠州惠阳大亚湾 人照: 8分 年龄18 资料:胸B 高162 水费: 500p 900pp 私聊:@djjdkfjcm 机器人: 频道:https://t.me/jxnfkfckksndmckdmdmmx 服务:洗 吹 做 🐍吻 制服丝袜 交流群: https://t.me/+4fsonAbER3YwNzhh

1

11 Aug 2026, 08:13 UTC695 views1 reactionsread 13 August 2026
Photo

艺名:#佳佳 位置:#惠州惠阳大亚湾 人照: 8分 年龄18 资料:胸B 高155 水费: 550p 1100pp 私聊:@xiaoxiao20080111 机器人:@jiajia773221bot 频道:https://t.me/XX20080111 服务:洗 吹 做 🐍吻 69 制服丝袜 交流群: https://t.me/+4fsonAbER3YwNzhh

1

10 Aug 2026, 08:59 UTC862 views1 reactionsread 13 August 2026
Photo

艺名:#晓颖 位置:#惠州惠阳大亚湾 人照: 8分 年龄25 资料:胸C 高168 水费: 600p 1200pp 私聊:@Xiaoying1207 机器人:@KLvdf22_bot 频道:https://t.me/xvgjf68gj 服务: 洗 吹 做 🐍吻 69 制服丝袜 交流群: https://t.me/+4fsonAbER3YwNzhh

1

9 Aug 2026, 08:34 UTC974 viewsread 13 August 2026
Photo

艺名:#小胖妞 位置:#惠州惠阳大亚湾 人照: 8分 年龄21 资料:胸E 高161 水费: 400p 800pp 私聊:@hyxpn987 机器人:@mzghjygmorng_bot 频道:https://t.me/Xpnppoo9999 服务: 洗 吹 做 69 🐻推 交流群: https://t.me/+4fsonAbER3YwNzhh

8 Aug 2026, 11:37 UTC≈1,080 viewsread 13 August 2026
Photo

惠城高端走秀海选SPA❗️ 🔈全国多家分店:技师不定时调配 团队总技师300+分布各地一二线城市 🎀技师精心挑选·只做高颜值 🎀技师均龄18-28岁之间 🎀技师穿着性感一排海选模式 🎀技师专业培训手法独特花样多 💰价格:3️⃣9️⃣9️⃣ 部分顶级一线妹子驻场4️⃣9️⃣9️⃣ 双飞活动第二位半价 真实海选 妹子站一排海选任挑! 💎服务内容 手推 熊推 丝足同时配合 任选出货! 音乐调情 艳舞互动,全程半果环游全身调情,女友式投怀送抱❤️ 吸气🎆过水🎊足交💕漫游🌸 胸滑🎆指划🎊调情💕鼻吸🌸 乳交🎆躺抱🎊环抱💕毒龙🌸 60分钟不限次数 制服变装黑丝白丝各种情趣制服任您挑选~ 📞186 666 02502(同微) 📞186 666 09019(同微) QQ: 2648 123 739 👨‍💻咨询/预约客服: @TX9018 ⬅️ 😍实拍美女相册: @TX88997 位置:河南岸麦地东泰汇养生会所 错过了10年前的东莞

7 Aug 2026, 08:16 UTC≈1,010 viewsread 11 August 2026
Photo

艺名:#小懒 位置:#惠州惠阳大亚湾 人照: 8分 年龄18 资料:胸B 高167 水费: 650p 1300pp 私聊:@QQ2008000 机器人:@xiaolan8866230bot 频道:https://t.me/QQ20080888 服务: 洗 吹 做 🐍吻 69 交流群: https://t.me/+4fsonAbER3YwNzhh

6 Aug 2026, 09:34 UTC947 views0 reactionsread 10 August 2026
Photo

艺名:#九月 位置:#惠州惠阳大亚湾 人照: 8分 年龄27 资料:胸C 高165 水费: 400p 800pp 私聊:@jiuyue0092 机器人:@jiuyue89377bot 频道:https://telegram.me/+BnnvFSVgewEzYzVh 服务: 洗 吹 做 69 制服丝袜 交流群: https://t.me/+4fsonAbER3YwNzhh

4 Aug 2026, 12:57 UTC≈1,230 viewsread 10 August 2026
Video

😀😀😀😀😀😀 😀😀😀😀😀😀😀 ⚽世界杯官方指定博彩平台 😍开云集团旗下亚洲最顶级博彩平台 😍体育 H5版 — WEB端入口 😍体育 PC端 — 网页版入口 😍体育 全站APP — APP下载 🔤🔤小程序,免实名-不限IP-U存U取 😍😍😍😍😍😍😀😀😀😀😀😀😀 匿名首选 📱飞投入口 ⭐首存加赠2⃣5⃣🔣复存加增1⃣0⃣🔣 ⭐足球/篮球/电竞首单包赔1⃣0⃣0⃣🔣 ⭐真人无门槛双边返水0⃣🔣9⃣🔣仅限飞投版 ❤❤❤❤ @MKFTYZ ⚡⚡⚡⚡易换支付钱包,1⃣0⃣亿🔤资金池储备 ⚡⚡⚡⚡全网5⃣0⃣0⃣0⃣万🔤担保,拒绝野鸡台 ❤❤❤❤代理分润 5⃣5⃣🔣 @MKFT888 ❤❤❤❤ @MKFT777 关注🔈😀😀😀😀😀😀😀😀 @rdsjo 掌握东南亚一线动态,看清风向料定先机 频道每周抽取100名TG会员,群发言积分兑🔤

4 Aug 2026, 10:10 UTC≈1,170 viewsread 10 August 2026
Photo

艺名:#小花猫 位置:#惠阳区 点击下方评论👇查看老师详细资料

3 Aug 2026, 07:24 UTC≈1,210 viewsread 9 August 2026
Photo

艺名:#雨雨 位置:#惠阳区 点击下方评论👇查看老师详细资料

3 Aug 2026, 06:55 UTC≈1,030 views2 reactionsread 8 August 2026
Photo

新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。

2

2 Aug 2026, 08:34 UTC≈1,160 views0 reactionsread 8 August 2026
Photo

艺名:#蛋卷 位置:#惠阳区 点击下方评论👇查看老师详细资料

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

Citation-graph rank — 754,158 of 1,189,255entries 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.

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

“惠州爽炮” (@qiusuio), 48,476 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/qiusuio.

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.