Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州星巴克新人工兵频道

Channel

杭州星巴克新人工兵频道

@hzxbkrz

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

45,559subscribers

+15,127 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003151574404
TypeChannel
Username@hzxbkrz
Description【主群】 @hzxbk
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/hzxbkrz

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 82% 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hzxbkrz/6333 · this entry19 Aug 2026, 14:23 UTC@hangzhouxbkzx/426419 Aug 2026, 14:23 UTC1.00under a minute
@hzxbkrz/6463 · this entry24 Aug 2026, 15:02 UTC@hangzhouxbkzx/436224 Aug 2026, 15:02 UTC1.00under a minute
@hzxbkrz/6635 · this entry31 Aug 2026, 14:13 UTC@hangzhouxbkzx/443731 Aug 2026, 14:13 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
@hangzhouxbkzx56 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (30–26)

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. 3 of the 3 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 285 comparable posts for this entry, running 11 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 @hzxbkrz — which is this entry. That is a statement about our reading window, not a claim of authorship.

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

30,43245,89138,161.545,55912 August 202614 November 2026
61 measurements spanning 94 days, net +15,127. 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 28,113–48,210 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
14 Nov 2026, 18:4845,559+25
11 Nov 2026, 17:4545,534-304
9 Nov 2026, 20:5645,838+55
8 Nov 2026, 12:0545,783-108
7 Nov 2026, 03:0645,891+53
6 Nov 2026, 02:0945,838+464
5 Nov 2026, 01:0645,374+540
3 Nov 2026, 22:2644,834+666
2 Nov 2026, 19:1044,168-60
1 Nov 2026, 21:4744,228-48
1 Nov 2026, 00:2844,276-195
31 Oct 2026, 00:4844,471+38
30 Oct 2026, 00:4944,433+70
29 Oct 2026, 01:5744,363+14
27 Oct 2026, 21:1644,349+205
26 Oct 2026, 19:4744,144+279
25 Oct 2026, 18:1743,865-57
24 Oct 2026, 18:0643,922+357
23 Oct 2026, 20:2043,565+950
22 Oct 2026, 21:4542,615first reading

Engagement

527 posts held, back to 10 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 178 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.18%
avg views ÷ 45,559 subscribers
Avg views / post
536
170 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
170
of 527 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held527 (10 August 2026 – 17 November 2026)
Views total91,075
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 18:06 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,280
Videos
≈711
Links
≈596

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
38m 33s
Average length
6s

Measured directly from 372 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 170 posts held from the last 30 days (0%) 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, 14:34 UTC306 viewsread 17 November 2026
Forwarded from @hangzhouxbkzxPhoto

【花名】#梅以漫 【联系】@meiyiman 【位置】#萧山 【价格】#2200P 【罩杯】#C 【标签】#御姐 #69互舔 🛫 纯欲天花板 【报告】 报告1 报告2 报告3 报告4

Signed 周旋久(小心骗子)

17 Nov 2026, 13:24 UTC411 viewsread 17 November 2026
Photo

【花名】 #若曦 【联系】 @gvhjcfju 【地区】 #拱墅 【价格】 #800p 【罩杯】 #C 【标签】 #嫩妹 #69互舔 #舌吻 🛫 新人嫩妹 【工兵优惠】: ①6折工兵2名,500P/1000PP ②报名请在群内发送“兑换”获取工兵名额 ③兑换成功后将兑换成功截图+报名表发送至机器人 @xbkgb_bot ④改期未报备或12小时内未预约作废,未按时出报告移除群聊 ⑤群内发送“报告”获取模板,报告提交 @xbkgb_bot 【报告】

Signed 周旋久(小心骗子)

17 Nov 2026, 10:43 UTC484 viewsread 17 November 2026
Photo

【花名】 #予朵 【联系】 @hzyuduo 【地区】 #萧山 【价格】 #1600p 【罩杯】 #B 【标签】 #嫩妹 #舌吻 🛫 肤白貌美大长腿,爱嫩妹 【报告】

Signed 周旋久(小心骗子)

17 Nov 2026, 10:34 UTC481 viewsread 17 November 2026
Photo

【花名】 #婉婉 【联系】 @wanwan988877 【地区】 #拱墅 【价格】 #800p 【罩杯】 #C 【标签】 #嫩妹 #69互舔 #舌吻 🛫 待测评 【工兵优惠】: ①6折工兵2名,500P/900PP ②报名请在群内发送“兑换”获取工兵名额, ③兑换成功后将兑换成功截图+报名表发送至机器人 @xbkgb_bot ④改期未报备或12小时内未预约作废,未按时出报告移除群聊 ⑤群内发送“报告”获取模板,报告提交 @xbkgb_bot【报告】

Signed 周旋久(小心骗子)

17 Nov 2026, 04:34 UTC593 viewsread 17 November 2026
Forwarded from @hangzhouxbkzxPhoto

【花名】#杭州灵动岛裸身私享泡泡浴 【联系】@hzppykf 【位置】#杭州 #余杭 #上城 【标签】#商家 #泡泡浴 #抓龙筋 #按摩 #spa 【价格】 【商家简介】 感谢为我停留💘ฅ՞•ﻌ•՞ฅ💘 这里是:杭州灵动岛裸身私享泡泡浴#杭州 #spa 🎵场所私密性优质、环境舒适,独家传承技艺泡泡浴老字号❤️弥漫着情欲的空间,入耳去忧的音乐,💘勾人的双臂将引导尊贵的你前往属于您的欢乐世界🎧细腻温润的泡泡环绕,指尖带来的温柔💅轻抚每一寸肌肤,纯口碑服务,舒缓压力,唤醒您身体的每一处感官 ☺️轻享 A 798/ 70 分:情景舒缓音乐+抚触欢迎礼 →半裸身制服+北海道泡泡浴+搓背助浴 →女友感亲密指滑+交感神经漫游+轻吟鼻吸 →冰火石三角区筋络疏通+丝袜捆绑脱敏训练 → 二代抓龙深度释放+沉浸式精油SPA按摩🛁 😍纵享 B 998/ 90 分:(包含 A )全裸身日式坐浴+贴贴花滑 →性感丝足挑逗+丝袜捆绑龟责寸止三起三落+AV…

17 Nov 2026, 03:41 UTC288 viewsread 17 November 2026
Photo

【花名】 #小猫 【联系】@xiaomao6782 【地区】 #上城 【价格】 #1300p 【罩杯】 #B 【标签】 #嫩妹 #69互舔 #舌吻 #萝莉 🛫 烧杯萝莉,幼态妹妹 【工兵优惠】: ①6折工兵2名,800P/1400PP ②报名请在群内发送“兑换”获取工兵名额, ③兑换成功后将兑换成功截图+报名表发送至机器人 @xbkgb_bot ④改期未报备或12小时内未预约作废,未按时出报告移除群聊 ⑤群内发送“报告”获取模板,报告提交 @xbkgb_bot 【报告】

16 Nov 2026, 08:41 UTC656 viewsread 17 November 2026
Forwarded from @hangzhouxbkzxPhoto

【花名】#小静 【联系】@xiaojing0088 【地区】#上城 【价格】#800P #1500PP 【罩杯】#B 【标签】#嫩妹 #舌吻 🛫 女友感十足,大众情人 【报告】 报告1 报告2 报告3 报告4 报告5 报告6

Signed 周旋久(小心骗子)

16 Nov 2026, 08:33 UTC674 viewsread 17 November 2026
Photo

【花名】 #小云 【联系】@xiaoyun0121 【地区】 #拱墅 【价格】 #1000p 【罩杯】 #B 【标签】 #嫩妹 #69互舔 #舌吻 #巨乳 🛫 又是细枝硕果 【工兵优惠】: ①6折工兵2名,600P/1100PP ②报名请在群内发送“兑换”获取工兵名额, ③兑换成功后将兑换成功截图+报名表发送至机器人 @xbkgb_bot ④改期未报备或12小时内未预约作废,未按时出报告移除群聊 ⑤群内发送“报告”获取模板,报告提交 @xbkgb_bot 【报告】

16 Nov 2026, 08:15 UTC633 viewsread 17 November 2026
Photo

【花名】 #李欣儿 【联系】@lxe5520 【地区】 #拱墅 【价格】 #900p 【罩杯】 #C 【标签】 #御姐 #69互舔 #舌吻 #车模 🛫 车模身材 【工兵优惠】: ①6折工兵2名,500P/1000PP ②报名请在群内发送“兑换”获取工兵名额, ③兑换成功后将兑换成功截图+报名表发送至机器人 @xbkgb_bot ④改期未报备或12小时内未预约作废,未按时出报告移除群聊 ⑤群内发送“报告”获取模板,报告提交 @xbkgb_bot 【报告】

16 Nov 2026, 08:00 UTC401 viewsread 16 November 2026
Forwarded from @hangzhouxbkzxPhoto

【花名】 #舒然 【联系】@suran2026 【地区】 #萧山 【价格】 #450p 【罩杯】 #B 【标签】 #御姐 #95 #口爆 #92 🛫 服务全都会,会所出身,无套口爆 【报告】

15 Nov 2026, 14:11 UTC341 viewsread 16 November 2026
Forwarded from @hangzhouxbkzxPhoto

【花名】 #刘念 【联系】@xyz123aa 【地区】 #上城 【价格】 #1200p 【罩杯】 #C 【标签】 #御姐 #69互舔 #舌吻 #反差 🛫 好看的皮囊千篇一律,合格的秘书万里挑一 【报告】

Signed 周旋久(小心骗子)

15 Nov 2026, 13:55 UTC435 viewsread 16 November 2026
Forwarded from @hangzhouxbkzxPhoto

【花名】#允恩 【联系】@yunen2026 【位置】#拱墅 【价格】#900p 【罩杯】#B 【标签】#嫩妹 #舌吻 #69互舔 🛫 待评价 【报告】 报告1 报告2 报告3

Showing the 12 most recent of 527 posts we hold for @hzxbkrz. 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 edited after publishing

@hzxbkrz edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
24 September 2026
Most recent edit
24 September 2026

Posts recorded as deleted after publishing

We recorded 7 posts on @hzxbkrz 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
15 August 2026
Most recent seen missing
17 November 2026
Median time before seen missing
18 hours
Seen missing in the last 30 days
1

Forward network

Republished by

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

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

“杭州星巴克新人工兵频道” (@hzxbkrz), 45,559 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/hzxbkrz.

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.