Telegram RegisterThe public register of Telegram
Telegram profile photo for 吃瓜热点

Channel

吃瓜热点

@Hotchigua

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

77,986subscribers

+2,751 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-1001545015761
TypeChannel
Username@Hotchigua
Description🍉全网吃瓜热点频道|每日更新网红爆料、社会热议、娱乐资讯、网络新鲜事件、圈内内幕 专注分享网络热点见闻,理性吃瓜,内容仅供娱乐 🌠国际吃瓜中文版 @KIVRAC 🍉抖音热瓜版 @Hotdychigua123 🆙吃瓜备用 @Hot_chiguao 聊天群 @Htcgrdbl 📡投稿&广告 @hot_chigua_bot
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Hotchigua

Topic

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 99% 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

75,23177,98676,608.57 August 2026 — 75,235 subscribers7 August 2026 — 75,262 subscribers8 August 2026 — 75,251 subscribers9 August 2026 — 75,231 subscribers11 August 2026 — 75,249 subscribers12 August 2026 — 75,290 subscribers13 August 2026 — 75,300 subscribers14 August 2026 — 75,316 subscribers16 August 2026 — 75,360 subscribers17 August 2026 — 75,389 subscribers18 August 2026 — 75,530 subscribers19 August 2026 — 75,635 subscribers20 August 2026 — 75,903 subscribers21 August 2026 — 76,128 subscribers23 August 2026 — 76,280 subscribers24 August 2026 — 76,375 subscribers26 August 2026 — 76,401 subscribers27 August 2026 — 76,513 subscribers28 August 2026 — 76,553 subscribers29 August 2026 — 76,606 subscribers30 August 2026 — 76,656 subscribers31 August 2026 — 76,725 subscribers1 September 2026 — 76,760 subscribers2 September 2026 — 76,812 subscribers3 September 2026 — 76,963 subscribers4 September 2026 — 77,089 subscribers7 September 2026 — 77,344 subscribers10 September 2026 — 77,618 subscribers12 September 2026 — 77,748 subscribers14 September 2026 — 77,819 subscribers15 September 2026 — 77,929 subscribers18 September 2026 — 77,986 subscribers7 August 202618 September 2026
32 measurements spanning 42 days, net +2,751. 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 74,818–78,399 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
18 Sept 2026, 02:2077,986+57
15 Sept 2026, 23:1977,929+110
14 Sept 2026, 06:5977,819+71
12 Sept 2026, 12:1477,748+130
10 Sept 2026, 11:3977,618+274
7 Sept 2026, 03:3977,344+255
4 Sept 2026, 11:1677,089+126
3 Sept 2026, 01:1476,963+151
2 Sept 2026, 02:3776,812+52
1 Sept 2026, 01:3676,760+35
31 Aug 2026, 02:0476,725+69
30 Aug 2026, 03:1276,656+50
29 Aug 2026, 02:1976,606+53
28 Aug 2026, 01:2676,553+40
27 Aug 2026, 02:1276,513+112
26 Aug 2026, 00:5476,401+26
24 Aug 2026, 22:0876,375+95
23 Aug 2026, 06:3776,280+152
21 Aug 2026, 16:3776,128+225
20 Aug 2026, 17:1275,903first reading

Engagement

808 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 94 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.06%
avg views ÷ 77,986 subscribers
Avg views / post
824
537 posts measured
Reaction rate
0.263%
reactions ÷ views · ER floor
Posts in window
537
of 808 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 388 of 537 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 20 September 2026
Posts held808 (6 August 202620 September 2026)
Views total442,669
Reactions total906
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Sept 2026, 11:56 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,500
Videos
65,400
Links
1,880

Lifetime counters from Telegram’s own channel header, read 20 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
9h 42m
Average length
54s

Measured directly from 648 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

1,137 reactions across 491 posts, in 32 distinct kinds. The most used accounts for 45.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍52145.8%
35631.3%
😁383.34%
🤮292.55%
💩262.29%
🙏181.58%
🕊131.14%
😱131.14%
🤡131.14%
🤬131.14%
🥰131.14%
👎121.06%
👏110.967%
🤣100.88%
🤯100.88%
🔥60.528%
🤩60.528%
🖕40.352%
😢40.352%
🤔30.264%
12 further kinds181.58%

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 526 of the 808 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 1,137 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 808 most recent posts we hold, published 6 August 2026 to 20 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

20 Sept 2026, 10:32 UTC482 views1 reactionsread 20 September 2026
Video

网传湖南株洲天元区 情杀🤯🤯 #吃瓜 #情杀

👍1

20 Sept 2026, 10:29 UTC473 views4 reactionsread 20 September 2026
Photo

抖音趣事:一位广西籍女子远嫁巴基斯坦后遭遇挨打 穿黑袍,禁足,出门必须给家里婆婆打报告才被允许,和大家庭一起生活,每天一个人做饭 洗衣 带孩子 有时候还会和婆婆打架,好像护照被没收了,她是疫情的时候出去的,然后父亲去世都没能回去,🤓🤓🤓

👍4

20 Sept 2026, 10:29 UTC467 viewsread 20 September 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5226850793

20 Sept 2026, 10:08 UTC515 viewsread 20 September 2026
Video

https://t.me/Hotchigua/91191 听说30分钟抓到,贵州人,父母双亡,有个哥在东莞,没钱

20 Sept 2026, 09:35 UTC660 views3 reactionsread 20 September 2026
Photo

印度北方邦桑博尔因为种性问题 两个情侣不能结婚 双双选择上吊自杀

👍3

19 Sept 2026, 21:10 UTC374 viewsread 19 September 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5226850793

19 Sept 2026, 21:10 UTC368 views2 reactionsread 19 September 2026
Video

一个日本人在中国打出租车 抢客原因 上演妈逼大战 日本录像放X上🤡

👍1🤩1

19 Sept 2026, 20:59 UTC394 views1 reactionsread 19 September 2026
Video

长江边吃个瓜 两女争一男🌚🌚

👍1

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

15 Aug 2026, 08:37 UTCAnonymous Poll68 voters

我最近迷茫不知道发什么内容你们选一下吧

  1. 打架 偷情56%
  2. 网络热瓜 网红八卦24%
  3. 海外视频 国际时事6%
  4. 社会热议 车祸 随手拍 自然灾害15%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

15 Aug 2026, 08:31 UTCAnonymous Poll83 voters

色情版 每天更

  1. 一天90%
  2. 两天一更5%
  3. 三天一更5%

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 808 most recent posts we hold, published 6 August 2026 to 20 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 5 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.

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.

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

“吃瓜热点” (@Hotchigua), 77,986 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Hotchigua.

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.