9月22日,四川发布 某小区高层外墙狭窄房檐上,两名小孩正在追逐跑动。 这里不是露台平台,只是楼房外沿窄窄的房檐,没有任何防护,脚下就是几十米高空,孩子来回奔跑,看着让人捏一把冷汗。 对面邻居拍到这惊险一幕,隔着屏幕都替他们担心。 家长一定要看管好孩子,千万不要让孩子跑到建筑外墙的房檐位置,一旦失足,后果不堪设想。♛♛
🤷♂1

Channel
@achiguao
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
81,872subscribers
-342 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001905442401 |
|---|---|
| Type | Channel |
| Username | @achiguao |
| Description | 吃瓜尽在 @achigua 绅士联盟 @tddk7 色瓜 正在创建 |
| Created | Between 1 March 2023 and 31 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/achiguao |
Memes & entertainment — 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 72% 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 |
|---|---|---|
| 18 Sept 2026, 03:40 | 81,872 | -25 |
| 15 Sept 2026, 22:20 | 81,897 | +16 |
| 14 Sept 2026, 07:39 | 81,881 | +15 |
| 12 Sept 2026, 15:16 | 81,866 | -30 |
| 10 Sept 2026, 15:21 | 81,896 | -43 |
| 7 Sept 2026, 15:02 | 81,939 | -62 |
| 4 Sept 2026, 19:38 | 82,001 | -8 |
| 3 Sept 2026, 07:58 | 82,009 | -25 |
| 2 Sept 2026, 05:05 | 82,034 | -24 |
| 1 Sept 2026, 06:36 | 82,058 | +1 |
| 31 Aug 2026, 03:55 | 82,057 | +2 |
| 30 Aug 2026, 07:13 | 82,055 | -19 |
| 29 Aug 2026, 05:34 | 82,074 | -5 |
| 28 Aug 2026, 08:25 | 82,079 | +25 |
| 27 Aug 2026, 08:06 | 82,054 | +42 |
| 26 Aug 2026, 07:24 | 82,012 | -20 |
| 25 Aug 2026, 04:25 | 82,032 | -29 |
| 24 Aug 2026, 03:06 | 82,061 | -9 |
| 22 Aug 2026, 07:46 | 82,070 | +50 |
| 20 Aug 2026, 20:34 | 82,020 | first reading |
793 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 97 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 170 of 478 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 793 (6 August 2026 – 22 September 2026) |
| Views total | 213,378 |
| Reactions total | 205 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 11:37 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.
Lifetime counters from Telegram’s own channel header, read 22 September 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.
Measured directly from 711 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.
264 reactions across 194 posts, in 13 distinct kinds. The most used accounts for 45.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 120 | 45.5% | |
| ❤ | 111 | 42.0% | |
| 👏 | 11 | 4.17% | |
| 😁 | 5 | 1.89% | |
| 🥰 | 5 | 1.89% | |
| 🤡 | 3 | 1.14% | |
| ⚡ | 2 | 0.758% | |
| 🎉 | 2 | 0.758% | |
| 💩 | 1 | 0.379% | |
| 🕊 | 1 | 0.379% | |
| 🤩 | 1 | 0.379% | |
| 🤮 | 1 | 0.379% | |
| 🤷♂ | 1 | 0.379% |
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 228 of the 793 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 264 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 793 most recent posts we hold, published 6 August 2026 to 22 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.
9月22日,四川发布 某小区高层外墙狭窄房檐上,两名小孩正在追逐跑动。 这里不是露台平台,只是楼房外沿窄窄的房檐,没有任何防护,脚下就是几十米高空,孩子来回奔跑,看着让人捏一把冷汗。 对面邻居拍到这惊险一幕,隔着屏幕都替他们担心。 家长一定要看管好孩子,千万不要让孩子跑到建筑外墙的房檐位置,一旦失足,后果不堪设想。♛♛
🤷♂1
监控下的一幕
❤1
高市早苗抵达美国纽约肯尼迪国际机场,准备参加联合国大会,并与特朗普、泽连斯基等人会面。 日本共同社报道称,第81届联合国大会召开期间,高市早苗希望在纽约和特朗普举行一场双边会晤,为了能凑上特朗普的时间,日方做了一个非常刻意的调整。 原本高市早苗在联合国大会的发言,排到了9月24日。为了抢窗口,日方硬生生把发言时间提前到22日下午。 只因特朗普21日、22日会到联大参会,开完会很快就要返回华盛顿,留给双边会谈的时间少得可怜。♛♛
🤮🤮好恶心
🌚
🤣🤣
印度喀拉拉邦卡萨拉戈德,一辆摩托车与一辆正在转弯的吉普车猛烈相撞。📹
醉酒乘客把网约车车门吐脏,只想用纸擦擦不肯赔钱。民警现场调解,纸巾擦不干净,造成财产损失就该赔偿,网约车司机真的很不容易…📹
大爷是耳聋没听到?📹
婚姻里不要动不动就提离婚,很小的事尽量自己去做,顾好自己,有能力爱另一半📹
一名自称村干部的醉酒男子,阻拦收割机秋收作业。与跨区作业的农机手发生激烈争执,言语粗暴,强行拦停机器。 据视频发布者描述:“当时这边正常开展收割,一开始并不认识对方,收割的地块是对方弟弟家的,事后才知晓双方是亲属。对方突然上前拦截收割机,我方担心机器链条会伤到他,提醒其远离,对方随即对收割机上作业人员动手”。♛♛
山东发布,孙子和爷爷公园玩从山上掉下来到救护车拉走,一动不动,也不哭也不挣眼,就像睡着了一样,希望孩子没事。♛♛
Showing the 12 most recent of 793 posts we hold for @achiguao. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
兄弟们对这两天的吃瓜内容满意吗
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 793 most recent posts we hold, published 6 August 2026 to 22 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 7 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.
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.
@achiguao named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 18 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“吃瓜🍉群众” (@achiguao), 81,872 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/achiguao.
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.