恢复了,大家重新提交。
❤2👍1

Channel
@xiaoxiongpindao
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
13,481subscribers
+5,519 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002534153956 |
|---|---|
| Type | Channel |
| Username | @xiaoxiongpindao |
| Created | 10 June 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/xiaoxiongpindao |
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 07:40 | 13,481 | +127 |
| 17 Sept 2026, 00:59 | 13,354 | +122 |
| 15 Sept 2026, 04:36 | 13,232 | +85 |
| 13 Sept 2026, 11:58 | 13,147 | +114 |
| 11 Sept 2026, 16:20 | 13,033 | +149 |
| 9 Sept 2026, 00:41 | 12,884 | +172 |
| 5 Sept 2026, 16:17 | 12,712 | +176 |
| 3 Sept 2026, 14:58 | 12,536 | +100 |
| 2 Sept 2026, 05:23 | 12,436 | +93 |
| 1 Sept 2026, 05:15 | 12,343 | +90 |
| 31 Aug 2026, 01:47 | 12,253 | +124 |
| 30 Aug 2026, 01:54 | 12,129 | +104 |
| 29 Aug 2026, 00:53 | 12,025 | +181 |
| 28 Aug 2026, 02:13 | 11,844 | +124 |
| 27 Aug 2026, 02:24 | 11,720 | +175 |
| 25 Aug 2026, 22:56 | 11,545 | +146 |
| 24 Aug 2026, 19:48 | 11,399 | +357 |
| 23 Aug 2026, 07:37 | 11,042 | +446 |
| 21 Aug 2026, 22:08 | 10,596 | +452 |
| 20 Aug 2026, 20:52 | 10,144 | first reading |
16 posts held, back to 10 June 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 38 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 16 (10 June 2025 – 2 September 2026) |
| Views total | 6,353 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 21:42 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.
Measured directly from 1 video 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.
130 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 66.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 86 | 66.2% | |
| 👍 | 24 | 18.5% | |
| 🤣 | 11 | 8.46% | |
| 🤮 | 5 | 3.85% | |
| 👏 | 1 | 0.769% | |
| 🔥 | 1 | 0.769% | |
| 😍 | 1 | 0.769% | |
| 🤯 | 1 | 0.769% |
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 14 of the 16 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 130 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 10 June 2025 to 2 September 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.
恢复了,大家重新提交。
❤2👍1
真地址接口异常,恢复了会通知,大家稍等下。
❤3
今晚小熊市场订单价格不错哦,黑客吃的饱饱的(*^-^)ノ🎉 有脱裤的机主订单发小熊市场秒出🤗 @xiaoxiongmarket
❤4😍1
很多用户打不开小熊市场,我咨询了几个能打开小熊市场的用户,根据他们使用的vpn/代理做了一份整理,以下白鲸和绿茶是免费的,其他都是收费的,群友推荐,请谨慎测试使用。 1、影子vpn:https://www.yingzi01.com/#/register?code=LRcuwcOZ 2、白鲸加速器:https://xn--yfrw1g6t2b8ovxfn.com/ 3、绿茶vpn:http://www.lvcha.org/ 4、狗急加速:https://goj999.com/app/index.html#/ 比较推荐付费影子vpn,一个月9.9人民币也有60g流量,不看小黄片的话,完全够用。
🤣5❤3
个户机器人真地址出单规则调整成同一天只收一次费用。 1、同一个用户,同一条身份证,在同一天内出过一单真地址后,再出真地址的所有版本都不再扣分; 2、出假地址后再出真地址需要扣积分。 3、出真地址后再出假地址也不需要扣积分。 2026年8月29日
👍10❤6🤯1
定义一下什么是硬广和软广: 1,硬广:交流群里没人问你你就直接发你的广告,没有上下文。 2,软广:交流群里有人问你的业务或者价格,你回复他,想促成交易。 小熊交流群不允许硬广,但是允许软广,允许大家在群里讨论交易甚至报价。
👍13❤8🤣6🤮5👏1🔥1
7月27日星期三 全国真地址、假地址均正常。 以下地区可出单(命中地区价格便宜,但是出单率有限,地区无法出单的自动走全国接口): 江苏 - 32 (24小时) 湖北 - 42 (24小时) 湖南 - 43 (24小时) 广西 - 45 (24小时) 海南 - 46 (24小时) 安徽 - 34 (早9晚19:30) 江西 - 36 (24小时) 广东 - 44 (早9晚19:30) 重庆 - 50 (早9晚19:30) 山东 - 37 (24小时) 甘肃 - 62(24小时) ‼️所有地区接口单文字户籍都是24小时可出。 ‼️地区订单是融合在一起的同一个命令。 ‼️命中地区且出单了,价格才会返回积分。 ‼️跨省迁户的不在地区范围的直接走全国接口。 ‼️地区接口也支持所有真地址版本(白底个户,身份证版本,各盖章版本)。
❤11
同样供需频道,同一时间对比3个小时前的阅读数据: 春江供需156606订阅,阅读479。价格30u一条。 小熊供需4799订阅,阅读317。价格5u一条。 对比时间:7月23号23:51 此数据仅作参考真人阅读率。
❤22
春江26776成员,2471在线 2471/26776=0.09228=9.22% 小熊群2795成员,596在线 (596/2795=0.21324=21.32%) 对比时间7月23号23:50 此数据只是参考对比小熊群的真人比例情况,并无炫耀之意。 当然群时间越长,注销账号的垃圾账号也会很多,不过小熊的5群时间也快一年多了。
❤4
小熊免费版假地址大头机器人 @xxjdzbot 小熊免费版假地址大头机器人 @xxjdzbot 小熊免费版假地址大头机器人 @xxjdzbot 🔛明天早上9点正式开启 ⌛️早9:00-晚19:30 ━━━━━━━━━━━━ 👤 匿名发布 🆘供需仅作为广告展示,请尽量在小熊群发起担保交易,谨防被骗。
❤8
🔥🔥小熊机器人已经全面支持@okpay 的交易,@okpay 官方交流群里面有大量的人出售usdt,而且可以自由的选择支付宝和微信交易,以上两个视频教你如何使用。 第一个视频:从okpay交易群里用微信支付购买usdt到okpay的钱包💰💰 第二个视频:小熊机器人用okpay钱包充值积分💵💵。 okpay有很多假冒机器人,注意真伪,另外交易一定要在群里通过okpay的交易机器人交易,不要私聊交流。
❤4
个户机器人结果为空,有以下几种原因: 1、现役军人、武警官兵、特殊部门人员及特殊级别官员; 2、退役不到2年的军人和士兵(根据军衔、兵种不同,时间会有所不同,一般为2年); 3、户口迁出,且没有在新的迁入地迁入; 4、户口迁入新迁入地,当地公安系统未将迁移信息上报到公安部(上报时间地域不同而有所差异); 5、更改姓名,当地公安系统未将更改信息上报到公安部(上报时间因地域不同而有所差异); 6、移民; 7、未更换二代身份证; 8、死亡; 9、身份证号确实不存在。 接口信息与公网实时同步,保证全网最高核验准确率。
❤6
Showing the 12 most recent of 16 posts we hold for @xiaoxiongpindao. 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.
@xiaoxiongpindao 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@xiaoxiongpindao named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“小熊机器人通知频道” (@xiaoxiongpindao), 13,481 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/xiaoxiongpindao.
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.