Telegram RegisterThe public register of Telegram
Telegram profile photo for (广州探花)娱乐反馈报告

Channel

(广州探花)娱乐反馈报告

@GZBG8866

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

23,889subscribers

+5,657 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002762048918
TypeChannel
Username@GZBG8866
Description广州娱乐总榜单: https://t.me/GZYL8866 上榜合作留言: @wl0705ls_bot & @gzsbjqrbot 交流群: https://t.me/GZ08866
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/GZBG8866

Topic

Adult — 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 72% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@GZYL8866/510017 Aug 2026, 11:24 UTC@GZBG8866/2486 · this entry17 Aug 2026, 11:24 UTC1.00under a minute
@GZYL8866/65363 Oct 2026, 12:46 UTC@GZBG8866/3523 · this entry3 Oct 2026, 12:46 UTC1.00under a minute
@GZYL8866/720021 Oct 2026, 08:35 UTC@GZBG8866/3925 · this entry21 Oct 2026, 08:35 UTC1.00under a minute
@GZYL8866/734826 Oct 2026, 11:39 UTC@GZBG8866/4022 · this entry26 Oct 2026, 11:40 UTC1.00under a minute
@GZYL8866/800612 Nov 2026, 11:11 UTC@GZBG8866/4479 · this entry12 Nov 2026, 11:11 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
@GZYL88665 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (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. 2 of the 2 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 590 comparable posts for this entry, running 5 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

17,28524,95121,11823,8896 August 202617 November 2026
65 measurements spanning 102 days, net +5,657. 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 16,135–26,101 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
17 Nov 2026, 07:1623,889-108
14 Nov 2026, 01:0723,997-16
11 Nov 2026, 10:4924,013-37
9 Nov 2026, 16:1124,050+13
8 Nov 2026, 07:1924,037-74
7 Nov 2026, 03:1624,111-30
6 Nov 2026, 02:5624,141-13
4 Nov 2026, 23:2924,154-15
4 Nov 2026, 02:5124,169-24
3 Nov 2026, 03:4524,193-16
2 Nov 2026, 02:1124,209-58
31 Oct 2026, 22:3124,267-102
30 Oct 2026, 23:1024,369-118
29 Oct 2026, 22:3924,487-31
29 Oct 2026, 00:5724,518-89
27 Oct 2026, 21:1624,607-38
26 Oct 2026, 21:2924,645-44
25 Oct 2026, 19:2624,689-53
24 Oct 2026, 16:1524,742-55
23 Oct 2026, 19:0624,797first reading

Engagement

638 posts held, back to 5 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 162 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.57%
avg views ÷ 23,889 subscribers
Avg views / post
375
250 posts measured
Reaction rate
0.219%
reactions ÷ views · ER floor
Posts in window
250
of 638 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 32 of 250 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 17 November 2026
Posts held638 (5 August 2026 – 17 November 2026)
Views total93,659
Reactions total26
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 17:53 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
≈118
Videos
≈6
Links
≈1,650

Lifetime counters from Telegram’s own channel header, read 17 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
23s
Average length
12s

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

53 reactions across 51 posts, in 3 distinct kinds. The most used accounts for 92.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4992.5%
👍23.77%
🔥23.77%

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

Measured over the 638 most recent posts we hold, published 5 August 2026 to 17 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: 8 of 250 posts held from the last 30 days (3.20%) 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).

17 Nov 2026, 15:44 UTC81 viewsread 17 November 2026

【时间】:2026-11-17 【老师】:甜崽 【留名】:如果这一秒钟你跟我讲从未爱我 【评价】:👍 好评 【人照】:9 【颜值】:10 【身材】:9 【服务】:9 【态度】:9 【环境】:9 【综合】:9.17 【过程】:临时起意,看到老师有空,所以约课,平时这个时间点都约不到。隔了几个月老师还是那么害羞,服务还是可以的,女上还是很能桩的。第二次来了,感觉还是不错的,下次还会返的。

17 Nov 2026, 12:33 UTC171 views1 reactionsread 17 November 2026

【时间】:2026-11-17 【老师】:雨汐 【留名】:匿名 【评价】:👍 好评 【人照】:9 【颜值】:9 【身材】:10 【服务】:10 【态度】:10 【环境】:10 【综合】:9.67 【过程】:下班就飞过来找老师了,约了两天终于开课了,进门一看bbw,身材满分,进来之后会帮忙洗澡,服务很周到,常规流程之后就到房间了,老师放的很开,直接就喊宝宝我要,然后就常规口法交流,口技很好哦,差点出来了,然后我一拍屁股就懂了,然后就123123,很润水很多,很主动,🐍的很放开,带着烧烧的,然后后面实在出不来了然后手打出来的,做完之后还带服务洗澡按摩,很舒服!强烈推荐,虽然我不是很想推,怕后面排队,到点了也不急着赶人,确实很舒服!手法口法都很厉害!!!

❤1

17 Nov 2026, 10:43 UTC287 viewsread 17 November 2026

【时间】:2026-11-17 【老师】:晶晶 【留名】:匿名 【评价】:👍 好评 【人照】:8.5 【颜值】:8.5 【身材】:9 【服务】:9 【态度】:10 【环境】:8.5 【综合】:8.92 【过程】:昨天没有约上,今天终于是约上了,早早就在楼下等待,位置离地铁站有些距离,到了地点后遥控上楼,老师热情迎接,老师小小一个,我一手拉过来抱了起来,进行长达2分钟的热吻后,交了水费开始沐浴更衣,不得不说这身材可以瘦底大熊,三点微粉,到了床上老师遍开始服务起来,口活可以,无齿感,在嫩妹系列是上游水平了,老师女上起手,进入的瞬间包裹感十足,很是湿嫩,愉悦的感觉涌上脑袋,这熟悉的感觉我就知道我该交代了出了名的123撑不过3秒。总结:紧 嫩 粉 服务到位,值得推荐。

17 Nov 2026, 10:10 UTC143 viewsread 17 November 2026

【时间】:2026-11-16 【老师】:艺艺 【留名】:Rr 【评价】:👍 好评 【人照】:8.5 【颜值】:8 【身材】:8 【服务】:8.5 【态度】:9 【环境】:8 【综合】:8.33 【过程】:到地点根据老师指引,进门后看到了老师,和照片8成像,嫩妹,付完水费后开始洗澡,洗完澡后擦干,老师有帮忙擦背啥的,擦干后上床,老师先来了一套二连,口得差不多开始上班,女上开场,老师挺卖力的,后面又换了其他姿势,老师一直很配合,总体体验不错,结束后和老师一起洗澡,心满意足完成本次服务.

17 Nov 2026, 09:42 UTC95 viewsread 17 November 2026
Photo

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

17 Nov 2026, 07:46 UTC460 viewsread 17 November 2026

【时间】:2026-11-16 【老师】:露露 【留名】:16号爱人 【评价】:👍 好评 【人照】:9 【颜值】:8 【身材】:9 【服务】:9 【态度】:9 【环境】:9 【综合】:8.83 【过程】:提前约好时间,准时到约定地点,房间干净整洁,整体环境让人很放松。随后就去洗澡。老师洗得很认真,注重卫生,从头到脚仔细清理,然后是浴室调情,穿着睡衣在浴室里口交很刺激时间还挺久的,洗完后还帮我擦干身体,动作细致,没有敷衍。躺上床后,露露老师开始正式服务。课表上的项目基本都会做,而且做得比较到位。老师很温柔,会主动kiss,正面漫游时手法熟练,不急不躁,慢慢把气氛烘起来。69的时候老师配合度很高,深喉几乎没有齿感,吞吐节奏控制得好,课表上的内容都有不偷工减料,正式开始后老师主动戴好安全套,先是女上老师臀部丰满,撞击时声音清脆,同时还会配合拍打,刺激感更强。然后换成了后入,然后看着镜子看她,双手可以自由抚摸她的胸部,触感柔软,最后换成…

17 Nov 2026, 07:42 UTC389 viewsread 17 November 2026

【时间】:2026-11-17 【老师】:露露 【留名】:卡 【评价】:👍 好评 【人照】:8.5 【颜值】:8 【身材】:9 【服务】:9.5 【态度】:9.5 【环境】:9 【综合】:8.92 【过程】:包两个小时。我去了家人们,确实如🐺友所说。进去整个就是一干净环境好吧,我还没反应过来露露老师就已经贴上来投怀送抱了,整个就是一反差感邻家女友,让你坐会,拖鞋也给你拿来换,衣服也帮你脱,相当热情,这样的服务很难在别处体验到了,洗完之后就让你挑选丝袜,直接上黑丝,一穿上黑丝老性感了,露露老师开始服务,从脸然后逐渐到脖子,耳朵,脸颊,然后又从另一边下去,直到小弟那,然后开始口,口的很舒服,没有齿感,也很软,偶尔还吸吸蛋蛋,后面受不了,就要求戴套,进去时候,就能感觉很紧,然后还有种湿润感,干起来水很多,都感觉到我身上了,换了几个姿势,还有语言刺激整个就是相当爽的,然后抱着快速冲击,冲击力十分钟,老师浪叫下,直接释放,休息会后,又来了…

17 Nov 2026, 07:37 UTC105 viewsread 17 November 2026

【时间】:2026-11-17 【老师】:菜菜 【留名】:匿名 【评价】:👍 好评 【人照】:9 【颜值】:8 【身材】:8 【服务】:8 【态度】:9 【环境】:8 【综合】:8.33 【过程】:人照一致基本,课表有的基本有 去到楼下 老师遥控上楼位置很好找,老师人很苗条,进到房间简单跟老师聊了一下,就去洗澡了 ,老师洗的很认真 事后还帮忙擦干 好评,洗完就去床上等着啦,摸了摸老师的咪咪 一只手差不多刚刚好 然后老师舔了一下咪咪舔 的很舒服,舔了会就带套开始,女上真的受不住 不愧是嫩妹,还是很紧的,姿势都没换就直接上高速 缴械投降了,最后说 人还是挺好看的就是 要是课表有其他服务就好啦 ,其他还是不错的.

17 Nov 2026, 07:34 UTC119 viewsread 17 November 2026

【时间】:2026-11-16 【老师】:可乐 【留名】:匿名 【评价】:👍 好评 【人照】:10 【颜值】:10 【身材】:10 【服务】:10 【态度】:10 【环境】:10 【综合】:10 【过程】:平时在群里聊天的时候,我经常能看见可乐姐姐出来聊天互动,也是比较少见老师来聊天,一来二去,自然而然就留意到她了。后来我特意去看了看频道,频道非常活跃,也翻了翻大家留下的评论,不得不说好评真的多,那时候还幻想着有机会的话一定见上一面。 也是苍天不负有心人,也许是我这个咸鱼感动了抽奖机器人,让我单抽中了可乐姐姐的半价,我自己属实也没想到,广告都没看哈哈。不少师兄问我是否前往,倒让我此行之心愈发坚定。因单休之故,约隔一周才来拜访。初次到访,一路难免紧张。 上楼直接推门进来,看到可乐姐姐坐在沙发上,可乐姐姐温婉热情,毫无生疏之感,温柔招呼我坐下休息,还给我拿了瓶水,让我本来紧张的心情慢慢放松下来。随后她轻轻抱住我,这突如其来的温柔和亲…

16 Nov 2026, 14:25 UTC205 viewsread 17 November 2026

【时间】:2026-11-15 【老师】:奈奈 【留名】:Thaleswar Sinha 【评价】:👍 好评 【人照】:8.5 【颜值】:8.5 【身材】:9 【服务】:9 【态度】:9.5 【环境】:8 【综合】:8.75 【过程】:颜值不错,精致好看,近看也很耐看,跟视频差样不大。皮肤滑嫩,黄白皮,胸可爱酥胸,很粉嫩,妹妹水也足,长腿,屁股很翘,很肉,后入很带感。

16 Nov 2026, 14:25 UTC193 viewsread 17 November 2026

【时间】:2026-11-16 【老师】:小丸子 【留名】:慢慢(梦想是不123)上岸版 【评价】:👌 中评 【人照】:1 【颜值】:8 【身材】:7 【服务】:8 【态度】:8 【环境】:8 【综合】:6.67 【过程】:问了一嘴老师开课的地方,离我稍微近一点,于是选择兑换出击。 这附近开课的老师应该还蛮少的,见到人之后发现不是嫩妹,而是御姐,本来是一直给自己做心里建设要是不合适就转身,但是老师颜值身材还是可以的,半价吃一吃也不是不行。课表服务都是有的,胸b左右,胸推没有那种大胸老师来的那么软弹,但是有不一样的体验,老师服务态度很不错,胸推结束后开始进攻两点,老师的漫游还是很爽,最后还是袭向二弟,先是舔🥚然后含根,太敏感后面选择戴套进入,让老师躺在床上我站在地上开始进攻,两分钟123出水搞定走人。 后面跟老师核对才发现原来老师是中介代聊,我说怎么货不对板,并非嫩妹实则御姐,冲着嫩妹来的不要考虑了,也可能是开盲盒,不过胜在质…

16 Nov 2026, 14:00 UTC85 viewsread 17 November 2026
Photo

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

Showing the 12 most recent of 638 posts we hold for @GZBG8866. 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 45 posts on @GZBG8866 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
17 November 2026
Median time before seen missing
28 hours
Seen missing in the last 30 days
19

Forward network

Republished by

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

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

Named by 25 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“(广州探花)娱乐反馈报告” (@GZBG8866), 23,889 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/GZBG8866.

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.