Channel
@awananQQ
On this record: Growth · Engagement · Posts · Citations · Cite this entry
348subscribers
+13 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001108220695 |
|---|---|
| Type | Channel |
| Username | @awananQQ |
| Created | 17 September 2017 — measured — dated from the channel’s first post |
| First recorded | 3 September 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/awananQQ |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 19:57 | 348 | +10 |
| 4 Sept 2026, 01:15 | 338 | +3 |
| 3 Sept 2026, 10:15 | 335 | first reading |
8 posts held, back to 17 September 2017 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 8 (17 September 2017 – 3 September 2026) |
| Views total | 327 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:15 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.
晚安上货通知群 pinned «9.3 实时现货更新： 🥰月卡虚卡重启真绑系列：包弹窗爆红 可查可挑号 月卡多绑月亮 价格200 一卡绑一月亮 价格340 强推 月卡多绑单太 价格230 一卡绑一单太 价格400 强推 月卡多绑双太 价格250 一卡绑一双太 价格420 强推 月卡多绑靓号 价格360 一卡绑一靓号 价格520 强推 月卡真绑售后规则：月卡有效期内找回被改密全额退款 上号7天内死卡接不到码 补新号 🥰月卡私人地推假绑系列：包弹窗爆红 可查可挑号 月卡多绑月亮 价格150 一卡绑一月亮 价格340 强推 月卡多绑单太…»
9.3 实时现货更新： 🥰月卡虚卡重启真绑系列：包弹窗爆红 可查可挑号 月卡多绑月亮 价格200 一卡绑一月亮 价格340 强推 月卡多绑单太 价格230 一卡绑一单太 价格400 强推 月卡多绑双太 价格250 一卡绑一双太 价格420 强推 月卡多绑靓号 价格360 一卡绑一靓号 价格520 强推 月卡真绑售后规则：月卡有效期内找回被改密全额退款 上号7天内死卡接不到码 补新号 🥰月卡私人地推假绑系列：包弹窗爆红 可查可挑号 月卡多绑月亮 价格150 一卡绑一月亮 价格340 强推 月卡多绑单太 价格180 一卡绑一单太 价格380 强推 月卡多绑双太 价格200 一卡绑一双太 价格400 强推 月卡多绑三太 价格230 一卡绑一三太 价格420 强推 月卡假绑售后规则：月卡有效期内找回被改密全额退款 上号7天内死卡接不到码 补新号 🥰私人回流扫码系列： 强推 稳定耐操 挂着不死 扫码星星 价格90…
➖➖➖ 能量闪租 ➖➖➖ 🔴转账前，请复制下方地址转入指定TRX后再去转账。 🔴 价格详情： • 1 笔 USDT 转账：2 TRX • 2 笔 USDT 转账：4 TRX • 3 笔 USDT 转账：6 TRX • 4 笔 USDT 转账：8 TRX • 5 笔 USDT 转账：10 TRX （对方地址无 U 或交易所需要两笔能量） 点击地址自动复制： TA52Wn38Th68DPKJYFwCpGz5ygVfbeZ3Rq 🔴 能量有效期：1小时 自助兑换机器人：@qqanBot
原客服号已冻结 拿货联系新飞机客服 @wanan9688
为什么要上一卡一绑 具体原因如下： 一张手机卡 可以绑定5个QQ 5个QQ 当中有一个用死的话 会连带手机卡上面绑定的4个QQ一起死 QQ登录没使用 挂着就死 动不动就封号 就是因为一卡多绑原因造成 有条件的客户 推荐上一卡绑一Q 这样就不存在上述情况 Q用死了 这张卡还可以继续进行绑定新号 强力推荐一卡绑一Q 虽然价格贵些 但是客户留住了
晚安上货通知群 pinned «🥰关于售后 避免扯皮 看懂在贸易 1. 本人在售的所有月卡号 发货时会给你标注下卡时间 下卡后无售后 务扯皮 2. 在我这里拿的月卡号或换绑卡位 留卡有效期内 被扫全额赔偿 补新号或退款 3. 所售的月卡号+卡位 有效期内如遇到死卡 掉实名 涉案 天灾 只补卡位钱 感谢大家长期以往的支持 晚安ID @wanan9699 客服ID @wanan9688»
🥰关于售后 避免扯皮 看懂在贸易 1. 本人在售的所有月卡号 发货时会给你标注下卡时间 下卡后无售后 务扯皮 2. 在我这里拿的月卡号或换绑卡位 留卡有效期内 被扫全额赔偿 补新号或退款 3. 所售的月卡号+卡位 有效期内如遇到死卡 掉实名 涉案 天灾 只补卡位钱 感谢大家长期以往的支持 晚安ID @wanan9699 客服ID @wanan9688
Channel created
Showing the 8 most recent of 8 posts we hold for @awananQQ. 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.
Named by 2 registered channels — 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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“晚安上货通知群” (@awananQQ), 348 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/awananQQ.
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.