Telegram RegisterThe public register of Telegram
Telegram profile photo for 广州佛山永乐公开榜

Channel

广州佛山永乐公开榜

@guangfoyongle

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

52,373subscribers

+4,709 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-1002168982538
TypeChannel
Username@guangfoyongle
Description广佛出击必备榜 本群🈲一切中介、骗子、代聊、驾照 踩雷有奖 广佛永乐聊天总群👇 @guangfoyongle2020 老师上榜请联系唯一客服机器人 @ShangbangjiqirenBot
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/guangfoyongle

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 3 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@guangfoyongle/26564 · this entry7 Aug 2026, 11:02 UTC@GZSJB/164217 Aug 2026, 11:46 UTC0.9944 minutes
@guangfoyongle/29232 · this entry11 Sept 2026, 11:50 UTC@GZSJB/1693211 Sept 2026, 11:52 UTC0.992 minutes
@GZSJB/167222 Sept 2026, 11:57 UTC@guangfoyongle/30727 · this entry30 Sept 2026, 11:16 UTC0.9928 days
@guangfoyongle/29226 · this entry11 Sept 2026, 10:41 UTC@GZSJB/1720719 Sept 2026, 09:27 UTC0.968 days
@guangfoyongle/27145 · this entry14 Aug 2026, 12:11 UTC@GZSJB/1654814 Aug 2026, 13:34 UTC0.9283 minutes
@guangfoyongle/26564 · this entry7 Aug 2026, 11:02 UTC@Gzffcl/64757 Aug 2026, 11:15 UTC0.9913 minutes
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
@GZSJB5 (5/5 hand-verifiable sample passed)0.9724 minutesthis entry (4–1)
@Gzffcl5 (5/5 hand-verifiable sample passed)0.9622 minutes@Gzffcl (3–2)
@heichefangbao7 (7/7 hand-verifiable sample passed)1.0072 seconds@heichefangbao (7–0)

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. 6 of the 6 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 540 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @heichefangbao. 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 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. 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

46,86452,37349,618.56 August 202615 November 2026
67 measurements spanning 101 days, net +4,709. 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 46,038–53,199 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
15 Nov 2026, 21:5652,373+188
12 Nov 2026, 10:5852,185+102
10 Nov 2026, 07:1752,083+39
8 Nov 2026, 22:0652,044+47
7 Nov 2026, 12:4751,997+11
6 Nov 2026, 14:2551,986+16
5 Nov 2026, 17:4951,970+63
4 Nov 2026, 16:5951,907+76
3 Nov 2026, 14:5651,831+49
2 Nov 2026, 12:3751,782+128
1 Nov 2026, 13:4551,654+38
31 Oct 2026, 17:1051,616+125
30 Oct 2026, 13:5051,491+74
29 Oct 2026, 11:0651,417+90
28 Oct 2026, 08:0051,327+64
27 Oct 2026, 10:4551,263+68
26 Oct 2026, 11:1151,195+106
25 Oct 2026, 13:2751,089+149
24 Oct 2026, 14:2150,940+82
23 Oct 2026, 11:2650,858first reading

Engagement

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

ERR · 30 days
1.24%
avg views ÷ 52,373 subscribers
Avg views / post
652
204 posts measured
Reaction rate
0.128%
reactions ÷ views · ER floor
Posts in window
204
of 639 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 68 of 204 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 held639 (6 August 2026 – 17 November 2026)
Views total132,921
Reactions total66
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 07:57 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
≈2,000
Videos
≈228
Links
≈393

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
46m 12s
Average length
11s

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

312 reactions across 190 posts, in 10 distinct kinds. The most used accounts for 81.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤25581.7%
👍268.33%
👏154.81%
🔥41.28%
🥰41.28%
👎20.641%
💯20.641%
😁20.641%
🤩10.321%
🤮10.321%

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

Measured over the 639 most recent posts we hold, published 6 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: 3 of 204 posts held from the last 30 days (1.47%) 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, 06:30 UTC212 viewsread 17 November 2026
Photo

#正宗泰国抓龙筋🔥🔥 💯高端公寓楼、环境优雅、 🌹本人两年金泰会所工作经验、三年正规抓龙筋手法、前列腺高潮、淋巴排毒、经络疏通、龟头脱敏、主打男性私密保养、SPA调理男性精气神、增强弟弟战斗力丶等… 🌹本人、小鸟依人、温柔风格胸大服务到位、身材高挑、 关注频道可享首单半价活动 #日式、#抓龙筋、#SPA、#前列腺保养 #前列腺高潮、#私人订制变装、等等 🈲95-98 ✈️宝宝号:@Af0898 ✈️双向奔赴:@Tyy6686_bot 与你号:gf0998 频道:https://t.me/afg8699 VX:只发位置:asb886699-69 企鹅🐧:2304814280 报告1 👍 点击返回导航 👍 点击返回抓龙筋推荐榜

17 Nov 2026, 06:09 UTC231 viewsread 17 November 2026
Photo

☝️艺名:#姜夏 📍地址:#禅城 💲价格:#600P #1200PP 👍特色:#嫩妹 #舌吻 #可上门 🚀私聊:@xyzhql ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击跳转禅城二区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

17 Nov 2026, 04:13 UTC400 viewsread 17 November 2026
Photo

☝️艺名:#琪琪 📍地址:#禅城 💲价格:#600P #1200PP 👍特色:#御姐 #舌吻 #可上门 👍特色:#毒龙 #口爆 🚀私聊:@aqiqi168 ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击跳转禅城二区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

16 Nov 2026, 14:11 UTC500 viewsread 16 November 2026
Photo

☝️艺名:#月月 📍地址:#禅城 💲价格:#700P #1300PP 👍特色:#嫩妹 #舌吻 #可上门 🚀私聊:@yueyue1208 ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击返回禅城区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

16 Nov 2026, 11:09 UTC726 views2 reactionsread 16 November 2026
Photo

🔈禅城花岸里会所🔈 ✅#佛山 #禅城 #张槎 #会所 #94 ✅原价539 😃预约价: 469 🟡时间.80分钟🟡 ✅多人组队优惠多多🤗🤗 ✅👅本店只做精品:94 《👋手出,🦶足交,🐻胸推,🦵腿夹》不限次数,根据个人爱好🉑各种花式出👈 ✅服务内容: 真空+黑丝,全裸(梅川内裤 ),真69互舔🫦魅舞表演,主打贴身,好玩,刺激。服务内容:主打情趣互动😍,激情艳舞,跪式调情,推漫游全身,👅舌尖调情,😍屁股退,真空推后背,舌尖环游全身,手✋,足🦶,腿🦵,胸🐻配合各种姿,网式情趣69式互舔,69式丝袜,姿势丰富,站坐跪,床上床下,🫦可舔逼摸逼玩美女下路,(舔蛋👅,含蛋👅,舔龙根👅5分钟以上,各种调情服务技师开放拉到极致(隐私部位可摸可亲🫦)可配合客人手腿。 主打全程贴身服务,好玩,刺激,过瘾让你回味无穷,操作细节、情绪价值拉满 感受94顶级天板。 🫠👌🫠 🫠频道:https://t.me/haifoshan069…

❤2

16 Nov 2026, 09:48 UTC666 viewsread 16 November 2026
Photo

☝️艺名:#依燚 📍地址:#顺德 💲价格:#800P #1500PP 👍特色:#舌吻 #可上门 🚀私聊:@nn1181888 ⌨️验证方式:#视频验证 #非中介 报告1 报告2 👍 点击返回顺德区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

16 Nov 2026, 06:56 UTC169 viewsread 16 November 2026
Photo

☝️艺名:#西西 📍地址:#海珠 💲价格:#400P #800PP 👍特色:#少妇 #舌吻 #大胸 👍特色:#毒龙 🚀私聊:@gzxiaoxiaini ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击返回海珠区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

16 Nov 2026, 06:37 UTC205 viewsread 16 November 2026
Photo

☝️艺名:#可可 📍地址:#白云 💲价格:#500P #900PP 👍特色:#御姐 #毒龙 #口爆 🚀私聊:@ck1230 ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击返回白云区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

15 Nov 2026, 10:27 UTC≈1,360 views1 reactionsread 16 November 2026
Photo

☝️艺名:#尤尼娅 📍地址:#天河 💲价格:#500P #1000PP 👍特色:#御姐 #舌吻 #毒龙 🚀私聊:@yly522 ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击跳转天河二区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200

❤1

15 Nov 2026, 09:19 UTC≈1,180 views9 reactionsread 16 November 2026
Photo

---#广州 #放松 #私密会所--- 特色:#广州高质量Spa课堂 #口爆 #真毒龙 #冰火两重天 #反向69 #深喉 #情趣丁字裤 #口出 #全裸 #舒适环境 #服务理念 店名:广州天河95高质量课堂 地址: #天河 #车陂南 #东圃 客服: @Xiexie580 双向: @Xiexiansheng2bot 频道:https://t.me/Gzspaaa 备注:以服务为理念,立志提供私密化舒适空间,给无趣的生活,多增加一个选择,让享受成为一次日常🤝🤝🤝 营业时间:中午12-3点 好评: @gpsaaa 项目1️⃣:94 600 项目2️⃣:95 800 👍 点击返回导航 👍 点击返回天河会所榜

❤8💯1

15 Nov 2026, 07:08 UTC883 views0 reactionsread 15 November 2026
Photo

☝️艺名:#关之琳 📍地址:#南海 #只上门 💲价格:#1200P #2000PP 👍特色:#御姐 #大胸 #只上门 🚀私聊:@guanzhilin27 ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击返回南海区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

15 Nov 2026, 06:58 UTC928 views3 reactionsread 15 November 2026
Photo

☝️艺名:#绮绮 📍地址:#白云 💲价格:#500P #1000PP 👍特色:#嫩妹 #舌吻 #可上门 🚀私聊:@qiqi00808 ⌨️验证方式:#视频验证 #非中介 首份报告提交者获得双倍积分奖励 👍 点击返回白云区 👍 点击返回导航 如果中介代聊、货不对版、照片本人差距大排雷奖励RMB200元

❤3

Showing the 12 most recent of 639 posts we hold for @guangfoyongle. 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 3 posts on @guangfoyongle 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
19 August 2026
Most recent seen missing
24 September 2026
Median time before seen missing
13 hours
Seen missing in the last 30 days
0

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

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

“广州佛山永乐公开榜” (@guangfoyongle), 52,373 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/guangfoyongle.

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.