Telegram RegisterThe public register of Telegram
Telegram profile photo for 茶语作业反馈频道

Channel

茶语作业反馈频道

@hubanchaye

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

15,295subscribers

-8,203 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-1002002780105
TypeChannel
Username@hubanchaye
Description唯一管理:https://t.me/hubanchayu8 作业反馈:https://t.me/hbcy_bot 交流群: t.me/hubanchayu_shanghai 精选榜: t.me/hbcy_sh 人气榜: t.me/hubanchaye_BD 广播站; t.me/shanghaichayu 备用群:t.me/hubanchayu 总导航:t.me/hbcy_dh 一键关注所有频道 https://t.me/addlist/dLsRw8Ru0zVjYTQ1
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 October 2026
Last confirmed live16 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/hubanchaye

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 19 October 2026 and assigned it the closest of 31 fixed categories, at 94% 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/2147 · this entry2 Nov 2026, 07:37 UTC@hbcy_sh/35412 Nov 2026, 07:37 UTC1.00under a minute
@hubanchaye/2158 · this entry3 Nov 2026, 06:18 UTC@hbcy_sh/35633 Nov 2026, 06:18 UTC1.00under a minute
@hbcy_sh/35653 Nov 2026, 06:59 UTC@hubanchaye/2160 · this entry3 Nov 2026, 06:59 UTC1.00under a minute
@hbcy_sh/35673 Nov 2026, 09:49 UTC@hubanchaye/2163 · this entry3 Nov 2026, 09:49 UTC1.00under a minute
@hubanchaye/2166 · this entry3 Nov 2026, 11:40 UTC@hbcy_sh/35693 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
@hbcy_sh5 (5/5 hand-verifiable sample passed)1.00under a minute@hbcy_sh (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. 5 of the 5 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 133 comparable posts for this entry, running 26 September 2026 to 17 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_copy, last confirmed 18 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

15,29523,50919,4024 October 2026 — 23,498 subscribers4 October 2026 — 23,498 subscribers8 October 2026 — 23,509 subscribers12 October 2026 — 23,373 subscribers14 October 2026 — 23,303 subscribers15 October 2026 — 23,292 subscribers16 October 2026 — 23,276 subscribers17 October 2026 — 22,738 subscribers18 October 2026 — 22,669 subscribers19 October 2026 — 22,544 subscribers20 October 2026 — 22,361 subscribers21 October 2026 — 22,218 subscribers22 October 2026 — 21,834 subscribers23 October 2026 — 21,521 subscribers24 October 2026 — 21,179 subscribers25 October 2026 — 21,031 subscribers26 October 2026 — 20,610 subscribers27 October 2026 — 20,393 subscribers28 October 2026 — 20,065 subscribers29 October 2026 — 19,679 subscribers30 October 2026 — 19,335 subscribers31 October 2026 — 19,075 subscribers1 November 2026 — 18,871 subscribers2 November 2026 — 18,768 subscribers3 November 2026 — 18,809 subscribers4 November 2026 — 18,664 subscribers5 November 2026 — 18,417 subscribers6 November 2026 — 18,275 subscribers7 November 2026 — 17,881 subscribers9 November 2026 — 17,531 subscribers10 November 2026 — 16,952 subscribers13 November 2026 — 16,391 subscribers16 November 2026 — 15,295 subscribers4 October 202616 November 2026
33 measurements spanning 43 days, net -8,203. 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 14,063–24,741 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
16 Nov 2026, 11:4415,295-1,096
13 Nov 2026, 01:2616,391-561
10 Nov 2026, 21:5416,952-579
9 Nov 2026, 06:3117,531-350
7 Nov 2026, 19:4717,881-394
6 Nov 2026, 16:2618,275-142
5 Nov 2026, 16:5018,417-247
4 Nov 2026, 16:3818,664-145
3 Nov 2026, 13:4818,809+41
2 Nov 2026, 12:0818,768-103
1 Nov 2026, 15:3718,871-204
31 Oct 2026, 17:2119,075-260
30 Oct 2026, 17:1019,335-344
29 Oct 2026, 14:3919,679-386
28 Oct 2026, 12:4920,065-328
27 Oct 2026, 15:1720,393-217
26 Oct 2026, 17:3820,610-421
25 Oct 2026, 17:2021,031-148
24 Oct 2026, 18:0021,179-342
23 Oct 2026, 18:5821,521first reading

Engagement

163 posts held, back to 26 September 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 54 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.34%
avg views ÷ 15,295 subscribers
Avg views / post
359
82 posts measured
Reaction rate
0.143%
reactions ÷ views · ER floor
Posts in window
106
of 163 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 3 of 82 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 held163 (26 September 2026 – 18 November 2026)
Views total29,402
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 19:00 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
257
Links
457

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3100.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 7 of the 163 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 163 most recent posts we hold, published 26 September 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: 28 of 106 posts held from the last 30 days (26.4%) 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 UTC38 viewsread 18 November 2026
Photo

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

18 Nov 2026, 07:51 UTC47 viewsread 18 November 2026

🍭验证老师: #小琪 ☁️联系方式: @xiao00qi 🎈验证时间:11.18 📍地理位置:#金桥 💵修车水费:#1000p 😵验证学生:老A86 ❤️优点缺点: 温柔,身材好,服务到位 💌推荐程度:10 ———————————— 🐻是亮点 颜值可以 身材也是很棒 人照基本一致 身材和模特一般 大长腿 腰很细 屁股翘 腿玩年 🐻大概在B+的样子 小穴户型普通没有异味 毛量一般般 穴紧 身上纹身不多腿上一些 态度非常可以 有点害羞 课表上有的服务都有 不含糊 叫声真实 好身材大长腿呈现出一副好的炮架

17 Nov 2026, 16:54 UTC553 viewsread 18 November 2026

🍭验证老师: #月月 ☁️联系方式: @yueyue0022 🎈验证时间:11.17 📍地理位置:#长宁 💵修车水费:#工兵6pp 😵验证学生:keepliveee ❤️优点缺点: 御姐温柔有引导 💌推荐程度:9 ———————————— 服务过程:到老师提到的地铁站后,根据老师的指引走到课室,老师很细心谨慎,会提醒该注意的地方,课室整体安全性好。开门见到老师后,人照基本一致,就是去掉美颜的状态,老师会贴心的拿水,提醒不要发出太大声音,然后一起洗澡帮洗完后进入房间。房间收拾得很整洁,有一股淡淡的香味,过程中老师会穿上黑色吊带裙。因为约的是pp所以先k立了带套开始第一次,配合度很高,过程中可以感受到老师的收缩,听到老师的哼喘,情绪价值给到,顺利出货。中间聊天休息了一会儿后,开始做ab面服务,和课表上的内容一致,到位的服务系内容,之后开启了第二次,体验了三四个姿势后顺利出货,中间情绪价值依旧给满,过程不多赘述。总之老师很温柔,整体性…

17 Nov 2026, 15:41 UTC489 viewsread 18 November 2026

🍭验证老师: #糯糯 ☁️联系方式: @db197460 🎈验证时间: 11.17 📍地理位置: #闵行 💵修车水费: #p 😵验证学生:TTFF ❤️优点缺点: 母狗M 💌推荐程度: #好评 ———————————— 服务过程:关注老师很久了,看到频道里的评价可以玩SM还可以潮喷,今天兴致来了,欣然前往。见到本人是御姐范,奶子很大,洗好澡躺床上有服务,老师喜欢被捏乳头,越捏她越兴奋,口的越深,感觉肉棒都顶到老师的喉咙了。口的快受不了了感觉叫停,让老师在上面,太骚了,用力猛干,啪啪啪声太大,动了一会老师叫我在上面,抗着她的双腿,两个人控住她的球,捏她乳头大力猛操,然后在拔出来用龟头左右帮老师按摩阴蒂,老师一下子就喷了出来。应该是阴蒂太敏感了,后面换后入侧入,老师说干的她太爽了,喜欢有劲的年轻人,在老师猛烈的叫喊声中123完事了,做的过程比较爽,持久的兄弟去体验感应该比较好。

17 Nov 2026, 08:34 UTC260 viewsread 18 November 2026

🍭验证老师: #小琪 ☁️联系方式: @xiao00qi 🎈验证时间: 11.17 📍地理位置: #浦东 💵修车水费: 1000p 😵验证学生:天真 ❤️优点缺点: 真人真照,身材好,漂亮 💌推荐程度: 值得推荐 ———————————— 服务过程:看到的其他反馈也是很不错,见面后的真实评价,18岁的年龄其身高165cm,大长腿,腰很细,无赘肉,身材好,胸特别美,服务细节都很到位,配合很高,很是听话,为人考虑着想,屌感具有丝滑感,值得推荐。

17 Nov 2026, 04:31 UTC388 viewsread 18 November 2026

🍭验证老师: #依依 ☁️联系方式: @yiyi1wo 🎈验证时间: 11月15 📍地理位置: #普陀 💵修车水费: #p 😵验证学生:ssimak ❤️优点缺点:可爱,服务好 ,值得多刷 💌推荐程度: #非常推荐 —————————————— 服务内容:,态度特别热情,瞬间就把期待值拉满了。进入正题后体验更是绝佳,口活特别舒服,完全零齿感,中途还会主动配合很快能进入状态,互动感极强,女友感简直拉满,整个过程中非常敏感,无论是视觉还是感官体验都是一种极致的享受,中途还会说很多让人脸红心跳的话,仿佛真的拥有了一个专属的小女友一样。最后在后入时顺利出货,结束后也没有半点敷衍,依然很耐心地陪着聊天,完全不催人。 这样兼顾颜值,配合度和服务态度的宝藏体验,真的要且行且珍惜,性价比和服务全都是满分,已经开始期待和老师的下次见面了

17 Nov 2026, 00:37 UTC273 viewsread 18 November 2026

🍭验证老师: #小琪 ☁️联系方式: @xiao00qi 🎈验证时间: 11.16 📍地理位置: #浦东金桥 💵修车水费: #工5 😵验证学生: Lili ❤️优点缺点: 嫩 爱笑 身材好 💌推荐程度: #值得推荐 ———————————— 服务过程: 看到老师在金桥,还真挺近,就出击了。看到老师,人照合一,九成像,163左右身高吧吧,嫩,18的样子。身材很棒,无一丝赘肉,非常瘦,能摸到胯骨的那种,胸B-吧,摸上去很有手感很棒,乳头很小很精致。一起去洗澡,浴室里楼楼亲亲,已经梆梆硬,老师也很温柔,很爱笑。上复式二楼,我先简单上上下下亲了舔了,下面也干净的。然后老师给吹,已经很硬了,带套开干,女上起手,搂着就是凿,转cjs紧搂着继续凿。老师提出后入比较深,那必须同意,然后两下就交代了。挺满意的出击。

16 Nov 2026, 13:45 UTC277 viewsread 18 November 2026

🍭验证老师: #汐颜 ☁️联系方式: @xiyan1000 🎈验证时间:11月15日 📍地理位置:#浦东 💵修车水费:600pp 😵验证学生:liming ❤️优点缺点:服务挺不错的态度非常好性格也很好 💌推荐程度:非常推荐 ———————————— 服务内容:汐颜老师很温柔,一进屋就是白色小兔制服,提前给你接好水,然后陪你yyy。进屋躺着,老师开始从上开始往下舔,舔的很舒服,老师是大蟒蛇,一直舌吻舔耳朵,口活也很卖力。口的时候差点没把持住,然后带t开始女上服务,全程自动很舒服。老师一直舞动边干边舔,最后后入没忍住,然后洗澡结束缓了一会接着继续,由于的确比较久也比较累,第二次玩了很久一直没出来了,老师也很尽力了,总体还是非常不错的。

Showing the 12 most recent of 163 posts we hold for @hubanchaye. 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 6 posts on @hubanchaye 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
5 November 2026
Most recent seen missing
13 November 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
6

Forward network

Republished by

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

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

“茶语作业反馈频道” (@hubanchaye), 15,295 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/hubanchaye.

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.