Telegram RegisterThe public register of Telegram
Telegram profile photo for 熊出没(杭州)

Channel

熊出没(杭州)

@xdrj002

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

14,331subscribers

+2,332 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002534094236
TypeChannel
Username@xdrj002
Description🐻看过花开就好了🌸何必在意花属于谁
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/xdrj002

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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
@HZMTRZB/403111 Aug 2026, 10:46 UTC@xdrj002/936 · this entry11 Aug 2026, 10:46 UTC1.00under a minute
@HZMTRZB/409113 Aug 2026, 10:36 UTC@xdrj002/938 · this entry13 Aug 2026, 10:36 UTC1.00under a minute
@HZMTRZB/419018 Aug 2026, 07:43 UTC@xdrj002/960 · this entry18 Aug 2026, 07:43 UTC1.00under a minute
@HZMTRZB/421421 Aug 2026, 04:00 UTC@xdrj002/966 · this entry21 Aug 2026, 04:00 UTC1.00under a minute
@xdrj002/1055 · this entry2 Nov 2026, 16:14 UTC@HZMTRZB/49502 Nov 2026, 16:14 UTC1.00under a minute
@HZMTRZB/49855 Nov 2026, 15:09 UTC@xdrj002/1060 · this entry5 Nov 2026, 15:09 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
@HZMTRZB7 (7/7 hand-verifiable sample passed)0.99under a minute@HZMTRZB (6–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. 6 of the 6 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 23 comparable posts for this entry, running 22 June 2026 to 5 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 @HZMTRZB. 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

11,99117,89214,941.514,3316 August 202612 November 2026
63 measurements spanning 97 days, net +2,332. 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 11,106–18,777 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
12 Nov 2026, 00:4914,331+103
10 Nov 2026, 02:5614,228+1,884
8 Nov 2026, 14:4912,344+21
7 Nov 2026, 07:1712,323+32
6 Nov 2026, 03:3712,291+11
5 Nov 2026, 01:5912,280+3
3 Nov 2026, 22:1612,277+4
2 Nov 2026, 21:0412,273-8
1 Nov 2026, 21:1912,281-7
31 Oct 2026, 22:2712,288-4
30 Oct 2026, 22:5012,292-6
29 Oct 2026, 19:2912,298-6
28 Oct 2026, 17:1112,304-3
27 Oct 2026, 16:3112,307-5
26 Oct 2026, 17:3712,312-3
24 Oct 2026, 21:3112,315-6
23 Oct 2026, 19:0112,321-6
22 Oct 2026, 18:4812,327-12
21 Oct 2026, 18:0112,339-13
20 Oct 2026, 13:5812,352first reading

Engagement

49 posts held, back to 22 June 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 80 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.0%
avg views ÷ 14,331 subscribers
Avg views / post
1,580
4 posts measured
Reaction rate
0.177%
reactions ÷ views · ER floor
Posts in window
4
of 49 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 4 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 5 November 2026
Posts held49 (22 June 2026 – 5 November 2026)
Views total6,300
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 08:46 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
141
Videos
44
Links
13

Lifetime counters from Telegram’s own channel header, read 14 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.

Video runtime
2m 19s
Average length
12s

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

464 reactions across 33 posts, in 7 distinct kinds. The most used accounts for 94.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤43794.2%
👍112.37%
😱71.51%
🔥51.08%
👀20.431%
👏10.216%
🥰10.216%

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

Measured over the 49 most recent posts we hold, published 22 June 2026 to 5 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.

Telegram Stars

Stars received
29
across the posts below
Posts paid on
19
of 49 we hold a reading for · 39%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @xdrj002. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 49 most recent posts we hold for this entry, published 22 June 2026 to 5 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 4 posts held from the last 30 days (50.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).

5 Nov 2026, 15:09 UTC640 viewsread 7 November 2026
Photo

#coco @plmoknijb25 的美团福利 📮 抽奖条件: 🎫 加入 杭州美团认证频道 🎫 加入 杭州美团报告频道 🎫 加入 熊出没(杭州) 🎫 加入 杭州Coco温馨家园 🎫 加入 杭州美团 活动期间有效发言 1 条 🍀 每 10 群内积分增加 1 倍抽奖概率 ↳ 在活动群内发送「人品+n」 (活动如作废退还加倍积分) 🎁 奖品内容: 5折优惠券(限P) × 1 200口令红包 × 1 💡 活动说明: 本次活动由 #coco @plmoknijb25 倾情赞助,兑奖有效期3天。 中奖用户请在有效期内及时联系主办方/赞助方兑换 📅 开奖日期:(北京时间) 2026/11/8 13:00:00

5 Nov 2026, 14:55 UTC≈1,420 views2 reactionsread 14 November 2026
Photo

600价位里给到夯 去过都说好 (我也偷偷去过了) ☝️ @gdiiti

👍2

2 Nov 2026, 16:14 UTC≈1,050 views2 reactionsread 7 November 2026
Photo

#小雪 @xe11520 的美团福利 📮 抽奖条件: 🎫 加入 杭州美团认证频道 🎫 加入 杭州美团 🎫 加入 熊出没(杭州) 🎫 加入 雪雪聊天室 🎫 加入 小雪的小家 🍀 每 10 群内积分增加 1 倍抽奖概率 ↳ 在活动群内发送「人品+n」 (活动如作废退还加倍积分) 🎁 奖品内容: 200通用优惠券 × 2 💡 活动说明: 本次活动由 #小雪 @xe11520 倾情赞助 ,优惠券兑换有效期5天。 中奖用户请在有效期内及时联系主办方/赞助方兑换 📅 开奖日期:(北京时间) 2026/11/6 12:00:00

❤2

22 Oct 2026, 08:19 UTC≈3,190 views6 reactionsread 14 November 2026
Photo

🚩腿长1M的—— #六六 🌟🌟🌟🌟🌟 传送门: @liuliubbbb 位置:#杭州 #拱墅区 水费:1100 颜值:人照9分 硬件:白皮,B+粉嫩,皮肤捏出水的感觉 屌感:很紧,日日水更多 情绪价值:不多不少,正好 Tips: “哇,你好高啊” 资料写170+的老师很多,真的一进门就被雪白的大长腿吸引的六六算是第一个。 看到之前有熟人去了说人照9.5 确实颜值在这个价位很能打。 妹妹课室比较干净整洁这点很好,浴室很小,有两个卫生间,也没有要共浴,妹子害羞我懂得。 到了床上朦胧的灯光一个娇嫩的肉体挤入怀中,抓揉着妹妹稚嫩的白兔,口中含入粉粉的乳头,很快就有了感觉,前戏很投入,妹妹很耐心可以陪你一直大蟒蛇互动,进攻到下面也是个小跳跳虾。 刚进入阻尼感很强,妹妹微微皱眉,有点欲拒还迎的感觉让人泛起怜香惜玉之心,赶忙安慰“我很温柔你放心” 循序渐进后渐入湿境,腿长的可玩性很高,手感很好,抬起来压住的感觉征服感很足,后入也可以配…

❤6

13 Oct 2026, 23:13 UTC≈3,540 viewsread 8 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7762378275

21 Sept 2026, 15:53 UTC≈6,850 views2 reactionsread 14 November 2026
Photo

杭州美团 主打精简优质,不卷活跃,获取优惠券、积分门槛超低 📍 加入群组 📣 关注榜单

❤2

20 Sept 2026, 14:39 UTC≈5,460 views1 reactionsread 14 November 2026
Forwarded from @DVAaibotPhoto

D.V.A 群管家1.0 遥遥领先 关注D.V.A频道送14天满血订阅 本条消息转发频道并置顶 可领取30天满血订阅 功能亮点: · 独立的web/miniapp双端管理后台 · 包含FZ功能,可一键迁移 · 包含抽奖机器人VIP功能 · 独创摇一次 / 踢一球 / 来一镖 全新促活游戏玩法 · 支持人机自动审核入群 / 自动拒绝垃圾账号入群申请 · 竞拍活动自助预告查询 · 可与教师管理后台联动发布竞拍/兑换活动 @dvagroupbot

❤1

19 Sept 2026, 09:56 UTC≈4,570 views1 reactionsread 14 November 2026
Photo

💃好厚米新店开业活动价500/h💃 猪猪侠恋爱体验馆 ⏰(测评后返50) 💃#小鼠 18-24 疯狂小野猫 超大 💃#挽挽 15-24 明艳动人 超大 💃#若熙 15-24 超级素人 超大 传奇女仆 🔝夭夭 情绪颜值顶级 周一回归 剩6-10(不参与任何优惠) 🍓🐍吻,摸🦵,撕🦵,摸🐻,亲🐻 🚗 外派服务:1200/2h(新店活动999/2h)+路费 📍/三墩附近 TG速约 @Finotey 客服vx HSZ47799 双向联系 @Zhuzhullbot 交群流 @zhuzhuxia66 排班群 @zhuzhullll 测评群 @zhuzhuceping

❤1

18 Sept 2026, 11:01 UTC≈5,020 views1 reactionsread 14 November 2026
Photo

有没有力量型小姐姐推荐我下

❤1

30 Aug 2026, 08:21 UTC≈6,460 views8 reactions1 Starread 14 November 2026
Photo

🚩高高瘦瘦古灵精怪—— #锦瑟 🌟🌟🌟🌟 传送门: @jinse04 位置:#杭州 #萧山区 水费:800 颜值:人照8-9分 硬件:无纹身,黄白皮,B+,腰臀比很棒 屌感:湿紧度不错 情绪价值:温柔小妹妹的感觉 Tips: “你已经好了?” 被鸽子后随缘出击的妹妹,看了下照片应该是高高瘦瘦的款,比较合眼缘火速预约出击了下。 见到妹妹,妹妹第一句话问我多高,赶紧凑上来和我比了比肩,然后balabala问了我一堆小问题,破冰还是还是蛮愉快的。妹妹的身体蛮不错,腰臀比很完美,共浴的时候正计划一会后入一下。 到了床上妹妹说自己会的不多,问题不大,舌吻起手给妹妹压到身下,先服务一波,妹妹又问为什么是你给我服务?我说我教你,妹子有些敏感,没有施展太开,只好让妹子展示下口技,技术和认真程度都不错。我提议让妹妹坐上来,屌感很烫很湿,上下律动起来非常润,过程中让妹妹趴在我身上一边盯着一边愉快的舌吻。 But 妹妹一会来了兴致,长腿…

❤8

27 Aug 2026, 13:54 UTC≈1,000 viewsread 29 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7762378275

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@xdrj002 edited 4 posts 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
17 August 2026
Most recent edit
27 August 2026

Posts recorded as deleted after publishing

We recorded 8 posts on @xdrj002 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
11 August 2026
Most recent seen missing
5 November 2026
Median time before seen missing
52 days
Seen missing in the last 30 days
4

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

“熊出没(杭州)” (@xdrj002), 14,331 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/xdrj002.

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.