好久没这么开心了,以后都叫我大帅哥!助人为乐
🔥1

Channel
@chiguaa258
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
22,572subscribers
-2,168 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002715997379 |
|---|---|
| Type | Channel |
| Username | @chiguaa258 |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/chiguaa258 |
Personal blog — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 02:20 | 22,572 | -375 |
| 16 Sept 2026, 20:36 | 22,947 | +343 |
| 15 Sept 2026, 00:20 | 22,604 | -354 |
| 13 Sept 2026, 09:40 | 22,958 | -162 |
| 11 Sept 2026, 12:19 | 23,120 | +368 |
| 8 Sept 2026, 16:38 | 22,752 | -457 |
| 5 Sept 2026, 11:58 | 23,209 | -501 |
| 3 Sept 2026, 13:19 | 23,710 | -227 |
| 2 Sept 2026, 04:24 | 23,937 | -49 |
| 1 Sept 2026, 03:58 | 23,986 | -103 |
| 31 Aug 2026, 01:27 | 24,089 | -323 |
| 29 Aug 2026, 22:26 | 24,412 | -12 |
| 29 Aug 2026, 00:52 | 24,424 | -41 |
| 27 Aug 2026, 21:58 | 24,465 | -134 |
| 26 Aug 2026, 22:23 | 24,599 | -117 |
| 25 Aug 2026, 21:53 | 24,716 | -124 |
| 24 Aug 2026, 20:17 | 24,840 | -312 |
| 23 Aug 2026, 04:59 | 25,152 | +23 |
| 21 Aug 2026, 17:17 | 25,129 | -738 |
| 20 Aug 2026, 18:38 | 25,867 | first reading |
318 posts held, back to 7 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 56 pages 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. It is computed over the 7 of 137 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 318 (7 August 2026 – 3 September 2026) |
| Views total | 86,960 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:53 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.
Measured directly from 223 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.
10 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 40.0% | |
| 🔥 | 3 | 30.0% | |
| ⚡ | 1 | 10.0% | |
| 🎉 | 1 | 10.0% | |
| 👍 | 1 | 10.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 13 of the 318 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 318 most recent posts we hold, published 7 August 2026 to 3 September 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.
好久没这么开心了,以后都叫我大帅哥!助人为乐
🔥1
简单吃点 👎
这段画面由 WNBC-TV 的 Chopper 4 直升机拍摄。摄像:April Amonica。 视频显示联合航空 175 号航班撞击世界贸易中心南塔。 2001 年 9 月 11 日,联合航空 175 号航班是第二架遭劫持的飞机,最终撞入世界贸易中心南塔。这架波音 767 客机撞击大楼的位置位于第 77 层至第 85 层之间。撞击发生 56 分钟后,南塔于上午 9 时 59 分坍塌。 2001 年 9 月 11 日当天,联合航空 175 号航班上共有 65 人,包括 56 名乘客(其中 5 人为劫机者)和 9 名机组人员。 乘客中有 50 名美国人,此外还有来自德国、英国、伊朗、以色列、印度尼西亚、爱尔兰和加拿大的人士。 飞机被蓄意撞入世界贸易中心南塔后,机上所有乘客和机组人员全部遇难。
第五架印度飞机已出发前往尼泊尔。 它携带一支11人救援队,配备专业设备,以及5.5吨基本药物。
苹果 CEO 特纳斯上任后,许多外国网友要求新购 iPhone 附赠充电头和耳机。
9月2日上午10点,西藏吉隆口岸救援通道陆路通道已基本打通,救援人员、救援物资和部分装备已通过陆路通道进入核心区并开展深入救援工作。
日本一名高中员工因涉嫌杀害 30 只仓鼠而被再次逮捕 8月31日,岩手县警察署宫古警察署再次逮捕了一名36岁的男性员工,该员工是岩手县宫古市宫古水产高等学校的员工,涉嫌违反《动物福利法》杀害多只仓鼠;同时,警方还以同样的罪名逮捕了一名来自北上市的20岁女性临时工。县警察署尚未透露两名嫌疑人是否认罪。 根据公告,两名嫌疑人涉嫌于3月下旬在泷泽市一家寄养设施内合谋杀害约30只仓鼠。两人还拍摄了作案过程的视频。他们事先并不认识,但通过社交媒体联系,并发送了诸如“一起杀仓鼠吧”之类的信息。 被告是一名男子,此前已因违反同一法律(杀害20多只仓鼠)而被捕并被起诉。此次指控是警方分析其智能手机后提出的。县警正在调查其作案动机及其他细节。
实力雄厚,百年好合! #结婚 订婚 收收小米 🤏
👍1
以为是邻桌发生口角,没想到是一桌的
美国没有任何车辆有特权超越停下的校车,哪怕是警车甚至是总统的座驾,都必须停下来。 评论啊 怎么不评论 !
韩国演员丁一宇为尼泊尔山洪灾区捐款 韩国演员丁一宇向儿童救助类非政府组织“好邻居”(Good Neighbors)捐款,用于帮助尼泊尔山洪灾区的居民与儿童。 好邻居方面2日表示,这笔善款将用于向尼泊尔努瓦科特等主要灾区提供紧急物资援助。好邻居上月28日起向努瓦科特灾民提供食品、生活用品和卫生用品等,并为受灾儿童设立安全活动空间,提供心理疏导与社区支持。 丁一宇通过此次捐款成为“好邻居俱乐部”成员。年捐款额超过1000万韩元(约合人民币4.9万元),并积极参与爱心的会员可加入该俱乐部。
🎉1
#火烧鸡 感受灼热 🔥
⚡1
Showing the 12 most recent of 318 posts we hold for @chiguaa258. 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 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“吃瓜不吐籽🍉” (@chiguaa258), 22,572 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/chiguaa258.
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.