😑 不慌的都:横穿马路.
❤1

Channel
@qiwen99
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
16,049subscribers
+484 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001604855251 |
|---|---|
| Type | Channel |
| Username | @qiwen99 |
| Created | Between 1 December 2021 and 30 April 2023 — 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 | 31 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/qiwen99 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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, 00:22 | 16,049 | +9 |
| 16 Sept 2026, 17:16 | 16,040 | +12 |
| 14 Sept 2026, 19:55 | 16,028 | +23 |
| 13 Sept 2026, 02:58 | 16,005 | +26 |
| 11 Sept 2026, 01:01 | 15,979 | +44 |
| 8 Sept 2026, 05:15 | 15,935 | +34 |
| 5 Sept 2026, 03:02 | 15,901 | +14 |
| 3 Sept 2026, 05:55 | 15,887 | +19 |
| 2 Sept 2026, 01:17 | 15,868 | +13 |
| 1 Sept 2026, 01:29 | 15,855 | +4 |
| 31 Aug 2026, 00:46 | 15,851 | +19 |
| 29 Aug 2026, 23:04 | 15,832 | -5 |
| 28 Aug 2026, 23:25 | 15,837 | +8 |
| 27 Aug 2026, 19:47 | 15,829 | +6 |
| 26 Aug 2026, 17:03 | 15,823 | +23 |
| 25 Aug 2026, 14:25 | 15,800 | +18 |
| 24 Aug 2026, 14:03 | 15,782 | +14 |
| 22 Aug 2026, 19:35 | 15,768 | +45 |
| 21 Aug 2026, 07:56 | 15,723 | +33 |
| 20 Aug 2026, 08:12 | 15,690 | first reading |
418 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 118 of 177 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 | 418 (7 August 2026 – 3 September 2026) |
| Views total | 11,138 |
| Reactions total | 127 |
| 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.
Measured directly from 308 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.
506 reactions across 280 posts, in 5 distinct kinds. The most used accounts for 21.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👏 | 111 | 21.9% | |
| ❤ | 110 | 21.7% | |
| 👍 | 108 | 21.3% | |
| 🔥 | 89 | 17.6% | |
| 🥰 | 88 | 17.4% |
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 283 of the 418 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 506 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 418 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
辅助驾驶 刹车油门失灵,事发前的120秒。 #刹车失灵 #车祸.
👍1
第一个月的工资是抚恤金! 这次尼泊尔泥石流一起悲伤的故事。 从皖北农村走出来,专升本,上岸985硕士,考上吉隆海关。8月21号上班,26号泥石流袭来! 上了26年学,上班4天,只尝到4天的甜,第一个月的工资就变成了抚恤金,太难受了 感谢家人们投稿!.
👏1
9月2日,云南,外卖小哥差点冲走了.
👏1
四川达州,空调师傅维修时掉下来了! 坑里的建筑是全世界最脑残的设计,安装个空调比拆核弹还危险!.
🔥1
福建福鼎到管阳104国道边上,唐阳村,暴雨引发山体滑坡,房屋被冲毁,有一对母子被压,不幸身亡 #山体滑坡.
❤1
🇺🇸 鳄鱼帮助警方抓捕逃犯。40岁的维克托·里瓦斯试图在路易斯安那州的沼泽中躲避警察。但一只鳄鱼袭击了他,并在水中咬了他的手。 尽管如此,里瓦斯仍然试图逃跑,但警方很快使用无人机找到了他。在医院接受治疗后,他将面临酒驾和妨碍逮捕的指控。 警局感谢这只爬行动物提供的帮助,甚至制作了一张带有玩笑性质的图片,称其为“年度杰出警员”。 #警察执法 #鳄鱼 #咬人 @chayin @chayin.
🇺🇸 一辆半挂卡车撞上了位于#Cincinnati的立交桥护栏,驾驶室悬挂在I-71高速公路上方,画面十分惊险,由俄亥俄州交通部门的视频记录。 据报道,8月30日发生的事故造成两人受伤,但预计他们会康复。由于救援人员正在努力固定卡车并清理现场,交通一度受到影响。 #车祸 #货车 悬挂 @chayin.
美国 🇺🇸 #NewYork。 一名男子从布莱顿海滩地铁站跑出来,捡起一个装满垃圾的容器,然后朝一位无辜的90岁老妇人扔了过去,老妇人在人行道上。 这是一起完全随机的袭击,发生在早上10点。 她被送往医院,而该男子逃走了。#迷惑行为 @chayin.
🥰1
美国 🇺🇸 在树下,撑着雨伞,拿着金属物品。 #StatenIsland 的一位男子(托马斯·法赫米)在去牙医诊所的路上被雷击中。 “当闪电击中我时,我全身感受到的最初感觉是前所未有的;刺痛、麻木、疼痛,我只觉得一种灼烧感……没有烧伤。我接受了多次身体检查,完全没有烧伤。星期天我去教堂,感谢上帝。” #闪电 #雷击 @chayin #倒霉.
👍1
#电瓶车 #烧车 锂电池炸弹.
🔥1
黑哥在中国大街上简单等个红灯就能加到集美的微信 #黑人 #亚洲马桶.
🥰1
Showing the 12 most recent of 418 posts we hold for @qiwen99. 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.
“奇闻趣事|开心TV|娱乐吃瓜” (@qiwen99), 16,049 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/qiwen99.
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.