业务全部打折,效率包满意,下单渠道 @laoxian1
Channel
老仙业务频道
@hui5781
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
142subscribers
-20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002202385543 |
|---|---|
| Type | Channel |
| Username | @hui5781 |
| Created | 30 August 2024 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 2 times, most recently 4 November 2026 |
| On Telegram | t.me/hui5781 |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 08:06 | 142 | -5 |
| 20 Oct 2026, 15:46 | 147 | +1 |
| 14 Oct 2026, 11:50 | 146 | -1 |
| 7 Oct 2026, 03:22 | 147 | -1 |
| 26 Sept 2026, 13:55 | 148 | -2 |
| 5 Sept 2026, 13:36 | 150 | -1 |
| 29 Aug 2026, 04:18 | 151 | -4 |
| 22 Aug 2026, 22:45 | 155 | -3 |
| 14 Aug 2026, 19:06 | 158 | -4 |
| 8 Aug 2026, 16:47 | 162 | no change |
| 7 Aug 2026, 13:34 | 162 | first reading |
Engagement
3 posts held, back to 30 August 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 3 October 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
8 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 100.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 1 of the 3 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 30 August 2024 to 3 October 2025, 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
公网机主 破解机主 公支一体 无盲机主 支宝机主 支百分百 运营机主 电百机主 剩菜机主 三网机主 名下房产 名下车辆 名下行卡 名下公司 名下证件 名下号码 微信流水 支宝流水 银行流水 微信好友提取 企鹅好友提取 微信记录提取 企鹅记录提取 通讯录提取 通话记录提取 户籍 全家户籍 刑侦全户 真地个户 假地个户 盖章个户 模糊找人 猎魔信息 人脸识别 车档信息 学历信息 社保信息 法人信息 卡反信息 微反信息 Q反信息 抖反信息 同住记录 出行记录 实时定位 人物轨迹 车辆轨迹 飞机记录 火车记录 外卖地址 美团地址 饿了地址 快递地址 顺丰地址 邮政地址 综合地址 户籍地址 常住地址 京东地址 淘宝地址 关联地址 业务联系: @laoxian1 双向联系: @laoxian01_bot 频道: https://t.me/hui5781 支持担保 支持👍👍👍
❤8
Channel created
Showing the 3 most recent of 3 posts we hold for @hui5781. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@hui5781 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 9 August 2026 – 9 August 2026
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“老仙业务频道” (@hui5781), 142 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/hui5781.
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.