Telegram RegisterThe public register of Telegram
Telegram profile photo for 嫦娥吃西瓜🍉吃瓜频道

Channel

嫦娥吃西瓜🍉吃瓜频道

@cgyl18

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

25,901subscribers

+16,172 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003933987961
TypeChannel
Username@cgyl18
Description吃瓜+曝光+娱乐+休闲+供需+关注点个赞👍🏼 🌙大月亮交流群 @zljaq 🎓海外商务大业绩 @ttttt106 🍵素材频道 @dylsc18 🔞夜间情欲 @yjqy18 🍉嫦娥吃西瓜 @cgyl18
CreatedBetween 1 April 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held54
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/cgyl18

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 4 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@dylsc18/938822 Oct 2026, 11:39 UTC@cgyl18/12795 · this entry4 Oct 2026, 06:58 UTC1.0043 hours
@cgyl18/13001 · this entry6 Oct 2026, 01:53 UTC@dylsc18/965286 Oct 2026, 13:51 UTC1.0012 hours
@dylsc18/990389 Oct 2026, 05:58 UTC@cgyl18/13555 · this entry10 Oct 2026, 16:26 UTC1.0034 hours
@dylsc18/10445418 Oct 2026, 18:02 UTC@cgyl18/14771 · this entry19 Oct 2026, 11:45 UTC1.0018 hours
@cgyl18/15157 · this entry22 Oct 2026, 05:46 UTC@dylsc18/10635322 Oct 2026, 05:48 UTC1.002 minutes
@dylsc18/10732825 Oct 2026, 04:02 UTC@cgyl18/15389 · this entry25 Oct 2026, 04:02 UTC1.00under a minute
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
@dylsc1819 (8/8 hand-verifiable sample passed)1.0013 hours@dylsc18 (13–6)
@tuigsc6 (5/6 hand-verifiable sample passed)1.006.8 hoursthis entry (5–1)
@aichiguaba5 (5/5 hand-verifiable sample passed)1.002.3 hoursthis entry (3–2)
@ZTX955 (5/5 hand-verifiable sample passed)1.007.6 hours@ZTX95 (3–2)

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. 15 of the 15 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 175 comparable posts for this entry, running 7 August 2026 to 14 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).

Of the group of 5 channels, the one whose matching posts we hold earliest is @dylsc18. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 16 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.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5,95060,47433,2127 August 2026 — 9,729 subscribers8 August 2026 — 9,588 subscribers11 August 2026 — 9,325 subscribers15 August 2026 — 8,735 subscribers18 August 2026 — 8,059 subscribers21 August 2026 — 5,950 subscribers25 August 2026 — 11,821 subscribers26 August 2026 — 11,598 subscribers26 August 2026 — 11,407 subscribers27 August 2026 — 11,254 subscribers28 August 2026 — 11,007 subscribers29 August 2026 — 10,763 subscribers30 August 2026 — 10,573 subscribers31 August 2026 — 10,570 subscribers1 September 2026 — 10,465 subscribers2 September 2026 — 10,257 subscribers4 September 2026 — 10,147 subscribers7 September 2026 — 9,649 subscribers11 September 2026 — 9,018 subscribers14 September 2026 — 12,280 subscribers16 September 2026 — 11,953 subscribers18 September 2026 — 11,673 subscribers25 September 2026 — 60,474 subscribers3 October 2026 — 60,289 subscribers8 October 2026 — 60,270 subscribers12 October 2026 — 60,264 subscribers14 October 2026 — 60,209 subscribers15 October 2026 — 60,205 subscribers16 October 2026 — 60,202 subscribers17 October 2026 — 60,200 subscribers18 October 2026 — 60,196 subscribers19 October 2026 — 60,179 subscribers20 October 2026 — 60,174 subscribers22 October 2026 — 31,418 subscribers23 October 2026 — 27,696 subscribers24 October 2026 — 26,897 subscribers25 October 2026 — 26,780 subscribers26 October 2026 — 26,733 subscribers27 October 2026 — 26,700 subscribers28 October 2026 — 26,671 subscribers29 October 2026 — 26,651 subscribers30 October 2026 — 26,624 subscribers31 October 2026 — 26,604 subscribers1 November 2026 — 26,576 subscribers2 November 2026 — 26,571 subscribers3 November 2026 — 26,512 subscribers4 November 2026 — 26,468 subscribers5 November 2026 — 26,424 subscribers6 November 2026 — 26,369 subscribers7 November 2026 — 26,315 subscribers8 November 2026 — 26,264 subscribers10 November 2026 — 26,170 subscribers12 November 2026 — 26,106 subscribers15 November 2026 — 25,901 subscribers25,9017 August 202615 November 2026
54 measurements spanning 100 days, net +16,172. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)SubscribersChange
15 Nov 2026, 10:5525,901-205
12 Nov 2026, 01:0426,106-64
10 Nov 2026, 03:1726,170-94
8 Nov 2026, 15:0626,264-51
7 Nov 2026, 12:1726,315-54
6 Nov 2026, 13:3026,369-55
5 Nov 2026, 15:5626,424-44
4 Nov 2026, 17:1726,468-44
3 Nov 2026, 15:2926,512-59
2 Nov 2026, 12:0426,571-5
1 Nov 2026, 15:3026,576-28
31 Oct 2026, 16:5026,604-20
30 Oct 2026, 18:0926,624-27
29 Oct 2026, 18:2826,651-20
28 Oct 2026, 15:4026,671-29
27 Oct 2026, 18:0726,700-33
26 Oct 2026, 18:1526,733-47
25 Oct 2026, 17:1626,780-117
24 Oct 2026, 17:0626,897-799
23 Oct 2026, 14:0627,696first reading

Engagement

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

ERR · 30 days
1.80%
avg views ÷ 25,901 subscribers
Avg views / post
466
287 posts measured
Reaction rate
0.451%
reactions ÷ views · ER floor
Posts in window
287
of 894 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 2 of 287 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 held894 (7 August 2026 – 16 November 2026)
Views total133,652
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 17:58 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
≈6,080
Videos
≈11,400
Links
≈92

Lifetime counters from Telegram’s own channel header, read 16 November 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
8h 21m
Average length
39s

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

7 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤457.1%
😁228.6%
🌚114.3%

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

Measured over the 894 most recent posts we hold, published 7 August 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: 1 of 287 posts held from the last 30 days (0.348%) 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, 16:44 UTC643 viewsread 16 November 2026
Video

老头 #粗口 #骂人 骂习近平 骂共产党 不想领退休金啦?

16 Nov 2026, 16:44 UTC14 viewsread 16 November 2026
Photo

在尼泊尔加德满 中国人跟白人干架 结果被一拳OK 这是国外 视频看来 白人已经很克制了 你不断动手挑衅 就事论事 #打架 #一拳ko

16 Nov 2026, 16:44 UTC689 viewsread 16 November 2026
Video

一名14岁的日本女孩,在TikTok上直播时,意外从六楼阳台坠落。直播期间她将手机放在一旁,坐在阳台边缘,片刻后发生意外,造成悲剧性的结局 #日本妞 #跳楼 #自杀 #直播

16 Nov 2026, 07:03 UTC31 viewsread 16 November 2026
Video

人类的文明。马斯克的 SpaceX 星舰,今早完成第 15 次综合试飞,在太空释放 26 颗星链 V3 卫星,飞行约 22.5 小时后,从轨道返回,被地面发射塔的筷子臂成功捕获。 这是人类历史上,首次从太空轨道返回,并被塔臂抓住的星舰上层飞船。

16 Nov 2026, 07:03 UTC728 viewsread 16 November 2026
Video

上海市,魔法攻击,车上没两瓶矿泉水还打不赢嘞 #吐口水

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

Mentions

Named by 4 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“嫦娥吃西瓜🍉吃瓜频道” (@cgyl18), 25,901 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/cgyl18.

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.