Telegram RegisterThe public register of Telegram
Telegram profile photo for 上海【沪伴茶语】精选榜

Channel

上海【沪伴茶语】精选榜

@hbcy_sh

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

18,327subscribers

-10,081 since we began measuring on 4 October 2026

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

Register entry

Telegram ID-1002000638616
TypeChannel
Username@hbcy_sh
CreatedBetween 1 November 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 October 2026
Last confirmed live18 November 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/hbcy_sh

Topic

Adult — 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 18 October 2026 and assigned it the closest of 31 fixed categories, at 92% 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
@hubanchaye/21472 Nov 2026, 07:37 UTC@hbcy_sh/3541 · this entry2 Nov 2026, 07:37 UTC1.00under a minute
@hubanchaye/21583 Nov 2026, 06:18 UTC@hbcy_sh/3563 · this entry3 Nov 2026, 06:18 UTC1.00under a minute
@hbcy_sh/3565 · this entry3 Nov 2026, 06:59 UTC@hubanchaye/21603 Nov 2026, 06:59 UTC1.00under a minute
@hbcy_sh/3567 · this entry3 Nov 2026, 09:49 UTC@hubanchaye/21633 Nov 2026, 09:49 UTC1.00under a minute
@hubanchaye/21663 Nov 2026, 11:40 UTC@hbcy_sh/3569 · this entry3 Nov 2026, 11: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
@hubanchaye5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (5–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 116 comparable posts for this entry, running 1 October 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_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.

Growth

18,32728,47723,4024 October 2026 — 28,408 subscribers4 October 2026 — 28,408 subscribers8 October 2026 — 28,477 subscribers13 October 2026 — 28,365 subscribers14 October 2026 — 28,309 subscribers15 October 2026 — 28,310 subscribers16 October 2026 — 28,308 subscribers17 October 2026 — 27,847 subscribers18 October 2026 — 27,700 subscribers19 October 2026 — 27,637 subscribers20 October 2026 — 27,432 subscribers21 October 2026 — 27,262 subscribers22 October 2026 — 26,863 subscribers23 October 2026 — 26,615 subscribers24 October 2026 — 26,192 subscribers25 October 2026 — 25,904 subscribers26 October 2026 — 25,450 subscribers27 October 2026 — 25,153 subscribers29 October 2026 — 24,605 subscribers30 October 2026 — 24,288 subscribers31 October 2026 — 23,888 subscribers31 October 2026 — 23,716 subscribers1 November 2026 — 23,363 subscribers2 November 2026 — 23,356 subscribers3 November 2026 — 23,338 subscribers4 November 2026 — 23,122 subscribers5 November 2026 — 22,824 subscribers6 November 2026 — 22,592 subscribers7 November 2026 — 22,152 subscribers8 November 2026 — 21,757 subscribers10 November 2026 — 21,187 subscribers12 November 2026 — 20,475 subscribers15 November 2026 — 19,264 subscribers18 November 2026 — 18,327 subscribers4 October 202618 November 2026
34 measurements spanning 45 days, net -10,081. 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,805–30,000 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Nov 2026, 19:0118,327-937
15 Nov 2026, 17:1819,264-1,211
12 Nov 2026, 10:5820,475-712
10 Nov 2026, 07:0721,187-570
8 Nov 2026, 22:0721,757-395
7 Nov 2026, 17:1522,152-440
6 Nov 2026, 19:5022,592-232
5 Nov 2026, 19:3722,824-298
4 Nov 2026, 20:5423,122-216
3 Nov 2026, 21:4723,338-18
2 Nov 2026, 19:5123,356-7
1 Nov 2026, 22:2023,363-353
31 Oct 2026, 22:3523,716-172
31 Oct 2026, 01:1723,888-400
30 Oct 2026, 04:1924,288-317
29 Oct 2026, 01:4024,605-548
27 Oct 2026, 23:2825,153-297
26 Oct 2026, 20:2725,450-454
25 Oct 2026, 18:0725,904-288
24 Oct 2026, 14:5026,192first reading

Engagement

133 posts held, back to 1 October 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 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.01%
avg views ÷ 18,327 subscribers
Avg views / post
185
83 posts measured
Reaction rate
0.501%
reactions ÷ views · ER floor
Posts in window
83
of 133 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 14 of 83 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 18 November 2026
Posts held133 (1 October 2026 – 18 November 2026)
Views total15,319
Reactions total12
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 16:38 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

Video runtime
10m 10s
Average length
8s

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

14 reactions across 12 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1285.7%
👍214.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 17 of the 133 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 133 most recent posts we hold, published 1 October 2026 to 18 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: 4 of 83 posts held from the last 30 days (4.82%) 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).

18 Nov 2026, 13:34 UTC98 viewsread 18 November 2026
Photo

🎰 闵行悦悦老师的抽奖活动 📮 抽奖条件: 🎫 加入-悦悦的小屋 🎫 加入-上海【沪伴茶语】交流群 🎫 加入-上海【沪伴茶语】精选榜 🎫 加入-茶语作业反馈频道 🎫 加入-上海【沪伴茶语】备用群 🎁 奖品内容: p pp 半价优惠券 × 1 💡 活动说明: 抽奖说明: 1.中奖三天内私信老师(有特殊情况提前说明) 2.出击后24小时提交出击报告 3.没有按时出击,中奖不去,出击完不写报告 以后抽奖不允许参加 中奖联系老师:(附带中奖截图): @yueyue524 活动最终解释权归沪伴茶语管理团队所有。 刷屏 灌水 纯表情 复制粘贴 无意义对话、撤回内容等,一律视为无效发言,不计入统计 📅 开奖日期:(UTC+8) 2026年11月20日 21时30分00秒

18 Nov 2026, 13:00 UTC98 viewsread 18 November 2026
Photo

💐💐💐开奖了💐💐💐 浦东时一老师的抽奖活动 开奖了! 本期总参与人数: 58 1- kk bobo 获得:半价p优惠券 谨祝中奖用户大吉大利万事顺意

18 Nov 2026, 12:30 UTC98 views1 reactionsread 18 November 2026
Photo

💐💐💐开奖了💐💐💐 闵行苗苗老师的抽奖活动 开奖了! 本期总参与人数: 27 1- Eric 获得:半价p优惠券 2- Vicky 获得:pp200优惠券 3- BTC 获得:pp200优惠券 4- yoi yoi 获得:pp200优惠券 5- slcz 获得:pp200优惠券 6- big zyko 获得:pp200优惠券 谨祝中奖用户大吉大利万事顺意

❤1

18 Nov 2026, 12:19 UTC108 views1 reactionsread 18 November 2026
Photo

🔥艺名:#玲子 #松江 💰车费:#900p #1400pp 😓:160cm 40kg B胸 🍃标签: #舌吻 #六九 #鸳鸯浴 📫联系方式: @shlingzi1 🤖双向联系: @lelelee666_bot 🗒️ ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分) 工兵福利 半价500p 共 2 名,还剩 1名,积分满300积分,可凭积分截图加工兵模板找 @hubanchayu8 群主领取,出击完24小时内提交出击报告,不提供报告的ly将失去以后出击工兵的权利。

❤1

18 Nov 2026, 07:52 UTC138 viewsread 18 November 2026
Photo

🎰 浦东艾薇儿老师的抽奖活动 📮 抽奖条件: 🎫 加入-艾薇儿-定金预定 🎫 加入-上海【沪伴茶语】交流群 🎫 加入-上海【沪伴茶语】精选榜 🎫 加入-茶语作业反馈频道 🎫 加入-上海【沪伴茶语】备用群 🎁 奖品内容: 300通用优惠券 × 3 💡 活动说明: 抽奖说明: 1.中奖三天内私信老师(有特殊情况提前说明) 2.出击后24小时提交出击报告 3.没有按时出击,中奖不去,出击完不写报告 以后抽奖不允许参加 中奖联系老师:(附带中奖截图): @aawr66666 活动最终解释权归沪伴茶语管理团队所有。 刷屏 灌水 纯表情 复制粘贴 无意义对话、撤回内容等,一律视为无效发言,不计入统计 📅 开奖日期:(UTC+8) 2026年11月20日 20时00分00秒

16 Nov 2026, 06:48 UTC306 viewsread 18 November 2026
Photo

🔥艺名:#时一 #浦东 💰车费:#1200p #1900pp 😓:151cm 39kg B胸 🍃标签: #舌吻 #三点口 #鸳鸯浴 #深喉 #口爆 📫联系方式: @ShiYi912399 🤖双向联系:@ShiYi6653Bot 🗒️ ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分)

16 Nov 2026, 05:15 UTC289 viewsread 18 November 2026
Photo

🔥艺名:#小琪 #浦东 💰车费:#1000p #1700pp 😓:166cm 45kg B胸 🍃标签: #蛇吻 #六九 #陪浴 #调情 #制服 #口活 #丝袜 📫联系方式:@xiao00qi 🤖双向联系: @klxiaoqi_bot 🗒️ 【出击报告001】 【出击报告002】 【出击报告003】 ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分) (工兵福利)半价500p 共2名,还剩1名,积分满300积分,可凭积分截图加工兵模板找 @hubanchayu8 群主领取,出击完24小时内提交出击报告,不提供报告的ly将失去以后出击工兵的权利

16 Nov 2026, 05:09 UTC483 viewsread 18 November 2026
Photo

🔥艺名: #月月 #长宁 💰车费: #700p #1200pp 😓:162cm 47kg 胸B 🍃标签: #陪浴 #六九 #无套口 #胸推 #臀腿 #缩阴 #指滑 📫联系方式: @yueyue0022 🤖双向联系: @yueyue02bot 🗒️【出击报告001】 【出击报告002】 【出击报告003】 【出击报告004】 ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分) (工兵福利)半价400p 600pp 共2名,还剩0名,积分满300积分,可凭积分截图加工兵模板找 @hubanchayu8 群主领取,出击完24小时内提交出击报告,不提供报告的ly将失去以后出击工兵的权利

15 Nov 2026, 14:20 UTC239 viewsread 18 November 2026
Photo

🔥艺名: #钱多多 #浦东 💰车费: #1000p #1900pp 😓:158cm 45kg C胸 🍃标签: #无T口 #蛇吻 #六九 #鸳鸯浴 #制服 📫联系方式:@X9988778 🤖双向联系: @X9988778bot 🗒️ ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分) (工兵福利)半价500 共2名,还剩2名,积分满300积分,可凭积分截图加工兵模板找 @hubanchayu8 群主领取,出击完24小时内提交出击报告,不提供报告的ly将失去以后出击工兵的权利

15 Nov 2026, 08:48 UTC155 viewsread 16 November 2026
Photo

🔥艺名:#诗悦 #闵行 💰车费:#900p #1600pp 😓:166cm 49kg C胸 🍃标签: #口活 #六九 #舌吻 #三点粉 #刚下海 📫联系方式: @sy9895 🤖双向联系: 🗒️ ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分) (工兵福利)半价p 共1名,还剩1名,积分满300积分,可凭积分截图加工兵模板找 @hubanchayu8 群主领取,出击完24小时内提交出击报告,不提供报告的ly将失去以后出击工兵的权利

14 Nov 2026, 14:58 UTC420 viewsread 16 November 2026
Photo

🔥艺名:#喵喵 #浦东 💰车费:#1100p #1600pp 😓:168cm 45kg D胸 🍃标签: #陪浴 #舌吻 #六九 #裸吹 #深喉 #水多 #裸吹 #胸射 📫联系方式: @mengqi200719 🤖双向联系: @yibaojiqiren9487bot 🗒️【出击报告001】 【出击报告002】 ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分) (工兵福利)半价p 共2名,还剩1名,积分满300积分,可凭积分截图加工兵模板找 @hubanchayu8 群主领取,出击完24小时内提交出击报告,不提供报告的ly将失去以后出击工兵的权利

14 Nov 2026, 05:54 UTC306 viewsread 15 November 2026
Photo

🔥艺名:#小九 #浦东 💰车费:#800p #1600pp 😓:163cm 47kg C胸 🍃标签: #舌吻 #六九 #口爆 #野战 #车震 📫联系方式: @xiaojiu25_r 🤖双向联系: @xiaojiu25_rbot 🗒️ ✍️提交作业 📱聊天群 🪙茶语币 📱(备注沪伴茶语推荐➕100积分) (工兵福利)半价p 共1名,还剩1名,积分满300积分,可凭积分截图加工兵模板找 @hubanchayu8 群主领取,出击完24小时内提交出击报告,不提供报告的ly将失去以后出击工兵的权利

Showing the 12 most recent of 133 posts we hold for @hbcy_sh. 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 4 posts on @hbcy_sh 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
14 October 2026
Most recent seen missing
6 November 2026
Median time before seen missing
26 hours
Seen missing in the last 30 days
3

Forward network

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

“上海【沪伴茶语】精选榜” (@hbcy_sh), 18,327 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/hbcy_sh.

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.