Telegram RegisterThe public register of Telegram
Telegram profile photo for 支付小屋

Channel

支付小屋

@zhifuxiaowu

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

416subscribers

-480 since we began measuring on 16 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003945757358
TypeChannel
Username@zhifuxiaowu
CreatedBetween 1 April 2026 and 8 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live17 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/zhifuxiaowu

Topic

Hacking & security — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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.

Growth

41689665616 August 2026 — 896 subscribers16 August 2026 — 896 subscribers17 August 2026 — 894 subscribers24 August 2026 — 596 subscribers30 August 2026 — 537 subscribers9 September 2026 — 431 subscribers17 September 2026 — 416 subscribers16 August 202617 September 2026
7 measurements spanning 31 days, net -480. 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 344–968 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 03:59416-15
9 Sept 2026, 08:40431-106
30 Aug 2026, 05:12537-59
24 Aug 2026, 05:13596-298
17 Aug 2026, 11:56894-2
16 Aug 2026, 19:30896no change
16 Aug 2026, 19:15896first reading

Engagement

20 posts held, back to 8 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

10 Jun 2026, 16:14 UTC426 views0 reactionsread 16 August 2026

目前开启 【通道名称】:咸鱼直付(无需确认收货) 【通道编码】:6028 【通道金额】:20-30-50 -100 -200 【通道成率】:80+ 【通道规则】:全层抗投,博彩,棋牌,彩票,视频,打赏! ⚠️禁三黑、电炸、杀猪、刷单、资金、代付、贷款、大头贴, 诈骗等一切黑资,发现不退不补不下发 发现大头贴 1:10赔付 不扯皮 ❗️ 1. 更换店铺支付,更改附言支付,不退不补!! ⚠️ 会员需下载咸鱼APP 开启默认规则 ❗️ 咸鱼大风控 费率上调到 费率7.2 7.2 7.2

10 Jun 2026, 15:57 UTC393 viewsread 16 August 2026

目前开启 【通道名称】:支付宝永辉商城 【通道编码】:6015 【通道金额】:10-100(整数) 【通道规则】:【通道规则】:全层 抗投,只接bc棋牌量,查单24小时 🈲三黑 大头贴 资金 电诈 刷单 杀猪 电商不发货 游戏盲盒 彩票抽奖 话费优惠卷 引流等一切黑料,一旦发现除bc棋牌以外的量,按照当日全部通道跑量1:10赔付,外加10w赔付费用,造成死主体的额外加10w赔付! ⚠️ 开启即默认规则 🉑带彩 ⚠️金额开10/20/30/40/50/60/70/80/90/100 费率 14.3 14.3

10 Jun 2026, 15:13 UTC295 viewsread 16 August 2026

11.20准时日切算账 请各位老板及时调整 祝您发财

9 Jun 2026, 15:52 UTC140 viewsread 16 August 2026

目前开启 【通道名称】:咸鱼直付(无需确认收货) 【通道编码】:6028 【通道金额】:20-30-50 -100 -200 【通道成率】:80+ 【通道规则】:全层抗投,博彩,棋牌,彩票,视频,打赏! ⚠️禁三黑、电炸、杀猪、刷单、资金、代付、贷款、大头贴, 诈骗等一切黑资,发现不退不补不下发 发现大头贴 1:10赔付 不扯皮 ❗️ 1. 更换店铺支付,更改附言支付,不退不补!! ⚠️ 会员需下载咸鱼APP 开启默认规则 ❗️ 费率6.5 6.5 【通道名称】:支付宝永辉商城 【通道编码】:6015 【通道金额】:10-100(整数) 【通道规则】:【通道规则】:全层 抗投,只接bc棋牌量,查单24小时 🈲三黑 大头贴 资金 电诈 刷单 杀猪 电商不发货 游戏盲盒 彩票抽奖 话费优惠卷 引流等一切黑料,一旦发现除bc棋牌以外的量,按照当日全部通道跑量1:10赔付,外加10w赔付费用,造成死主体的额外加

9 Jun 2026, 15:27 UTC129 viewsread 16 August 2026

11.30准时日切算账 请各位老板及时调整 祝您发财

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

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“支付小屋” (@zhifuxiaowu), 416 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/zhifuxiaowu.

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.