Telegram RegisterThe public register of Telegram
Telegram profile photo for 广州天河海悦会所频道

Channel

广州天河海悦会所频道

@qwe656729

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

422subscribers

-9 since we began measuring on 27 September 2026

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

Register entry

Telegram ID-1001881048953
TypeChannel
Username@qwe656729
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live13 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/qwe656729

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 13 October 2026 and assigned it the closest of 31 fixed categories, at 74% 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 (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qwr8851829999/5025 May 2026, 12:02 UTC@qwe656729/462 · this entry25 May 2026, 12:06 UTC1.004 minutes
@qwr8851829999/5125 May 2026, 15:40 UTC@qwe656729/463 · this entry25 May 2026, 15:40 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
@qwr88518299996 (6/6 hand-verifiable sample passed)1.00under a minute@qwr8851829999 (5–1)

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 2 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 6 comparable posts for this entry, running 24 May 2026 to 28 May 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 @qwr8851829999. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

422431426.527 September 2026 — 431 subscribers27 September 2026 — 431 subscribers13 October 2026 — 425 subscribers20 October 2026 — 423 subscribers28 October 2026 — 425 subscribers4 November 2026 — 424 subscribers13 November 2026 — 422 subscribers27 September 202613 November 2026
7 measurements spanning 47 days, net -9. 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 421–432 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 09:07422-2
4 Nov 2026, 20:11424-1
28 Oct 2026, 10:46425+2
20 Oct 2026, 21:21423-2
13 Oct 2026, 19:27425-6
27 Sept 2026, 07:22431no change
27 Sept 2026, 06:48431first reading

Engagement

17 posts held, back to 24 May 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 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 17 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
33s
Average length
17s

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

13 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤13100.0%

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

Measured over the 17 most recent posts we hold, published 24 May 2026 to 22 July 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

22 Jul 2026, 10:08 UTC≈2,150 views1 reactionsread 27 September 2026
Photo

💎点评论看报告💎 部长推荐,好好看(极品甜妹)cd667

❤1

19 Jul 2026, 14:56 UTC≈2,130 views1 reactionsread 27 September 2026
Photo

会所房间环境,独立卫浴

❤1

26 Jun 2026, 07:18 UTC≈2,300 views4 reactionsread 27 September 2026
Photo

💎点评论看报告💎 1234 (cd667)部长推荐,好好看 👍👍👍👍👍👍👍👍

❤4

21 Jun 2026, 08:24 UTC≈2,470 viewsread 27 September 2026
Video

💎点评论看报告💎 2222(cd667) 03年嫩妹 童颜巨乳,神似水卜樱😍😍😍😍😍😍😍 🐻 D+

21 Jun 2026, 07:26 UTC≈2,540 views3 reactionsread 27 September 2026
Video

💎点评论看报告💎 868(cd668) 07年嫩妹😍😍😍😍

❤3

3 Jun 2026, 07:23 UTC≈3,500 viewsread 27 September 2026
Photo

04年御姐,情趣价值高 cd(666-667)

28 May 2026, 17:34 UTC≈3,660 viewsread 27 September 2026
Photo

💎点评论看报告💎 7777 (cd667+ 可送💋💋) 👍👍👍👍👍👍👍👍

28 May 2026, 17:11 UTC≈3,330 views1 reactionsread 27 September 2026
Photo

💎点评论看报告💎 9999(cd667)❤️❤️❤️❤️

❤1

28 May 2026, 11:44 UTC≈2,560 viewsread 27 September 2026
Photo

【会所名称】:海悦 【会所位置】:天河棠东 【联系方式】:@qwe88518299 【会所价格】: 639-70(报告-70) 【技师号码】: 7777 【验证留名】: 匿名 【验证时间】:5.28 【颜值评价】: 八分 【身材评价】:八分 【推荐理由】:今天看到群里,一直挂着7777然后就联系部长出发了 原本想约868和9999的,但是都来姨妈了。 一进房间,看到人还挺好看的,一进去看到人 尊重且立了起来,然后我就上去起手 身材不错,嘻嘻嘻,后面我就躺着让她帮我做服务了,因为我不喜欢做背面,然后正面做了很久,哆啦a梦没说错,舔蛋蛋和棍棍舔了很久,👅很舒服,后面有送口啊,,还行吧,但是我没啥感觉,不是我get的点,后面就边蛇边出水(蛇饱),适合躺尸党,总体中等偏上吧,还是值得推荐的,后面就一边聊天一边按摩,妹妹还是挺有趣的,哈哈哈哈,总体来说cd667+💋💋💋💋

27 May 2026, 22:46 UTC≈1,730 views1 reactionsread 27 September 2026
Photo

今天7777上班💋💋💋💋💋

❤1

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

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

“广州天河海悦会所频道” (@qwe656729), 422 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/qwe656729.

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.