😨腾龙 × 银钻 × 钻石,三大娱乐 😨腾龙领势、银钻稳势、钻石加速 😨三平台一条心,靠谱从不掉链子 充值/提现 : 人民币😨USD😨缅币 😀 银钻娱乐 : yz1089.com 😒腾龙娱乐 : TL10380.com 钻石娱乐 : ty6611.cc 邀请码78912 😋😋😋 @AAUV8 🇷🇼🇺🇸🇵🇷🇵🇰🍉🏆🥇🎉🎁🎁🎁 赌场频道 https://t.me/+0nxYjAQ7XM41MWRl

Channel
爆笑情报站
@chigua_aauv88
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7,615subscribers
-35 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003529837986 |
|---|---|
| Type | Channel |
| Username | @chigua_aauv88 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/chigua_aauv88 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 11:59 | 7,615 | -11 |
| 7 Sept 2026, 01:18 | 7,626 | -13 |
| 2 Sept 2026, 17:46 | 7,639 | -3 |
| 31 Aug 2026, 02:44 | 7,642 | -5 |
| 28 Aug 2026, 10:32 | 7,647 | +1 |
| 22 Aug 2026, 09:45 | 7,646 | -2 |
| 18 Aug 2026, 14:12 | 7,648 | -1 |
| 15 Aug 2026, 16:05 | 7,649 | -1 |
| 11 Aug 2026, 07:00 | 7,650 | no change |
| 11 Aug 2026, 06:50 | 7,650 | first reading |
Engagement
58 posts held, back to 9 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 9 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.73%
- avg views ÷ 7,615 subscribers
- Avg views / post
- 741
- 20 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 58 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 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 August 2026 |
|---|---|
| Posts held | 58 (9 August 2026 – 18 August 2026) |
| Views total | 14,825 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 21:14 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
- 37m 24s
- Average length
- 39s
Measured directly from 57 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
大饱眼福,气氛拉满 #吃瓜
这个黑色的脸谱做的真逼真 #吃瓜
真正睡着的猫,尾巴是不会放下的 #吃瓜
你俩都吃方便面了,还互相伤害 #吃瓜
墙都不服,就服你!我的兄弟! #吃瓜
玩着玩着怎么还急眼了! #吃瓜
我还以为是条狗 #吃瓜
这才是严丝合缝、密不透风。 #吃瓜
这个绝了!舒淇在宝格丽晚宴即兴跳舞! #吃瓜
把我快笑死了 #吃瓜
不白来,都不白来哦。 #吃瓜
Showing the 12 most recent of 58 posts we hold for @chigua_aauv88. 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.
Forward network
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“爆笑情报站” (@chigua_aauv88), 7,615 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/chigua_aauv88.
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.