Telegram RegisterThe public register of Telegram
Telegram profile photo for 硬核🚀科技推送🔥热点新闻&吃瓜🍉🔞

Channel

硬核🚀科技推送🔥热点新闻&吃瓜🍉🔞

@chigua_007

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

57,006subscribers

-817 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002030401233
TypeChannel
Username@chigua_007
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/chigua_007

Topic

Gaming — 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 77% 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.

Growth

57,00657,82357,414.57 August 2026 — 57,823 subscribers7 August 2026 — 57,823 subscribers7 August 2026 — 57,818 subscribers8 August 2026 — 57,785 subscribers9 August 2026 — 57,736 subscribers10 August 2026 — 57,719 subscribers11 August 2026 — 57,722 subscribers12 August 2026 — 57,703 subscribers13 August 2026 — 57,686 subscribers14 August 2026 — 57,667 subscribers16 August 2026 — 57,641 subscribers17 August 2026 — 57,615 subscribers18 August 2026 — 57,588 subscribers19 August 2026 — 57,577 subscribers20 August 2026 — 57,555 subscribers21 August 2026 — 57,560 subscribers23 August 2026 — 57,549 subscribers24 August 2026 — 57,520 subscribers25 August 2026 — 57,504 subscribers26 August 2026 — 57,470 subscribers27 August 2026 — 57,457 subscribers28 August 2026 — 57,442 subscribers29 August 2026 — 57,440 subscribers30 August 2026 — 57,421 subscribers31 August 2026 — 57,389 subscribers1 September 2026 — 57,370 subscribers2 September 2026 — 57,372 subscribers4 September 2026 — 57,353 subscribers6 September 2026 — 57,314 subscribers9 September 2026 — 57,256 subscribers11 September 2026 — 57,181 subscribers13 September 2026 — 57,123 subscribers15 September 2026 — 57,066 subscribers17 September 2026 — 57,006 subscribers7 August 202617 September 2026
34 measurements spanning 41 days, net -817. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 56,883–57,946 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
17 Sept 2026, 13:5657,006-60
15 Sept 2026, 14:4157,066-57
13 Sept 2026, 19:4057,123-58
11 Sept 2026, 23:5857,181-75
9 Sept 2026, 14:5957,256-58
6 Sept 2026, 10:4157,314-39
4 Sept 2026, 04:5657,353-19
2 Sept 2026, 19:0357,372+2
1 Sept 2026, 15:1257,370-19
31 Aug 2026, 16:1857,389-32
30 Aug 2026, 15:1357,421-19
29 Aug 2026, 16:4557,440-2
28 Aug 2026, 19:3657,442-15
27 Aug 2026, 18:1857,457-13
26 Aug 2026, 17:5457,470-34
25 Aug 2026, 14:3357,504-16
24 Aug 2026, 18:0457,520-29
23 Aug 2026, 02:4657,549-11
21 Aug 2026, 16:0357,560+5
20 Aug 2026, 16:4657,555first reading

Engagement

633 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 95 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.973%
avg views ÷ 57,006 subscribers
Avg views / post
555
498 posts measured
Reaction rate
0.238%
reactions ÷ views · ER floor
Posts in window
499
of 633 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 172 of 498 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 September 2026
Posts held633 (6 August 202622 September 2026)
Views total276,204
Reactions total330
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 03:18 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

Photos
22,300
Videos
29,900
Links
1,630

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.

Video runtime
4h 48m
Average length
47s

Measured directly from 370 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.

Reaction mix

516 reactions across 228 posts, in 12 distinct kinds. The most used accounts for 34.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
17634.1%
👍8817.1%
😁8817.1%
💩6212.0%
🤡244.65%
👏152.91%
🤣152.91%
🔥142.71%
👎132.52%
🥰112.13%
🙏91.74%
😈10.194%

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 250 of the 633 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 516 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 633 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.

Recent posts

22 Sept 2026, 00:34 UTC172 viewsread 22 September 2026
Photo

😂🤯 code 的 GitHub commit 留言区玩梗大赏 Zcode 开源出来的仓库,居然只留下两次 commit,PR 和 issue 也都被关停;code 的 GitHub commit 留言区因此化为一场声势不小的玩梗狂欢😂 #玩梗现场 #开源仓库 #评论区

22 Sept 2026, 00:33 UTC38 viewsread 22 September 2026
Forwarded from @guangaojijinPhoto

💎🎰🙌💵 😀💰💸💸 💳💳💳💳💳💳💳💳💳 💳💳💳💳💳💳💳💳💳 🧐专业服务 超高限红 毫秒出款 ❤视讯 — 索莱尔/DB/CQ9高限红 ❤电子 — PG/PP/CQ9 一注2000 ❤彩票 — 独家综艺28/哈希区块彩 🏆OK游戏中心 公群9 入驻300万U 🏆新币担保 公群999 入驻100万U 官方网址 ➔ 9Y.COM 官方飞投 ➔ @GF9Y 官方唯一客服 ➔ @KF9Y 官方唯一频道 ➔ @WWW9YCOM 💎🐋🐋🐋🐋🐋🐋🐋🐋💎

21 Sept 2026, 10:19 UTC591 views1 reactionsread 22 September 2026
Photo

🛶💼 商务漂流、文旅、陪玩、女团与潜规则 国内简直什么都能搞成商务,这股商务风终究也刮到了漂流;连我这个没去漂流的人,看了都忍不住心动😀 #商务漂流 #文旅 #陪玩 #潜规则

😁1

21 Sept 2026, 10:15 UTC529 viewsread 22 September 2026
Video

😍🔥 顶配黑珍珠,黑皮肤靓女,身段也还将就。

21 Sept 2026, 10:10 UTC197 viewsread 21 September 2026
Video

⛑️🥊 戴上安全帽,外卖员打架占大便宜了

Showing the 12 most recent of 633 posts we hold for @chigua_007. 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.

Posts edited after publishing

@chigua_007 edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
19 August 2026
Most recent edit
27 August 2026

Forward network

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.

Mentions

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.

Channels Telegram recommends alongside this one

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.

(吃瓜)搞笑😐视频
@cgbg8 · 107,027
#1
奇趣💋百科💋内涵💋吃瓜
@qiqubaike11 · 2,581
#2
全网吃瓜
@DBHR8 · 19,064
#3
轻口味时间
@lightrekt · 49,340
#4
快来吃瓜
@renrenchigua · 68,565
#5
吃瓜大队
@JNAF8888 · 7,900
#6
吃瓜🍉群众
@achiguao · 81,872
#7
吃瓜🍉|搞笑🥸|软色情🥵|树洞投稿📮
@onlychigua · 200,649
#8
新闻报道📰热点时事
@TDKNEWS · 3,126
#9
搞笑视频 吃瓜群众 内涵段子 沙雕日常
@lsd62 · 25,101
#10
觉醒攻略
@juexinggonglue · 16,248
#11
吃瓜大佬(热点 黑料 搞笑)
@chiguaou · 20,805
#12
新闻🌜🌱瓜秧🌱🌛 #吃瓜 #爆料 #门事件 #每日新闻
@bf_gy · 23,282
#13
缅甸打人|缅北吃瓜新闻
@miandiandaren123 · 9,960
#14
Free•News
@NFSCHimalayaNews · 9,527
#15

Read from Telegram’s recommendation API, most recently 25 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.

Appears in Telegram’s recommendations for other channels

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.

轻口味时间
@lightrekt · 49,340
Telegram ranks this channel #8 of 35 here — alongside 34 others — read 25 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“硬核🚀科技推送🔥热点新闻&吃瓜🍉🔞” (@chigua_007), 57,006 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/chigua_007.

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.