Telegram RegisterThe public register of Telegram
Telegram profile photo for 黑马独家业务播报

Channel

黑马独家业务播报

@heima001b

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

133subscribers

-149 since we began measuring on 13 September 2026

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

Register entry

Telegram ID-1002648585059
TypeChannel
Username@heima001b
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live7 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/heima001b

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 7 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 why it has no browse page of its own yet.

Growth

133282207.513 September 2026 — 282 subscribers13 September 2026 — 282 subscribers14 September 2026 — 256 subscribers26 September 2026 — 163 subscribers7 October 2026 — 133 subscribers13 September 20267 October 2026
5 measurements spanning 24 days, net -149. 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 111–304 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 04:36133-30
26 Sept 2026, 22:41163-93
14 Sept 2026, 17:57256-26
13 Sept 2026, 08:22282no change
13 Sept 2026, 07:47282first reading

Engagement

20 posts held, back to 12 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.0%
avg views ÷ 133 subscribers
Avg views / post
19.9
18 posts measured
Reaction rate
7.84%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 2 of 18 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 13 September 2026
Posts held20 (12 September 2026 – 13 September 2026)
Views total359
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Sept 2026, 08:22 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.

Reaction mix

4 reactions across 2 posts, in 1 kind.

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

Measured over the 20 most recent posts we hold, published 12 September 2026 to 13 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.

Recent posts

13 Sept 2026, 08:09 UTC3 viewsread 13 September 2026

新渠道 银行流水 查最新一笔流水 柜台包出 带量谈价格

13 Sept 2026, 06:48 UTC13 viewsread 13 September 2026

实时公网在逃数据 45u出最新实时数据 撤销或者结案有详情 在逃无详情 带撤销

13 Sept 2026, 06:16 UTC18 viewsread 13 September 2026

中国银行名下卡带余额 工商银行名下卡带余额 农业银行名下卡带余额 邮政银行名下卡带余额 广发银行名下卡带余额 光大银行名下卡带余额 柜台卡反柜台流水 无盲刑侦流水 公网:个人名下所有银行卡 工商局:公司户名下卡 价格不高。有单上,稳定回单

13 Sept 2026, 05:24 UTC18 viewsread 13 September 2026

银行流水 公户 半年580 一年620 两年660 三年720 开卡800 私户 半年240 一年260 两年300 三年320 开卡400 5到7个工作日回 周日发车 现最稳流水 保真不保漏,上限9999条 柜台流水 现有 工商,中国,邮政,农业, 柜台公户流水 工商,中国,邮政 隔天回单 柜台保真保漏

12 Sept 2026, 14:20 UTCviews —

黑马优势播报(主打银行流水) pinned «👮想要业余赚点外快的条哥可以来聊一下,基层民警都可以来搞,权限高或很大的 日入过万,月入百万不是问题 长期寻可以查全国的 同户人,微信主体,公安.刑侦.经侦部门,运营商,房管局,民政局,车管部门,云搜部门,反诈部门,等各种有全国范围查询权限的条哥或内部人员合作。 权限越高赚的越多,包你安全的日入过万,一对一教专业的洗前变现手法,避免使用交易所入账出账被溯源追查。保证你的安全,从业5年多从未有任何一个合作伙伴出事,稳上岸。 权限低的基层民警,例如只能查:网络在逃,人脸找人之类的,也可以做到日入过万 是否有害怕和其他焦虑?📌…»

12 Sept 2026, 14:20 UTC23 viewsread 13 September 2026

👮想要业余赚点外快的条哥可以来聊一下,基层民警都可以来搞,权限高或很大的 日入过万,月入百万不是问题 长期寻可以查全国的 同户人,微信主体,公安.刑侦.经侦部门,运营商,房管局,民政局,车管部门,云搜部门,反诈部门,等各种有全国范围查询权限的条哥或内部人员合作。 权限越高赚的越多,包你安全的日入过万,一对一教专业的洗前变现手法,避免使用交易所入账出账被溯源追查。保证你的安全,从业5年多从未有任何一个合作伙伴出事,稳上岸。 权限低的基层民警,例如只能查:网络在逃,人脸找人之类的,也可以做到日入过万 是否有害怕和其他焦虑?📌 把心放到肚子里!多年老品牌。背后大型社工库。多种规避手段,避免原系统图片泄露,一对一教学洗钱混币躲ip追踪,安全虚拟币变现,从业多年无一合作伙伴出事,安全无忧。😃🤮😲🥵😤 Ps:目前微信,流水业务,名下房,全户业务,定位,轨迹这些业务都很需要,我这边单量可以保证,微信业务日入5w左右甚至10万。流水业务…

12 Sept 2026, 12:40 UTCviews —

黑马优势播报(主打银行流水) pinned «联系人 @xqx104 24小时在线客服机器人 @hmkf002bot»

Showing the 12 most recent of 20 posts we hold for @heima001b. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“黑马独家业务播报” (@heima001b), 133 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/heima001b.

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.