SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。 🔗 本频道专属邀请链接 https://t.me/sosoo?start=autopromo_-1002715997379_7544809516_soso_4a58eed0
👍1

Channel
@chiguaa258
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
21,107subscribers
-3,633 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 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 52 |
| Confirmed unchanged | 1 time, most recently 28 October 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 15:37 | 21,107 | +379 |
| 27 Oct 2026, 13:46 | 20,728 | -105 |
| 26 Oct 2026, 13:37 | 20,833 | +828 |
| 25 Oct 2026, 10:01 | 20,005 | -82 |
| 24 Oct 2026, 10:54 | 20,087 | -191 |
| 23 Oct 2026, 13:07 | 20,278 | -118 |
| 22 Oct 2026, 12:20 | 20,396 | -158 |
| 21 Oct 2026, 05:11 | 20,554 | -124 |
| 20 Oct 2026, 05:37 | 20,678 | -98 |
| 19 Oct 2026, 08:58 | 20,776 | -93 |
| 18 Oct 2026, 11:14 | 20,869 | -52 |
| 17 Oct 2026, 10:46 | 20,921 | -198 |
| 16 Oct 2026, 10:06 | 21,119 | -83 |
| 15 Oct 2026, 11:19 | 21,202 | -140 |
| 14 Oct 2026, 12:37 | 21,342 | -239 |
| 12 Oct 2026, 21:30 | 21,581 | -437 |
| 8 Oct 2026, 12:37 | 22,018 | -556 |
| 4 Oct 2026, 02:18 | 22,574 | +1,157 |
| 25 Sept 2026, 10:41 | 21,417 | -1,155 |
| 19 Sept 2026, 02:20 | 22,572 | first reading |
425 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 70 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 12 of 78 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 October 2026 |
|---|---|
| Posts held | 425 (7 August 2026 – 11 October 2026) |
| Views total | 83,785 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Oct 2026, 08:17 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 297 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.
27 reactions across 26 posts, in 8 distinct kinds. The most used accounts for 25.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 25.9% | |
| 🔥 | 6 | 22.2% | |
| ⚡ | 4 | 14.8% | |
| 🎉 | 3 | 11.1% | |
| 👍 | 3 | 11.1% | |
| 😁 | 2 | 7.41% | |
| 🙏 | 1 | 3.70% | |
| 🥰 | 1 | 3.70% |
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 30 of the 425 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 425 most recent posts we hold, published 7 August 2026 to 11 October 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.
SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。 🔗 本频道专属邀请链接 https://t.me/sosoo?start=autopromo_-1002715997379_7544809516_soso_4a58eed0
👍1
英约克郡野生动物园出意外 一名男子被老虎咬成重伤 周六,一名男子在英格兰北部约克郡野生动物园(Yorkshire Wildlife)遭到老虎袭击,身受重伤。 南约克郡警方表示,他们于下午1点30分左右接到报案,称一名男子进入了位于唐卡斯特附近的约克郡野生动物园的老虎围栏。 警方在一份声明中表示:“老虎随后袭击了该男子,导致其身受重伤。” 警方补充道:“事件发生后,老虎仍留在围栏内,公众安全不会受到影响。” 据同一消息来源称,动物园已疏散人员,警方仍在现场进行调查。野生动物园证实,老虎围栏内发生了一起“严重事件”,导致该围栏周末剩余时间关闭。约克郡救护车服务中心报告称,已派出两辆救护车和一支空中救援队前往现场。 这个名为“老虎乐园”的景点设有一条300米长的架空步道,游客可以沿着步道观赏西伯利亚虎在它们的围栏内活动。围栏内包括一片树林、一片草地和一个带瀑布的水池。 据估计,这种濒危亚种的西伯利亚虎在野外仅存约500只。
凡日本反华人士,都被台湾邀请去参加双十节活动。
英国独立电视新闻(ITN)公布了约4小时此前未公开的1989年天安门事件影像。画面由当年将录像带秘密带出中国的摄制组拍摄。 这些资料被封存约35年,其中包括一段时长约2小时的对抗影像汇编,以及约90分钟在事发后几天秘密拍摄的原始素材,记录了北京街头的军用卡车、人群和事后景象。
泰勒·斯威夫特昨晚在纽约市现身,看起来婚后很幸福。
央视新闻周刊对此前中埃“文明之鹰-2026”的报道,埃方空军对解放军空军电子干扰能力非常认可
当地时间10月10日下午,一名男子闯进约克郡野生动物园的老虎活动区域,遭到老虎袭击,最终不治身亡。警方正在调查事件具体经过。根据约克郡野生动物园官网介绍,该园于2009年4月开放,主要开展野生动物保护、濒危物种繁育及公众教育等活动。园内饲养有东北虎、北极熊、狮子等动物。#动物园 #事故 #老虎 #咬人 #吃人 #作死
大二专科生,靠切片3年赚了700万
破成这样还能刀一下 🔪 租房 #环境 堪忧 !
❤1
深夜 #飙车 #极速飞车 #车祸 拿生命当儿戏
#结婚 吃席 #打架 大无语事件
7日,河北。这两个孩子家的大人也不管管吗?太危险了。 #爬车 兜风 #危险驾驶
Showing the 12 most recent of 425 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.
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 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.
@chiguaa258 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.
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“吃瓜不吐籽🍉” (@chiguaa258), 21,107 subscribers as measured 28 October 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.