Telegram RegisterThe public register of Telegram
Telegram profile photo for 🏪东莞同城报告发布🏪(免费上榜)

Channel

🏪东莞同城报告发布🏪(免费上榜)

@dghfbyujiu

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

11subscribers

+0 since we began measuring on 8 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002185563223
TypeChannel
Username@dghfbyujiu
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live14 November 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/dghfbyujiu

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 17 October 2026 and assigned it the closest of 31 fixed categories, at 73% 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. 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
@wefgeweg/7631 Oct 2025, 14:24 UTC@dghfbyujiu/97 · this entry31 Oct 2025, 14:24 UTC1.00under a minute
@dghfbyujiu/98 · this entry31 Oct 2025, 14:24 UTC@wefgeweg/7731 Oct 2025, 14:24 UTC1.00under a minute
@wefgeweg/7831 Oct 2025, 14:24 UTC@dghfbyujiu/99 · this entry31 Oct 2025, 14:24 UTC1.00under a minute
@dghfbyujiu/100 · this entry31 Oct 2025, 14:25 UTC@wefgeweg/7931 Oct 2025, 14:25 UTC1.00under a minute
@wefgeweg/8031 Oct 2025, 14:25 UTC@dghfbyujiu/101 · this entry31 Oct 2025, 14:25 UTC1.00under a minute
@wefgeweg/8131 Oct 2025, 14:26 UTC@dghfbyujiu/102 · this entry31 Oct 2025, 14:26 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
@wefgeweg11 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (11–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 31 October 2025 to 31 October 2025. 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 @wefgeweg. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 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

101110.58 September 2026 — 11 subscribers14 September 2026 — 11 subscribers13 October 2026 — 10 subscribers14 November 2026 — 11 subscribers8 September 202614 November 2026
4 measurements spanning 66 days. 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 10–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 08:1711+1
13 Oct 2026, 15:5610-1
14 Sept 2026, 08:2311no change
8 Sept 2026, 23:1711first reading

Engagement

20 posts held, back to 31 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 October 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Oct 2025, 14:31 UTC16 viewsread 14 September 2026

【联系方式】 @xiaxia0930 【验证留名】Yu 【验证日期】10.25 【上课价位】1600PP 【人照几分】10 【服务过程】无意中刷到妍妍老师。从南城飞奔长安。真人比照片好看,皮肤雪白,粉胸很大挺,手感不错,差一点口出,确实厉害,值得一赞。服务很配合,任何姿势配合,妹子很给力,能服务的都会尽量满足,这一点一般ls做不到。下面粉嫩,干净很紧,毛毛不多,x起来很爽,水嫩嫩,也很享受,回味无穷,颜值+服务优秀,情绪价值拉满 真奈斯,非常棒的一次出击。

31 Oct 2025, 14:31 UTC16 viewsread 14 September 2026

【联系方式】@moli1927 【验证留名】李哥 【上课价位】668 【人照几分】10分 【服务过程】见到老师比照片还漂亮,很温柔,声音好听,身材很火辣,最主要口技了得,体验很好,胸也很大,会继续反食的 很满意

31 Oct 2025, 14:31 UTC16 viewsread 14 September 2026

【联系方式】@moli1927 【验证留名】李哥 【上课价位】668 【人照几分】10分 【服务过程】见到老师比照片还漂亮,很温柔,声音好听,身材很火辣,最主要口技了得,体验很好,胸也很大,会继续反食的 很满意

31 Oct 2025, 14:31 UTC13 viewsread 14 September 2026

【联系方式】@xiaoli99978 【验证留名】12 【上课价位】600p 【人照几分】9 【服务过程】9 人美,人照一致。环境舒服,妹妹服务得很棒,叫的很销魂!!

31 Oct 2025, 14:30 UTC9 viewsread 14 September 2026

【联系方式】 @xiaxia0930 【验证留名】li 【上课价位】1600PP 【人照几分】10 【服务过程】闲着没事,突然想找个高质量的 ls ,想起之前留意到的妍妍老师,心动不如行动,一问时间合适,还是头课,马上出发,一路跟着 Is 遥控到课室,初见果然不得了,人照合一,是我喜欢的类型,颜值满分,身材满分,皮肤又白又嫩,难得的老师还很热情,见面一个拥抱+香吻,遂交水费,脱衣期间2得太激动没忍住,在客厅和 ls 来了第一回合,123交出亿万子孙,然后 ls 在浴室洗了个鸳鸯浴,浴室出来 ls 还细致得帮忙擦干身体,太有服务意识了,加分,最后在房间和 ls 开始第二回合,乖乖投降123交出亿万子孙,第二次洗澡后 ls 依旧细致得帮忙擦干身体,服务有的都有。意识真的太到位了,服务内容69 舌吻 口爆。毒龙简直顶。 总结:不愧号称颜值天花板,风骚性感,服务期间全程不尴尬,今天确实?爽了,真是一分钱一分货。物有所值。

31 Oct 2025, 14:30 UTC8 viewsread 14 September 2026

【联系方式】@xueerz2005 【验证留名】Mcllroy 【上课价位】p 【人照几分】9 【服务过程】有段时间没见雪儿了,遥控上楼开门就给妹妹按在床上摩擦,共浴有水中萧,还有各种战衣可以选择,服务更是一级棒!妹妹牙齿做了矫正比之前好看多了,如此嫩妹值得一试!

31 Oct 2025, 14:27 UTC8 viewsread 14 September 2026

【联系方式】@yumyun8568 【验证留名】朋友仔 【上课价位】600p 【人照几分】9 【服务过程】看到老师好评挺多,果断约老师,本来今天塞车心情不太好,到楼下遥控上楼,看到老师那一刻心情就好起来了,老师长得好看,年纪25,简单聊了两句之后就一起去洗澡了,洗好了就去床上翻云覆雨,老师给人一种女友的感觉,🐍到饱,老师💧也是很多,把床都弄湿了,换了几个姿势,经过不懈的努力的终于出水,抱着老师不舍得拔出来,老师也抱着我,最终还是含泪一起去洗澡,下次有时间会返

31 Oct 2025, 14:27 UTC8 viewsread 14 September 2026

【联系方式】@xueerz2005 【验证留名】lg 【上课价位】600p 【人照几分】10 【服务过程】四返雪儿,这次雪儿带了隐形牙套,说话结结巴巴的,很可爱,而且临近姨妈期身体异常敏感,是限定版雪儿,我玩得很开心,很棒的一次体验。

31 Oct 2025, 14:27 UTC6 viewsread 14 September 2026

【联系方式】@xiaotuantuan2007 【验证留名】白云 【上课价位】1000P 【人照几分】10+ 【服务过程】翻衣柜的时候发现了一缕发丝,闻了下瞬间上头,是小团团的香甜味,好久不见还是那般忘不掉,便再次约了团团。开门瞬间,扑面而来的小团团香香甜甜软软糯糯的初恋的味道,进门狠狠抱了一下以解我的思念之苦。太久没见,迫不及待脱衣服洗澡上楼,躺床上看着团团娇羞地趴到我身前,仅仅张口看着我那一瞬间我就忍不住了,直接扑倒,带上雨伞,团团小穴太紧太嫩了,我只能慢慢插进去,积攒多日的思念化成精水喷涌而出,最后离场还被夹得紧紧的,从腿发软到上半身,最后趴在团团身上歇会感受余温,顺便吸食那让人上头的体香,团团真香,下次还来。

31 Oct 2025, 14:26 UTC5 viewsread 14 September 2026

【联系方式】@xueerz2005 【验证留名】磊帝 【上课价位】6 【人照几分】9 【服务过程】很久没见,老师还是那么主动,进门就贴着,服务很好很配合,还会返

31 Oct 2025, 14:26 UTC5 viewsread 14 September 2026

【联系方式】@GuoGuoii1 【验证留名】隔壁老王 【验证日期】10.26 【上课价位】6 【人照几分】 【服务过程】 看到本人长相还行。身材均匀,皮肤算白的🐻算平的,服务还行,口的很舒服,就是异味有点,估计没有洗干净,平时没有注意个人卫生。支持匿名报告,匿名需要花费200积分隐藏ID。(积分多此举是为了避免恶意刷好评或者差评,所以大家尽量还是客观评价吧)OK

31 Oct 2025, 14:25 UTC5 viewsread 14 September 2026

【联系方式 @mumu5500 【验证留名】隔壁老王 【上课价位】6 【人照几分】 【服务过程】 看到本人长相好看。身材刚好,皮肤正常,🐻好看,服务还行,口的很舒服,还是可以返的。支持匿名报告,匿名需要花费200积分隐藏ID。(积分多此举是为了避免恶意刷好评或者差评,所以大家尽量还是客观评价吧)OK

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

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

“🏪东莞同城报告发布🏪(免费上榜)” (@dghfbyujiu), 11 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/dghfbyujiu.

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.