Telegram RegisterThe public register of Telegram
Telegram profile photo for 快来吃瓜

Channel

快来吃瓜

@renrenchigua

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

68,321subscribers

-18 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001521754979
TypeChannel
Username@renrenchigua
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/renrenchigua

Topic

Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@renrenchigua/278633 · this entry6 Aug 2026, 18:38 UTC@chigua2022/3344586 Aug 2026, 18:38 UTC1.00under a minute
@chigua2022/33495212 Aug 2026, 05:45 UTC@renrenchigua/278861 · this entry12 Aug 2026, 08:55 UTC1.003.2 hours
@chigua2022/3371181 Sept 2026, 11:57 UTC@renrenchigua/279919 · this entry1 Sept 2026, 21:32 UTC1.009.6 hours
@chigua2022/33967826 Sept 2026, 10:51 UTC@renrenchigua/281205 · this entry26 Sept 2026, 17:15 UTC1.006.4 hours
@renrenchigua/281254 · this entry27 Sept 2026, 18:49 UTC@chigua2022/33980527 Sept 2026, 22:00 UTC1.003.2 hours
@chigua2022/3403232 Oct 2026, 23:41 UTC@renrenchigua/281534 · this entry3 Oct 2026, 02:52 UTC1.003.2 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@chigua20228 (8/8 hand-verifiable sample passed)1.003.2 hourseven

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 4 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 261 comparable posts for this entry, running 6 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_mutual, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

68,15268,59268,37268,3216 August 202616 November 2026
65 measurements spanning 102 days, net -18. 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 68,086–68,658 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
16 Nov 2026, 22:1968,321-64
13 Nov 2026, 16:2168,385-29
11 Nov 2026, 01:5868,414+6
9 Nov 2026, 08:1768,408-25
8 Nov 2026, 01:3168,433-25
6 Nov 2026, 19:4768,458-9
5 Nov 2026, 16:2968,467+6
4 Nov 2026, 13:3668,461+28
3 Nov 2026, 11:4168,433-10
2 Nov 2026, 08:2068,443+2
1 Nov 2026, 05:2968,441-10
31 Oct 2026, 08:4068,451+10
30 Oct 2026, 07:5168,441+15
29 Oct 2026, 04:2768,426-6
27 Oct 2026, 23:0068,432+25
27 Oct 2026, 00:0568,407+9
25 Oct 2026, 21:1068,398-4
24 Oct 2026, 22:1668,402-4
24 Oct 2026, 01:2768,406-10
22 Oct 2026, 21:5868,416first reading

Engagement

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

ERR · 30 days
0.799%
avg views ÷ 68,321 subscribers
Avg views / post
546
464 posts measured
Reaction rate
0.241%
reactions ÷ views · ER floor
Posts in window
464
of 1,837 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 242 of 464 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 16 November 2026
Posts held1,837 (6 August 2026 – 16 November 2026)
Views total253,381
Reactions total376
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 21:34 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

Video runtime
9h 39m
Average length
52s

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

716 reactions across 444 posts, in 16 distinct kinds. The most used accounts for 65.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍46665.1%
❤19627.4%
👏131.82%
🤣70.978%
😁60.838%
🥰60.838%
🔥50.698%
🤯40.559%
🎉30.419%
🤡30.419%
⚡20.279%
👎10.14%
💩10.14%
🕊10.14%
😭10.14%
🤩10.14%

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

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 September 2026 to 16 November 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

Telegram’s own ‘edited’ marker: 13 of 464 posts held from the last 30 days (2.80%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 21:09 UTC27 views1 reactionsread 16 November 2026

| 次元色色◆A3◆精品互推车队 | ●COS美颜姬 #NSFW ~COSBIKA ●精神小妹纹身母狗 ●媚黑联盟|黑人BBC ●吃瓜群众🍉 ●三梦的美颜🔞AV 【第六梦】 ●黄文小说⭐恶堕女帝 ●[NSFW]SM交流资源🔞 ●快来吃瓜 ●窥视天下 ●TS奴隶俱乐部 💋SM调教 ●菊之爱|肛交 爆菊 屁眼 ●露出 淫妻 多人 调教 ------------------------ ❤点击参与互推 ------------------------ ●乱伦圈●低价翻墙●主奴群 ●TS妖妖🌟仙女棒

👍1

16 Nov 2026, 15:36 UTC374 views3 reactionsread 16 November 2026
Video

🇬🇧 英国屠夫们游行展示一个巨大的充气猪排,反对穆斯林入侵英国

👍3

16 Nov 2026, 15:35 UTC362 views4 reactionsread 16 November 2026
Photo

放着也是放着,笑死啦 现在连鸡都没生意了,那就太严重了

👍3❤1

16 Nov 2026, 15:32 UTC361 viewsread 16 November 2026
Photo

上海瑞和苑外卖小哥灭门案的凶手找到了! 现在外卖员的压力越来越大,请大家保护好自己!

16 Nov 2026, 11:06 UTC615 views1 reactionsread 16 November 2026
Video

粉丝追星被口罩男一脚踢飞 哪位大明星啊

👍1

16 Nov 2026, 11:03 UTC570 views0 reactionsread 16 November 2026
Video

笑到肚子痛 我真的以为是耳机 没想到是被偷光零件的电动车🤣

16 Nov 2026, 11:02 UTC581 views2 reactionsread 16 November 2026
Video

真是不小心啊,锻炼身体一定要有人在,不然后果不堪设想。😅

❤2

16 Nov 2026, 11:01 UTC537 views2 reactionsread 16 November 2026
Video

这种体验感怎么样!有没有体验过的兄弟

❤1👍1

16 Nov 2026, 11:01 UTC511 viewsread 16 November 2026
Video

#台湾漫展 #烧姬 #coser #透明内裤 阴毛阴唇屁眼全看到

16 Nov 2026, 11:00 UTC498 views1 reactionsread 16 November 2026
Video

女婿竟与丈母娘开房发生不伦关系 被岳父和妻子当场抓奸 #女婿 #丈母娘 #抓奸

👍1

16 Nov 2026, 11:00 UTC481 viewsread 16 November 2026
Video

自从电车有守护模式以后,真的什么都能拍到。男的女的在车旁撒尿也就算了,人有三急都可以理解。 但是居然拍到一个女的在车旁蹲着撒尿,然后她老公还得乘机亲个嘴子,这是什么操作?!😨😨

Showing the 12 most recent of 1,837 posts we hold for @renrenchigua. 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 recorded as deleted after publishing

We recorded 152 posts on @renrenchigua as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
16 November 2026
Median time before seen missing
2.7 hours
Seen missing in the last 30 days
50

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 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.

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.

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.

硬核🚀科技推送🔥热点新闻&吃瓜🍉🔞
@chigua_007 · 55,386
Telegram ranks this channel #5 of 15 here — alongside 14 others — read 25 August 2026
轻口味时间
@lightrekt · 47,940
Telegram ranks this channel #6 of 35 here — alongside 34 others — read 25 August 2026
吃瓜群众【 猎奇】
@chiguadog · 155,874
Telegram ranks this channel #7 of 48 here — alongside 47 others — read 12 August 2026
吃瓜视频
@pdsss · 52,242
Telegram ranks this channel #16 of 51 here — alongside 50 others — read 23 August 2026
中国悲剧档案官方频道
@newszg_official · 155,840
Telegram ranks this channel #17 of 52 here — alongside 51 others — read 12 August 2026
吃瓜猎奇 幽默视频 搞笑段子
@ay2028 · 76,279
Telegram ranks this channel #21 of 57 here — alongside 56 others — read 18 August 2026
搞笑段子《问题不大》😹
@GXduanzi1 · 51,925
Telegram ranks this channel #26 of 55 here — alongside 54 others — read 13 August 2026
吃瓜群众🍉
@chigua_e · 213,920
Telegram ranks this channel #26 of 45 here — alongside 44 others — read 11 August 2026
东南亚大事件|海外事件|吃瓜曝光|今日头条
@miandianDS · 40,376
Telegram ranks this channel #28 of 50 here — alongside 49 others — read 27 August 2026
【吃瓜🍉&搞笑】
@GQSP9 · 55,452
Telegram ranks this channel #36 of 53 here — alongside 52 others — read 14 August 2026
全网吃瓜🍉
@aichiguaba · 246,005
Telegram ranks this channel #37 of 51 here — alongside 50 others — read 14 August 2026
生活素材包装【阿Q资讯】
@AQzx_7 · 67,391
Telegram ranks this channel #39 of 42 here — alongside 41 others — read 23 August 2026
中文吃瓜中心沙雕日常 🍉
@chigua_a · 214,479
Telegram ranks this channel #43 of 54 here — alongside 53 others — read 12 August 2026
🍉吃瓜搞笑俱乐部🌚
@cggxhhh · 260,017
Telegram ranks this channel #53 of 54 here — alongside 53 others — read 10 August 2026

This channel appears in 14 seed channels' Telegram-generated recommendation lists 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“快来吃瓜” (@renrenchigua), 68,321 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/renrenchigua.

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.